Manifest position 740 · CrUX rank bucket 1000
https://hi.xhamster46.desi
Coverage complete
Atomic coverage complete across five representative paths; playback, payment, authenticated account settings, uploads, and post-signup submission were intentionally not exercised.
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 | Evidence linked to F01: Under emulated dark preference the page stays on its fixed dark theme, while computed `color-scheme` is `normal`; the dark and default screenshots are effectively identical. F01 medium: Site theme does not declare or adapt the browser color scheme |
respect-user-preferencesrespects-reduced-motion | issues | high | Evidence linked to F02: The reduced-motion probe reports eight running `shimmer-56cf2` animations at 2,000 ms while `prefers-reduced-motion: reduce` is active. F02 medium: Loading shimmer continues under reduced-motion |
respect-user-preferencesrespects-contrast | issues | high | Evidence linked to F11: Lighthouse reports 13 color-contrast failures and one link-in-text-block failure; no prefers-contrast handling was found in the captured CSS. F11 high: Text and links fail contrast requirements |
implement-natural-interactionsview-transitions | issues | high | Evidence linked to F03: Rendered DOM/CSS contains no view-transition usage although the site has many cross-document navigation paths; detail/category changes are abrupt. F03 low: Route changes have no view-transition treatment |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS inspection finds no main-thread scrollytelling effect; trace records only two load long tasks and ordinary scrolling remains native. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, drag-to-dismiss, carousel, or other physics-based gesture is part of the inspected core browsing journey. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots show persistent header/sidebar navigation and selected-section styling as content scrolls. |
provide-guided-navigationanchored-positioning | pass | medium | Navigation controls remain visually attached to their triggers in desktop and narrow captures; no drifting overlay was observed. |
provide-guided-navigationdirects-attention | pass | high | Red active-tab underlines, headings, and card hierarchy consistently direct attention to the current section. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Evidence linked to F04: Desktop capture shows a large consent surface covering the content and controls before interaction; it is also present in the crawler/no-JS view. F04 high: Consent interstitial obscures the primary content on arrival |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Evidence linked to F05: A visible modal dominates the initial screenshot, but the DOM probe finds no `<dialog>`, `[role=dialog]`, or `[aria-modal=true]` on the homepage. F05 high: The consent overlay is not exposed as a semantic dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | Evidence linked to F04: Desktop capture shows a large consent surface covering the content and controls before interaction; it is also present in the crawler/no-JS view. F04 high: Consent interstitial obscures the primary content on arrival |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Evidence linked to F06: Mobile layout reports 1,030 px content width against a 360 px visual viewport, 670 px horizontal overflow. Homepage, category, detail, and signup captures all clip primary content offscreen. F06 critical: Primary templates are fixed-width and unusable at 360 px |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Evidence linked to F06: Mobile layout reports 1,030 px content width against a 360 px visual viewport, 670 px horizontal overflow. Homepage, category, detail, and signup captures all clip primary content offscreen. F06 critical: Primary templates are fixed-width and unusable at 360 px |
adapt-to-the-form-factorinput-modality-aware | issues | high | Evidence linked to F09: Computed focus styles for search/login buttons report no outline, 53 visible controls are under 24 px in one dimension, and Lighthouse fails target-size. F09 high: Interactive controls have weak keyboard focus and undersized targets |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage H1 and media grid clearly identify the discovery task; search and category navigation are prominent. |
support-core-task-successprimary-flow-completion | pass | high | The audited home -> detail path reaches a video detail/verification surface; signup reaches clearly labelled provider/email choices. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 route returns HTTP 404 and renders a Hindi “page not found” explanation, support suggestion, and popular-video recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Evidence linked to F07: Lighthouse reports 4.5 s LCP. HAR records 140 requests and 1.80 MB transferred, including 62 scripts/1.06 MB; Lighthouse estimates 1,130 ms render-blocking savings and trace records 145 ms TBT. F07 high: Loading performance misses the LCP target and ships a large script chain |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.0014 on desktop and 0 on mobile during the capture window. |
be-fast-and-stableefficient-main-thread | issues | high | Evidence linked to F07: Lighthouse reports 4.5 s LCP. HAR records 140 requests and 1.80 MB transferred, including 62 scripts/1.06 MB; Lighthouse estimates 1,130 ms render-blocking savings and trace records 145 ms TBT. F07 high: Loading performance misses the LCP target and ships a large script chain |
be-fast-and-stableefficient-resource-delivery | issues | high | Evidence linked to F07, F08: Lighthouse reports 4.5 s LCP. HAR records 140 requests and 1.80 MB transferred, including 62 scripts/1.06 MB; Lighthouse estimates 1,130 ms render-blocking savings and trace records 145 ms TBT. Image audit finds 29/36 images without width/height, 14 oversized, 14 legacy-format results, and eight below-fold images not lazy loaded. F07 high: Loading performance misses the LCP target and ships a large script chain F08 medium: Media cards waste bytes and omit intrinsic dimensions |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Evidence linked to F07: Lighthouse reports 4.5 s LCP. HAR records 140 requests and 1.80 MB transferred, including 62 scripts/1.06 MB; Lighthouse estimates 1,130 ms render-blocking savings and trace records 145 ms TBT. F07 high: Loading performance misses the LCP target and ships a large script chain |
be-inclusivenames-roles-labels | issues | high | Evidence linked to F10: Lighthouse fails button-name, label/content-name mismatch, list structure, and accessibility-tree audits; the probe also finds an unlabeled category filter input. F10 high: Accessible names and semantic structure contain failures |
be-inclusivesufficient-contrast | issues | high | Evidence linked to F11: Lighthouse reports 13 color-contrast failures and one link-in-text-block failure; no prefers-contrast handling was found in the captured CSS. F11 high: Text and links fail contrast requirements |
be-inclusivestructure-and-focus | issues | high | Evidence linked to F09, F10: Computed focus styles for search/login buttons report no outline, 53 visible controls are under 24 px in one dimension, and Lighthouse fails target-size. Lighthouse fails button-name, label/content-name mismatch, list structure, and accessibility-tree audits; the probe also finds an unlabeled category filter input. F09 high: Interactive controls have weak keyboard focus and undersized targets F10 high: Accessible names and semantic structure contain failures |
be-inclusivelegible-text | pass | high | Screenshots show readable high-size headings/body copy with clear spacing on the correctly reflowing 404 surface. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Evidence linked to F12: Lighthouse fails the meta-viewport zoom audit and target-size; independent 360 px captures show severe clipping instead of reflow. F12 high: Zoom/reflow and touch accessibility fail together |
follow-best-practicesno-console-errors | pass | high | Lighthouse console-errors audit passed with zero items. |
follow-best-practicessound-document-and-assets | issues | high | Evidence linked to F08: Image audit finds 29/36 images without width/height, 14 oversized, 14 legacy-format results, and eight below-fold images not lazy loaded. F08 medium: Media cards waste bytes and omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices score is 1.0; no permission prompt, deprecated interaction, or console error was observed. |
be-discoverabletitle-and-description | pass | high | Rendered and raw HTML contain a Hindi title, H1, and descriptive meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Evidence linked to F06: Mobile layout reports 1,030 px content width against a 360 px visual viewport, 670 px horizontal overflow. Homepage, category, detail, and signup captures all clip primary content offscreen. F06 critical: Primary templates are fixed-width and unusable at 360 px |
be-discoverablecanonical-and-indexing-signals | issues | high | Evidence linked to F13: robots.txt is available, but `/sitemap.xml` returns 404; the canonical points to a different hostname (`hi.xhamster.desi`) than the audited host. F13 medium: Indexing metadata is incomplete for a large catalogue |
be-discoverablestructured-and-shareable-metadata | issues | high | Evidence linked to F14: The rendered probe finds zero JSON-LD blocks and zero Open Graph tags despite a content-heavy media catalogue. F14 medium: Shareable and structured metadata is absent on the entry page |
be-private-and-securesecure-transport-and-headers | issues | high | Evidence linked to F15: Headers lack `X-Content-Type-Options` and `Referrer-Policy`; CSP is only `frame-ancestors`; two first-party cookies are not Secure and `settings` uses SameSite=None. F15 high: Security headers and cookies leave avoidable gaps |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Evidence linked to F16: Tracker/network captures observe 14 third-party origins and 117 third-party requests transferring 1.69 MB on initial load, while the consent interstitial is still awaiting a choice. F16 high: Third-party activity occurs before a consent decision |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Evidence linked to F17: The signup surface exposes Google, X, and email choices, while the inspected DOM has no WebAuthn/passkey affordance. No permission prompt fired on load. F17 medium: Account entry offers federated sign-in but no modern phishing-resistant option |
be-private-and-securedefensive-browser-policies | issues | high | Evidence linked to F15: Headers lack `X-Content-Type-Options` and `Referrer-Policy`; CSP is only `frame-ancestors`; two first-party cookies are not Secure and `settings` uses SameSite=None. F15 high: Security headers and cookies leave avoidable gaps |
be-resilientprogressive-enhancement | issues | high | Evidence linked to F18: Discoverability finds 63% rendered-word coverage without JavaScript; the crawler capture adds a prominent JavaScript-required warning and still shows the consent surface. F18 medium: Core content degrades noticeably without JavaScript |
be-resilientresilient-runtime-behaviour | pass | high | Consent, navigation, account dialog, and 404 state all render without console/runtime failure. |
be-resilientoffline-and-installable | pass | high | A valid manifest (name, start URL, icons, display) and active service worker registration were observed. |
be-resilientnetwork-and-http-failure-states | pass | high | A real unknown URL returns 404 and a clear, linked recovery page rather than a blank/error shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang="hi" and renders Hindi navigation/content; no bidi-sensitive RTL claim is made. |
be-internationalisedlocale-aware-data | pass | high | The Hindi host localises titles, navigation, legal copy, and UI labels and exposes alternate locale hosts. |
be-internationalisedtime-zone-correctness | not-applicable | high | No date, event scheduling, or time-zone-sensitive value appears in the representative public paths. |
be-trustworthyno-dark-patterns | issues | high | Evidence linked to F19: The page asks users to accept/reject cookies, yet HAR/trackers record substantial third-party traffic before either choice; this makes the stated control less effective. F19 medium: Consent choice and pre-consent loading undermine trustworthy defaults |
be-trustworthyhumane-error-handling | not-applicable | high | No editable personal-data form was exposed before choosing an identity provider/email route, and no data was submitted during this non-invasive audit. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, credential, or profile fields were exposed in the inspected first sign-up step. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The signup dialog identifies provider/email choices and discloses age verification, terms, privacy, and public-data implications before submission. |
be-sustainableoptimised-assets | issues | high | Evidence linked to F08: Image audit finds 29/36 images without width/height, 14 oversized, 14 legacy-format results, and eight below-fold images not lazy loaded. F08 medium: Media cards waste bytes and omit intrinsic dimensions |
be-sustainableno-wasteful-work | pass | high | Trace found two bounded load tasks and no continuing idle long-task activity in the observed window. |
be-sustainablethird-party-and-media-budget | issues | high | Evidence linked to F16: Tracker/network captures observe 14 third-party origins and 117 third-party requests transferring 1.69 MB on initial load, while the consent interstitial is still awaiting a choice. F16 high: Third-party activity occurs before a consent decision |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public media catalogue exposes no declared agent-facing task or transactional capability; WebMCP is therefore contextual and not required for this audit scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, translation, generation, or other inference feature is part of the inspected site purpose. |
be-memory-efficientno-leak-under-repeated-interaction | issues | high | Evidence linked to F20: Heap summary rises from 681,854 nodes/36.57 MB to 748,416 nodes/39.91 MB after ten top-to-bottom scroll cycles. Lazy content may explain part of the 9% growth, so confidence is low. F20 low: Retained heap grows after repeated feed traversal |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is 36.57 MB for a media-rich listing; post-scroll is 39.91 MB, still bounded within the observed session. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary surfaced Detached* constructors among its top retained constructors; no runaway task activity was observed. |
Provenance
Canonical report: results/atomic/reports/0740-hi_xhamster46_desi.json
Report SHA-256: 127537c49c4d6867aa0799d4d7d37711df797c8a1d1ccad7a4204a77a4350586
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster46_desi/2026-07-22T19-08-00-600Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster46_desi/2026-07-22T19-08-00-600Z
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.