Manifest position 889 · CrUX rank bucket 1000
https://hil.xhamster45.desi
Coverage complete
Coverage-complete audit of four representative archetypes. Explicitly not covered: authenticated account settings, payment/subscription completion, content upload, live chat, and actual video playback because they require credentials, payment, or extended media interaction.
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 | Dark and default screenshots are visually identical, and the CSS probe found no color-scheme preference support. F-001 medium: The fixed dark palette does not follow the system color-scheme preference |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found eight running 2000 ms animations while prefers-reduced-motion: reduce matched, and no reduced-motion CSS was present. F-002 medium: Animations continue when reduced motion is requested |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse measured contrast ratios of 1.75:1 and 2.15:1 in the age banner plus 3.29:1 for view counts; the CSS probe found no prefers-contrast or forced-colors rules. F-003 high: Key text fails contrast requirements and no contrast preference styling exists |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition rules on an MPA with search, login, listing and detail routes. F-004 low: Route and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | medium | DOM and CSS probes found no scroll-linked animation or custom scroll animation handler on the tested feed, so no main-thread scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | medium | The tested listing, search, detail and login surfaces use native scrolling and standard controls; no custom pointer-driven gesture surface was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The desktop and mobile captures show a long feed with static chrome, while the CSS probe found no scroll-state or scroll-timeline implementation. F-005 low: Long listing pages provide no scroll-state feedback |
provide-guided-navigationanchored-positioning | pass | medium | Menus and the centered consent overlay remained visually attached within the tested desktop screenshots; no edge-positioned tooltip drift was observed. |
provide-guided-navigationdirects-attention | issues | high | The CSS probe found no View Transition, scroll marker or highlight implementation across the tested listing, search and detail routes. F-006 low: Navigation changes offer no directional or destination cue |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots of home, search and detail routes show a large centered cookie overlay covering the main content before interaction. F-007 high: A cookie interstitial obscures the primary content on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The overlay is visible in screenshots, but the DOM probe reported zero dialog elements and zero role=dialog elements. F-008 high: The consent overlay is not exposed as a dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | The first desktop viewport contains two navigation bars, an age banner, a sidebar, a cookie interstitial and promotional cards around the feed. F-009 medium: Navigation, banners, sidebars, promos and overlays crowd the content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360 px viewport, layout measured scrollWidth 1032 px and horizontalOverflowPx 672; the screenshot shows most content clipped off-screen. F-010 critical: The mobile page renders a desktop-width layout and overflows by 672 px |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries, and the 360 px capture retains the desktop sidebar and content grid. F-011 medium: Components do not adapt to their available container |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active search button computed to outline none 0px and box-shadow none. F-012 high: Keyboard focus is not visibly indicated |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The first viewport has a descriptive H1 and immediately visible content cards; search, sign-in and viewing actions are clearly labelled. |
support-core-task-successprimary-flow-completion | issues | high | The detail route presents age verification plus the cookie overlay before the player can be reached, adding avoidable modal detours to the primary viewing journey. F-013 medium: Viewing content requires multiple overlapping gates |
support-core-task-successclear-system-state-and-recovery | issues | high | Submitting the empty sign-in form produced no invalid controls and no alert or live-region message; /sitemap.xml produced a generic browser 404. F-014 medium: Invalid sign-in and missing-page states do not provide useful recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.9 s and FCP 2.8 s; the trace measured LCP 2285 ms under a separate desktop run. F-015 high: Mobile LCP is outside the good range |
be-fast-and-stablevisual-stability | pass | medium | Layout observer and Lighthouse both measured CLS 0 with no recorded layout-shift entries. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace recorded two long tasks, 155.5 ms longest and 121 ms total blocking time; Lighthouse measured 0 ms TBT in its mobile run, supporting acceptable main-thread responsiveness. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 144 requests and 1.76 MB transferred, including three parser-inserted VeryHigh-priority stylesheets and a redirect. F-016 medium: The load has a large request graph and render-blocking styles |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 56 KiB unused CSS with 90 to 95 percent waste in two files, plus 26 KiB unused JavaScript. F-017 medium: The page ships avoidable unused CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | Lighthouse identified a visible 40 by 24 button with no text, aria-label, title or label. The username field also lacks a programmatic label. F-018 high: An interactive button has no accessible name |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed the color-contrast audit with ratios as low as 1.75:1 on the age banner and 3.29:1 on metadata. F-019 high: Text and controls have insufficient color contrast |
be-inclusivestructure-and-focus | issues | high | The focused search button had no outline and no box shadow, preventing keyboard users from seeing focus position. F-020 high: Focus is invisible on a primary control |
be-inclusivelegible-text | issues | high | The 360 px screenshot and layout evidence show a 1032 px content canvas clipped into a narrow strip, cutting headings and cards. F-021 high: Mobile clipping prevents comfortable reading |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport allows scaling, but at 360 px the page overflows horizontally by 672 px and leaves content unreachable without two-dimensional scrolling. F-022 high: The experience does not reflow at a narrow mobile width |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console audit passed with no captured console error entries. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 29 of 36 images missing width or height and 13 images more than twice their displayed size. F-023 medium: Most images do not reserve layout space and many are oversized |
follow-best-practicesbrowser-platform-hygiene | pass | medium | Lighthouse best-practices scored 1.0 and BFCache passed; no permission prompt, paste prevention or deprecation warning appeared in tested paths. |
be-discoverabletitle-and-description | pass | medium | DOM probe found a descriptive title and a populated meta description on the public homepage. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | The page has a viewport meta tag, 358 href links, and robots.txt permits the main public surface; Lighthouse SEO passed. |
be-discoverablecanonical-and-indexing-signals | issues | high | The request redirects from xhamster45 to xhamster46, while canonical points to hil.xhamster.desi; hreflang is absent and /sitemap.xml returns 404. F-024 medium: Indexing signals are inconsistent across hosts |
be-discoverablestructured-and-shareable-metadata | issues | high | The DOM probe found zero JSON-LD blocks and no Open Graph properties despite the page representing a rich media listing. F-025 medium: The public listing lacks structured and social metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP only sets frame-ancestors; X-Content-Type-Options and Referrer-Policy are missing. F-026 high: The CSP does not protect script sources and key headers are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 15 third-party origins; HAR attributed 142 of 144 requests and 1.757 MB of 1.758 MB to origins different from the requested host, including an ad request. F-027 high: The initial load has an extensive third-party data surface |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found username/password and Google/X sign-in but no WebAuthn or passkey integration; the password field is tagged new-password on a sign-in form. F-028 medium: Sign-in is password-only and does not expose passkeys |
be-private-and-securedefensive-browser-policies | issues | high | Headers show clickjacking protection and HSTS, but missing nosniff and Referrer-Policy plus a frame-only CSP leave XSS and referrer defenses incomplete. F-029 high: Browser-enforced defenses are incomplete |
be-resilientprogressive-enhancement | pass | medium | Discoverability evidence measured 89 percent raw-HTML content coverage with title, H1 and description present and isJsShell false. |
be-resilientresilient-runtime-behaviour | issues | high | The non-semantic cookie overlay covers primary content on desktop, while the mobile viewport clips the page to a 1032 px desktop canvas. F-030 medium: Custom overlays are fragile across viewports |
be-resilientoffline-and-installable | pass | medium | The page links a complete web manifest and has an active service worker controlling the page, with start_url, icons and minimal-ui display configured. |
be-resilientnetwork-and-http-failure-states | issues | high | The sitemap request returned HTTP 404 and a chrome-error page with no site navigation or recovery path. F-031 medium: Missing resources fall through to a generic browser error |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page declares lang=hil, the BCP 47 code for Hiligaynon, while navigation and content are Hindi transliterated into Latin script; no hreflang alternatives are exposed. F-032 high: The declared language does not match the rendered locale |
be-internationalisedlocale-aware-data | issues | high | View counts use fixed English-style compact notation such as 4.2M and 28.8M on the Hindi-localized page, rather than locale-aware formatting. F-033 medium: Compact numbers are not locale-aware |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, scheduling, stored times or time-zone-sensitive data appeared on the representative listing, search, detail or sign-in surfaces. |
be-trustworthyno-dark-patterns | pass | medium | The consent overlay provides equally prominent accept and reject actions, and the tested sign-in page does not preselect marketing or subscription options. |
be-trustworthyhumane-error-handling | issues | high | Both sign-in fields are not required; submitting empty produced no :invalid field and no alert or live-region error. F-034 high: The sign-in form provides no actionable empty-submit feedback |
be-trustworthytrustworthy-input-assistance | issues | high | Username uses autocomplete=username, but the sign-in password uses autocomplete=new-password instead of current-password; username has no programmatic label. F-035 medium: Sign-in autofill metadata is partly incorrect |
be-trustworthysafe-commercial-and-account-flows | issues | high | The tested account entry offers password and federated sign-in only; no passkey/WebAuthn support was detected. F-036 medium: Account authentication lacks a phishing-resistant option |
be-sustainableoptimised-assets | issues | high | The image audit found 13 oversized images, 15 legacy-format images, 29 missing dimensions and 8 below-fold images without lazy loading. F-037 high: Image delivery wastes bytes |
be-sustainableno-wasteful-work | issues | high | HAR recorded 62 scripts totaling 1.02 MB and 144 total requests, while Lighthouse found substantial unused CSS and JS. F-038 medium: The page starts a large script and third-party workload before user intent |
be-sustainablethird-party-and-media-budget | issues | high | HAR reports 1.757 MB third-party transfer out of 1.758 MB total and 142 third-party requests, with advertising and federated identity loaded immediately. F-039 high: Third-party resources dominate the initial page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent indicates that this adult media site wants to expose action capabilities to AI agents; the emerging WebMCP opportunity is out of scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, authoring or language-model task was present where on-device inference would clearly improve the core experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-feed scroll cycles, heap self-size rose 3.3 percent from 36.38 MB to 37.57 MB while lazy content was exercised; this bounded change does not establish retained unbounded growth. |
be-memory-efficientbounded-footprint | pass | medium | The baseline heap summary was 36.38 MB for a media-rich listing with 36 images and extensive navigation, proportionate to the tested surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-scroll heap summaries listed Detached constructors among top retained populations; the repeated interaction showed no large unbounded heap jump. |
Provenance
Canonical report: results/atomic/reports/0889-hil_xhamster45_desi.json
Report SHA-256: 64710f8e8bcf3070dcddadfa28bcad0aba26d834bedc1e83f6ac02d9b41f4aca
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/hil_xhamster45_desi/2026-07-23T16-05-26-507Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/hil_xhamster45_desi/2026-07-23T16-05-26-507Z
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.