Manifest position 71 · CrUX rank bucket 1000
https://id.xhname.com
Coverage complete
Coverage-complete atomic audit of anonymous public browsing, listing, detail, signup, and recovery archetypes. Authenticated playback/account/payment states were not entered.
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 | pass | high | Computed CSS inspection under prefers-color-scheme: dark found explicit dark and light media-query token sets; the dark screenshot remained usable. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, getAnimations() still reported eight running shimmer animations, each with a 2000 ms duration. F001 medium: Motion preference is ignored by loading shimmers |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found 13 insufficient-contrast nodes, including 2.15:1 and 1.75:1 text in the age banner; no prefers-contrast rules were found. The forced-colors capture attempt received an external 503. F002 high: Key text fails contrast requirements |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition CSS or route-transition implementation; representative navigation is a full abrupt document change. F003 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, carousel, or reveal animation was present on the representative pages, so there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | pass | high | DOM/CSS inspection found no custom pointer-drag gesture implementation fighting platform scrolling; browsing uses native links and scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Home and category screenshots show large static header, banner, and side navigation chrome; CSS inspection found no scroll-state query or progress treatment. F004 low: Navigation chrome does not respond to scroll |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-sensitive transient menu was present in the exercised core paths; the cookie and signup overlays are modal surfaces, not anchored popovers. |
provide-guided-navigationdirects-attention | issues | high | Representative route changes provide no transition, focus handoff, or destination highlight; screenshots show abrupt replacement while static chrome dominates. F005 low: Navigation does not cue destination changes |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial desktop viewport is obscured by a large cookie modal before interaction, while age-verification and promotional banners also occupy the underlying first viewport. F006 high: Consent UI obscures the initial content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found the cookie surface as a custom div.experimentalModalContainer with no dialog element or role=dialog; the page had zero dialog elements. F007 high: Cookie modal is a non-semantic custom div |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop/mobile screenshots show stacked header, age-verification banner, sale banner, persistent category rail, inline promotions, and consent UI competing with the media content. F008 medium: Promotional and navigation chrome crowds the content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360 px visual viewport, layout reported scrollWidth 1036 and 676 px horizontal overflow; the mobile screenshot visibly clips the content column. F009 critical: Mobile layout remains desktop-width |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Computed layout at mobile retained a 1024 px body/main and inspection found no @container rules, so reused page chrome does not adapt to its available container. F010 high: Components do not adapt to their container |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused search input matched :focus-visible but computed outline was none and box-shadow none; Lighthouse also found two undersized/obscured targets. F011 high: Keyboard focus and touch targeting are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, category, detail, and signup surfaces have descriptive titles/headings and visible next actions such as category links, media cards, Start, and sign-up providers. |
support-core-task-successprimary-flow-completion | pass | high | The anonymous browse journey reaches a media detail and clearly states that viewing requires age verification and login, with a Start action; signup exposes provider/email choices and terms. |
support-core-task-successclear-system-state-and-recovery | pass | high | A synthetic missing route rendered an Indonesian not-found explanation and a clear home link; gated media explicitly explains the required login/age state. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.0 s (outside the good <=2.5 s range) and FCP 2.9 s; CLS was 0 and TBT 0 ms in that run. F013 medium: Largest content paint misses the good range |
be-fast-and-stablevisual-stability | pass | high | Both layout observation and Lighthouse measured CLS 0 during the observation windows, with no recorded layout-shift entries. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 170.75 ms, and 145.04 ms total blocking time; mobile layout observation independently recorded 62 ms and 144 ms tasks. F014 medium: Long main-thread tasks occur after load |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimated 1220 ms savings from five render-blocking stylesheets and 115 KiB from cache lifetime improvements; HAR recorded 140 requests. F015 high: Render-blocking and cache delivery delay content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 58 KiB unused CSS, 26 KiB unused JS, and 11 KiB legacy JavaScript; HAR recorded 61 scripts and about 1.01 MB script transfer. F016 medium: Unused and legacy code is shipped |
be-inclusivenames-roles-labels | issues | high | Lighthouse found one unnamed button, two unnamed links, nine label/name mismatches, and invalid list semantics; image inspection found one missing alt. F017 high: Controls and links lack robust accessible names/roles |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 13 contrast failures, including age-banner text at 2.15:1 and 1.75:1 and metadata text at 3.29:1. F018 high: Text contrast is insufficient |
be-inclusivestructure-and-focus | issues | high | Lighthouse found malformed list structure and inappropriate roles; direct keyboard-focus probing found no visible outline or shadow on the focused search field. F019 high: Focus and document structure are unreliable |
be-inclusivelegible-text | issues | high | At 360 px the page keeps a 1036 px content width, clipping headings, navigation, cards, and signup content outside the viewport and harming readable reflow. F020 high: Text and controls do not reflow on narrow screens |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse reports user-scalable=no in the audited mobile viewport and two target-size failures; video DOM exposed no caption tracks in the gated player state. F021 high: Zoom, target size, and media alternatives are incomplete |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices scored 1.0 and reported no console-error or runtime-exception audit failure on the entry page. |
follow-best-practicessound-document-and-assets | issues | high | Document has HTML doctype and UTF-8, but image inspection found 29 of 36 images missing dimensions and 13 oversized; Lighthouse independently found unsized images. F022 medium: Image markup wastes bytes and risks instability |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0; no permission prompt appeared on load, and scripts observed in the head were deferred or async. |
be-discoverabletitle-and-description | pass | high | DOM inspection found a descriptive localized title and a non-empty meta description on the home page; detail and signup titles were also specific. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Links and viewport meta are present and robots permits public pages, but the 360 px layout overflows by 676 px, so the mobile-friendly part fails directly. F023 high: Public pages are not mobile-friendly |
be-discoverablecanonical-and-indexing-signals | issues | high | Home returned 200 and has a canonical, but it points to id.xhamster.com rather than the audited id.xhname.com host; /sitemap.xml returned 404 and no hreflang links were present despite many locale variants. F024 medium: Indexing signals are inconsistent |
be-discoverablestructured-and-shareable-metadata | issues | high | The home page is a rich media listing, but DOM inspection found zero JSON-LD blocks and zero Open Graph tags. F025 medium: Rich pages lack structured/share metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP is only frame-ancestors self; nosniff and Referrer-Policy are missing, and two first-party cookies lack Secure. F026 high: Transport policy and cookies are incompletely hardened |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 116 of 140 requests and 1.60 MB of 1.79 MB transfer on non-page origins; tracker probe enumerated 16 third-party origins including Google accounts and an ad syndication origin. F027 medium: The anonymous page has a broad cross-origin footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but the relevant signup flow exposes Google, X, or email and no passkey/WebAuthn option or navigator.credentials use was observed. F028 medium: Authentication does not expose phishing-resistant sign-in |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and clickjacking defenses are present, but Referrer-Policy and nosniff are absent, CSP lacks script restrictions, and Permissions-Policy only configures UA client hints. F029 high: Browser-enforced defensive policies are weak |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 83% of rendered content represented in raw HTML, with title, H1, and description present and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Cookie choices, login/signup overlays, category browsing, and detail gating all rendered actionable states; the tested 404 provides recovery rather than a broken shell. |
be-resilientoffline-and-installable | pass | high | A valid manifest defines name, start_url, icons, and minimal-ui; an active scoped service worker exists and its source contains cache/fetch/offline handling. |
be-resilientnetwork-and-http-failure-states | pass | high | The representative 404 route renders a localized explanation, technical-help direction, and a direct home recovery link rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Indonesian page declares html lang=id and exposes a broad locale switcher including RTL languages; Indonesian correctly uses default LTR direction. |
be-internationalisedlocale-aware-data | issues | high | Rendered Indonesian copy mixes non-localized abbreviations and English labels such as 108.6M tampilan, More Videos, and Choose your porn category rather than locale-aware Indonesian formatting. F030 medium: Localized pages retain English and non-locale number formatting |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public pages show media durations and counts but no dates, appointments, recurring events, or cross-time-zone data. |
be-trustworthyno-dark-patterns | issues | high | The content list interleaves third-party and subscription promotions with ordinary media cards; screenshots show the sale banner and in-feed commercial content competing with organic results, with weak ad distinction. F031 medium: Commercial cards are weakly distinguished from organic content |
be-trustworthyhumane-error-handling | not-applicable | high | The reachable anonymous forms are search and provider-choice controls with no required user-entered validation flow; no invalid-input state exists to exercise. |
be-trustworthytrustworthy-input-assistance | pass | high | The search input is correctly identified and provider-based signup reduces typed credentials; no address/payment form is present in the anonymous scope requiring further autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Signup states age-verification requirements, terms, privacy use, and public-data implications before account creation; no purchase was initiated in the anonymous scope. |
be-sustainableoptimised-assets | issues | high | Image inspection found 13 oversized images, 15 legacy-format images, 29 missing dimensions, and three without responsive sources. F032 medium: Image assets are oversized or legacy |
be-sustainableno-wasteful-work | issues | high | The home load makes 140 requests including 61 scripts; Lighthouse identifies substantial unused CSS/JS and the trace records long tasks after load. F033 medium: The page ships wasteful work |
be-sustainablethird-party-and-media-budget | issues | high | The page transfers 1.79 MB; 1.60 MB and 116 requests are attributed to non-page origins, with 1.01 MB of scripts and 16 third-party origins. F034 medium: Third-party and script budget is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public media browsing site declares no agent-facing intent; emerging WebMCP capability exposure is not assumed to be required. |
be-agent-readyon-device-inference | not-applicable | high | No page task identified in the representative anonymous journey requires on-device inference; absence is not a failure for this contextual emerging check. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Equivalent heap snapshots after one versus ten login open/close cycles were stable: 36,711,360 bytes/687,985 nodes versus 36,681,499 bytes/687,572 nodes. |
be-memory-efficientbounded-footprint | pass | high | After representative UI initialization the heap was about 36.7 MB with about 688k nodes, proportionate to the media-heavy listing and stable across repeated cycles. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | One-to-ten cycle heap comparison slightly decreased in node count and size, and no Detached* constructor appeared among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0071-id_xhname_com.json
Report SHA-256: 11b8ee5300713402fed6ac5125320c92f7b5250476fa95bbc766ca2462ed64a4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/id_xhname_com/2026-07-18T05-08-27-474Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/id_xhname_com/2026-07-18T05-08-27-474Z
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.