Manifest position 323 · CrUX rank bucket 1000
https://jp.xhamster.com
Coverage complete
Atomic coverage complete across five representative public archetypes; authenticated, payment, and destructive flows excluded.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Paired light and dark captures are visually unchanged, and the DOM reports color-scheme: normal; the interface remains dark under prefers-color-scheme: light. F01 medium: Theme does not follow the user’s light/dark preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found eight running shimmer animations, each 2000 ms, while matchMedia confirmed prefers-reduced-motion: reduce. F02 medium: Loading shimmer continues under reduced-motion. |
respect-user-preferencesrespects-contrast | issues | high | The CSS feature probe found no prefers-contrast/forced-colors handling; Lighthouse reported color-contrast failures. F03 medium: Contrast preferences are not handled and baseline contrast failures remain. |
implement-natural-interactionsview-transitions | issues | high | The loaded CSS contained no view-transition usage; navigation is conventional full replacement. F04 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, scrollytelling, or reveal behavior was present on the sampled templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-specific swipe, pull, reorder, or carousel interaction was exposed on the sampled paths; native scrolling remains available. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The first viewport and feature probe show fixed dense chrome but no scroll-state/container-query or scroll-timeline treatment. F05 low: Persistent navigation does not react to scroll state. |
provide-guided-navigationanchored-positioning | issues | medium | The CSS feature probe found no anchor-name, position-anchor, or position-try usage despite multiple header dropdown controls. F06 low: Menus and transient controls do not use resilient CSS anchoring. |
provide-guided-navigationdirects-attention | pass | high | Desktop screenshot shows a persistent labelled sidebar and a red active-tab underline; links have real href destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Homepage, detail, search, and signup captures all show the same near-full-viewport consent interruption covering core content. Reject is available, but reading or acting requires clearing the overlay first. F07 high: A large consent modal obscures every sampled primary surface on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | While the modal was visible, the feature probe found zero <dialog> elements and zero [role=dialog] elements. F08 medium: The blocking consent overlay lacks dialog semantics. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and narrow captures devote a large persistent left rail plus multiple top promotional bands to chrome; the narrow view leaves only a small clipped content column. F09 medium: Dense navigation and promotional chrome compete with primary content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout recorded scrollWidth 1038 versus visualViewportWidth 360, 678 px horizontal overflow, on both homepage and detail. The signup mobile capture places the form mostly off-screen. F10 critical: The site serves a desktop-width layout at a 360 px visual viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no @container rules, and the narrow screenshot shows desktop header/sidebar/content dimensions preserved and clipped. F11 high: Reused components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first focused link computed to outline: none and box-shadow: none. The probe lists many 25–40 px-high controls; Lighthouse also failed target-size. F12 high: Keyboard focus is invisible and many targets are too short. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage H1 and card grid clearly identify the catalogue; detail and search routes load their expected archetypes. |
support-core-task-successprimary-flow-completion | pass | high | A representative listing link reached the detail route directly with content and player region present; no account wall blocked browsing. |
support-core-task-successclear-system-state-and-recovery | pass | high | The deliberate invalid route rendered a Japanese “page not found” explanation, home link, support link, and recovery content. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.4 s and FCP 2.8 s, while the desktop trace was faster at 1.14 s; the common mobile condition misses the 2.5 s good LCP threshold. F13 medium: Mobile LCP is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.000012 on home and 0 on detail; Lighthouse reported CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded two long tasks, 152 ms TBT and a 167 ms longest task; Lighthouse mobile TBT was 10 ms, within the good range. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found three parser-inserted very-high-priority stylesheets; Lighthouse failed cache, image-delivery, dependency-tree and render-blocking insights. DOM confirmation shows scripts are deferred, so the issue is concentrated in styles and delivery rather than falsely labelling those scripts blocking. F14 medium: The critical path includes multiple render-blocking styles and weak cache/image delivery signals. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse failed unused CSS, unused JavaScript, and legacy JavaScript audits; HAR recorded 61 scripts and about 1.02 MB transferred script bytes. F15 medium: The homepage ships substantial unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, label-content-name-mismatch, and list audits; the image primitive also found one image without alt. F16 high: Some controls and links lack usable accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s color-contrast audit failed on the sampled homepage. F17 high: Text/UI contrast does not consistently meet WCAG minimums. |
be-inclusivestructure-and-focus | issues | high | The focused first link had no outline or shadow, and Lighthouse reported structural/list accessibility failures. F18 high: Focus visibility and document structure need repair. |
be-inclusivelegible-text | pass | high | Desktop captures show readable 14–24 px Japanese text with clear spacing and no clipping at the intended desktop width. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360 px, content remains 1038 px wide with 678 px overflow; Lighthouse failed meta-viewport/target-size and the mobile account panel is mostly beyond the viewport. F19 critical: Narrow reflow fails and controls fall below recommended target size. |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices score was 1.0 and did not report console-error or uncaught-exception failures. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 29 of 36 images without width/height and 12 oversized relative to display; Lighthouse failed unsized-images and image-delivery. F20 medium: Many images omit intrinsic dimensions or are oversized. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0 with no deprecated API, notification, geolocation, or paste-prevention failure. |
be-discoverabletitle-and-description | pass | high | DOM probe found a descriptive Japanese title and non-empty meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport meta, and a permissive route-aware robots.txt were present; Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | issues | high | The Japanese page links to many language hosts, but the head probe found no link[hreflang]; sitemap.xml returned 404. Canonical and robots were otherwise present. F21 low: Localized variants are not connected with hreflang metadata. |
be-discoverablestructured-and-shareable-metadata | issues | high | The probe found no JSON-LD and no Open Graph properties despite a public, indexable content catalogue. F22 low: The homepage lacks structured and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | CSP is limited to frame-ancestors; X-Content-Type-Options and Referrer-Policy are absent. Two first-party cookies lack Secure and the settings cookie is SameSite=None. F23 high: Transport is HTTPS, but CSP and cookie protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 118 of 145 requests and 1.62 of 1.74 MB on non-page origins, including Google account code and advertising/CDN origins; trackers inventory found 16 third-party origins. Some are organizational CDNs, but the total cross-origin surface is still large. F24 high: The anonymous homepage has a broad third-party/network footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | The sampled signup surface advertises email and federated entry; no WebAuthn/passkey capability was exposed in the rendered flow. No permission prompt fired on load. F25 low: Public account entry points do not expose phishing-resistant authentication. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and clickjacking protection are present, but Referrer-Policy and nosniff are absent; Permissions-Policy only declares two client-hint features, and CSP only supplies frame-ancestors. F26 medium: Defensive policy coverage is narrow. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 83% rendered-word coverage in 414,924-byte raw HTML, with title, H1, and description present and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | All five representative routes rendered meaningful HTML and navigation without blank shells; invalid-route recovery remained functional. |
be-resilientoffline-and-installable | not-applicable | high | The core product is streamed network media and is intrinsically online; although a manifest and service-worker controller exist, offline playback is not a meaningful requirement. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberate nonexistent route produced a clear localized not-found state with explanation and links back home/support. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Japanese host declares html lang=ja and renders translated navigation/content; language-switch links expose many localized hosts. |
be-internationalisedlocale-aware-data | not-applicable | high | The sampled public templates did not present dates, currencies, or other locale-sensitive values requiring formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled or time-zone-sensitive event data appeared on the sampled public templates. |
be-trustworthyno-dark-patterns | pass | high | The observed consent surface gives accept and reject equal-sized adjacent controls and links to cookie/privacy policies; no preselected paid commitment was observed. |
be-trustworthyhumane-error-handling | pass | high | No editable account fields were exposed before selecting an explicit signup method; the sampled search and 404 states provide clear outcomes rather than blame. |
be-trustworthytrustworthy-input-assistance | pass | high | The visible search field has an explicit Japanese accessible label and purposeful autocomplete=off for query suggestions. |
be-trustworthysafe-commercial-and-account-flows | pass | high | No purchase or subscription was initiated; public signup labels its account action as free and did not expose a hidden paid commitment in the sampled state. |
be-sustainableoptimised-assets | issues | high | The image audit found 12 oversized images, 16 legacy-format URLs, 29 missing dimensions, and 8 below-fold images without lazy loading. F27 medium: Image delivery wastes bytes and risks extra layout work. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 145 requests and 61 scripts; Lighthouse identified unused CSS/JS and legacy JavaScript. F28 medium: The initial page executes more script and requests than its listing task needs. |
be-sustainablethird-party-and-media-budget | issues | high | Cross-origin resources account for 1.62 MB of the 1.74 MB homepage transfer; script alone is about 1.02 MB before the user starts a video. F29 high: Third-party code dominates transferred bytes before media playback begins. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional agent surface was present; this emerging capability is optional for this public media catalogue. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the sampled paths required on-device language-model or summarisation inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | After ten search suggestion open/clear cycles, snapshot self size was 38.5 MB versus 36.6 MB baseline (+5%); native node count slightly fell, so this bounded sample does not show runaway retained growth. |
be-memory-efficientbounded-footprint | pass | low | Heap snapshots were 36.6–38.5 MB self size for a 1,827-element media catalogue page, proportionate to the rendered content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | No Detached* constructor appeared among top retained constructors and native-node count did not grow across the two summaries; confidence is limited because snapshots used fresh sessions. |
Provenance
Canonical report: results/atomic/reports/0323-jp_xhamster_com.json
Report SHA-256: 4b1f12edf0cc345e30341088fc5a440bf6febeb4364173d55942b0eeb69916f2
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/jp_xhamster_com/2026-07-19T23-08-03-827Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/jp_xhamster_com/2026-07-19T23-08-03-827Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.