Manifest position 330 · CrUX rank bucket 1000
https://hi.xhamster.desi
Coverage complete
Coverage-complete atomic audit across six representative paths.
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 | The light-preference screenshot remains the same dark palette, while computed html color-scheme is “normal”; the UI does not follow the requested light scheme. F01 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce matched, eight shimmer animations remain running at 2000 ms; the stylesheet probe found no reduced-motion rule. F02 medium: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found no prefers-contrast or forced-colors handling, and Lighthouse reported failing color-contrast nodes. F03 medium: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | Representative home, listing, search and detail route swaps are full document changes; the stylesheet probe found no view-transition CSS. F04 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | issues | high | The long listing uses sticky chrome and animated placeholders, but CSS inspection found no animation-timeline/scroll-timeline while trace and layout show main-thread work. F05 low: Scroll-linked motion (parallax, scrollytelling, entry/exit reveals) uses declarative CSS scroll-driven animations (off main thread) instead of scroll event listeners. |
implement-natural-interactionsphysical-gestures | issues | high | The content grid is a long fixed-width scroller with no observed scroll-snap/overscroll gesture treatment; the 360 px capture exposes a desktop canvas rather than touch-native adaptation. F06 low: Gesture-driven interactions and entry/exit motion feel native (declarative overscroll/scroll-snap, physics-based easing, animating to intrinsic sizes, pull/swipe gestures) rather than fighting the platform with custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Navigation is sticky but remains visually static across the long 4,486 px page; CSS inspection found no scroll-state query or progress feedback. F07 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | issues | high | The site exposes multiple menus/dropdowns, but the CSS probe found no anchor-name, position-anchor or position-try fallback rules. F08 low: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | pass | high | Active navigation is visibly underlined, selected search/category states are highlighted, and the detail heading remains adjacent to its main action. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A large cookie dialog appears on every fresh representative route and obscures the primary heading, results, video and sign-up content. F09 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The visible home consent overlay was not exposed by dialog/[role=dialog]/aria-modal queries, while sign-up uses a role dialog; overlay semantics are inconsistent. F10 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport devotes substantial space to two promotional/age banners, two navigation rows and a permanent sidebar; the content grid is crowded by competing promotions. F11 medium: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360×800 the layout primitive measured scrollWidth 1030 versus clientWidth 360, or 670 px overflow; the screenshot shows a clipped desktop layout. F12 critical: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container/container-type signal, and cards/sidebar retain desktop geometry in the 360 px viewport. F13 medium: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused search input and button compute to outline none and no box-shadow; Lighthouse also fails target-size, and 38 sampled focusables were under 24 px or hidden-sized. F14 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, category, search and detail templates expose descriptive headings, recognizable filters and visible next actions in the first content region. |
support-core-task-successprimary-flow-completion | pass | high | Search reaches a populated results template; selecting a detail exposes the title and a clear “Start” age-verification action, which in turn opens explicit sign-up options. The legal prerequisite is stated before account creation. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 route displays “Page not found”, explanatory copy, popular content and a route back home; age verification and sign-up states state what is required and what happens next. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse reports LCP 4.2 s (failing the good threshold) and FCP 2.5 s; trace corroborates blocking work even though its warm capture LCP was 1.43 s. F15 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | pass | high | The narrow layout observer recorded CLS 0.000006 with one negligible shift; no first-load jump was visible in retained captures. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 183.95 ms, with 177.59 ms total blocking time; layout independently observed tasks of 72 and 172 ms. F16 medium: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found parser-blocking stylesheets and Lighthouse estimates 1,120 ms render-blocking savings plus 119 KiB cache-lifetime savings. F17 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 57 KiB unused CSS and 26 KiB unused JavaScript; HAR transfers 61 scripts totaling 1.06 MB. F18 medium: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails button-name, link-name, label-content-name-mismatch and accessibility-tree audits; image audit also finds one missing alt. F19 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast audit fails visible text/UI combinations. F20 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Programmatic focus leaves the search input/button with no outline or shadow; Lighthouse reports malformed accessibility structure and list semantics. F21 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | At 360 px, headings and cards are clipped outside the visual viewport and the dense sidebar leaves only a narrow content sliver, impairing reading. F22 high: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse reports viewport scaling restrictions and insufficient target sizes; the 360 px layout fails reflow with 670 px overflow. F23 critical: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices score is 1.0 and its console/JavaScript-error audits did not report a failure on the tested load. |
follow-best-practicessound-document-and-assets | issues | high | Document has HTML doctype and UTF-8, but image audit finds 29 of 36 images without width/height; Lighthouse independently fails unsized-images. F24 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices is 1.0 with no reported deprecation, vulnerable-library or prompt-on-load failure; no permission prompt appeared during recon. |
be-discoverabletitle-and-description | pass | high | Home and detail probes expose unique descriptive titles and meta descriptions; raw HTML retains title, H1 and description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO is 1.0; rendered navigation uses real href links, viewport meta exists and robots allows public content routes. |
be-discoverablecanonical-and-indexing-signals | issues | high | Home/detail have canonical URLs and 200 responses, but /sitemap.xml returns 404 and no hreflang links were observed despite many localized host variants. F25 medium: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative video detail has Open Graph tags but no JSON-LD VideoObject (jsonld count 0), limiting rich-entity understanding. F26 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP is only frame-ancestors and two first-party cookies are not Secure; settings is SameSite=None. F27 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR attributes 117/142 requests and 1.64/1.76 MB to 15 third-party origins; generated outbound URLs carry long experiment/session identifiers. F28 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt appeared on load, but the sign-up dialog offers Google, X and email/password only; no passkey/WebAuthn option was observed. F29 medium: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | frame-ancestors and X-Frame-Options are present, but X-Content-Type-Options and Referrer-Policy are missing; CSP lacks broader script/style defenses. F30 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Raw HTML is 441,540 bytes, contains title/H1/meta and 65% of rendered content tokens; the crawler view is populated and is not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | At a 360 px visual viewport, runtime layout remains 1030 px wide and overlays/content are clipped; this is not robust across the supported viewport condition. F31 high: The page behaves robustly at runtime: overlays and menus never get cut off, DOM state survives moves, background work and async dependencies are sequenced and conditional rather than fragile, and initial visibility state is detected correctly. |
be-resilientoffline-and-installable | pass | high | A valid manifest with start_url, scope, icons and minimal-ui is linked, and navigator.serviceWorker.controller is present. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately nonexistent route renders a localized “Page not found” state with explanation, popular content and a home recovery path rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang="hi" is correct, but dir is absent and CSS sampling found 705 physical left/right declarations versus 14 logical-property uses, risking RTL variants. F32 medium: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | issues | high | The Hindi UI renders numerous compact counts with English-style M/K and mixed English labels, despite exposing dozens of locale variants. F33 low: Dates, numbers, currencies, durations and calendar systems are formatted locale-aware (Intl), location-agnostic where stored, and recurring intervals and event differentials are modelled correctly. |
be-internationalisedtime-zone-correctness | not-applicable | high | No dates, schedules, recurring events or user-entered time concepts appear in the representative browsing, search, detail or sign-up flows. |
be-trustworthyno-dark-patterns | pass | high | Consent accept/reject actions have equal visual weight, the age requirement is stated before proceeding, and sign-up discloses data/public-account implications and terms. |
be-trustworthyhumane-error-handling | issues | high | The email sign-up state exposes duplicate text inputs named email without associated labels, autocomplete is off and required is false, making validation and recovery cues ambiguous. F34 high: Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | Email inputs use type=text and autocomplete=off; search also disables autocomplete, while password correctly uses new-password. Account input assistance is therefore incomplete. F35 medium: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Sign-up presents federated and email choices, discloses age requirements, public-data use, terms and privacy before submission, and retains a login alternative. |
be-sustainableoptimised-assets | issues | high | Image audit finds 13 oversized images, 15 legacy-format images, 29 without dimensions and three without responsive sources. F36 medium: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The entry page loads 61 scripts (1.06 MB), keeps eight shimmer animations running even under reduced motion and incurs 177.59 ms blocking time. F37 medium: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party hosts account for 117 requests and 1.64 MB (93% of transfer) before the user engages with media; promotional and recommendation modules dominate the initial surface. F38 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing workflow was declared; the site is an age-gated adult media catalog whose sensitive actions should not be exposed to autonomous agents by default. |
be-agent-readyon-device-inference | not-applicable | high | Search, browsing, playback gating and sign-up do not require summarization or on-device generative inference to complete their core purpose. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll down/up cycles, heap self size was 37.97 MB versus 37.13 MB baseline (+2.3%) and node count +2.1%; no unbounded growth is demonstrated by this bounded exercise. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap self size is 37.13 MB for a media-rich grid with 36 rendered images and extensive navigation; the measured footprint is substantial but proportionate and remained below 40 MB post-exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary reports a Detached* constructor among retained constructor populations, and repeated scrolling increased total heap only modestly rather than showing runaway listener/timer retention. |
Provenance
Canonical report: results/atomic/reports/0330-hi_xhamster_desi.json
Report SHA-256: f12981a923c01fde3fc3748de87ce354bd1f0889f6cdf2839cc1de0d948be8b1
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster_desi/2026-07-19T23-55-28-132Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster_desi/2026-07-19T23-55-28-132Z
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.