Manifest position 653 · CrUX rank bucket 1000
https://hi.xhamster1.desi
Coverage complete
All 58 catalog checks were judged. Repeated 503 responses are site findings; Lighthouse was unavailable, so raw CDP, trace, layout, axe, DOM and custom probes supplied equivalent evidence.
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 | Default light-condition and emulated dark screenshots remain visually identical dark surfaces; the captured CSS has only two color-scheme media matches and the rendered surface does not retint. F01 low: Theme does not follow the OS color preference |
respect-user-preferencesrespects-reduced-motion | issues | high | Eight animations remained running with 2000 ms durations under prefers-reduced-motion: reduce, and no reduced-motion CSS rule was found. F02 medium: Motion continues under reduced-motion preference |
respect-user-preferencesrespects-contrast | issues | high | No prefers-contrast or forced-colors rule was found; axe reported serious contrast failures including 1.75:1 and 2.15:1 text combinations. F03 high: Contrast preferences and baseline contrast are not supported |
implement-natural-interactionsview-transitions | issues | medium | Navigation between homepage, categories, signup, and failure surfaces is abrupt, and no same-document or cross-document view-transition rule was found. F32 low: Navigation changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No decorative scroll-linked animation was present, so a scroll timeline is not needed. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | The audited listing, search, and signup surfaces do not expose a swipe, drag, carousel, or other physical-gesture task. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The page has a long feed and persistent navigation, but no scroll-state query or other state-aware chrome behavior was found in the captured CSS. F04 low: Long-page navigation does not adapt to scroll state |
provide-guided-navigationanchored-positioning | not-applicable | high | The only observed overlay was a centered consent modal, not an element anchored to a trigger or edge-sensitive target. |
provide-guided-navigationdirects-attention | pass | high | The H1, active Video tab, search control, categories, and content cards provide clear visual and semantic attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A large consent overlay appears before interaction and obscures most of the homepage, category page, signup page, and 404 content. F05 high: Consent interrupts every primary path |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The visible consent overlay is absent from dialog, role=dialog, aria-modal, popover, and details inventories, indicating custom non-semantic overlay handling. F06 medium: Consent overlay is not exposed as a semantic dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | The fixed top navigation, 200 px sidebar, banners, and blocking consent surface leave a minority of the mobile viewport for primary content. F07 medium: Persistent chrome crowds out content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360 px visual viewport the document reports 1030 px content width and 670 px horizontal overflow, clipping most content. F08 high: Mobile layout overflows by 670 px |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No @container rule was present in the captured CSS, and the desktop feed/sidebar composition remains 1030 px wide on mobile. F09 high: Components retain desktop geometry on mobile |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first visible link receives outline-style none and no box-shadow after focus, leaving keyboard focus without a visible indicator. F10 high: Keyboard focus is visually hidden |
support-core-task-successclear-purpose-and-primary-action | pass | high | The Hindi H1 identifies trending free videos, search is prominent, and content/navigation labels make the page purpose clear. |
support-core-task-successprimary-flow-completion | issues | high | Submitting the prominent search form with “test” navigated to /?q=test but returned a generic 503 page rather than results. F11 high: Primary search flow ends in 503 |
support-core-task-successclear-system-state-and-recovery | issues | high | Failure states are a bare nginx 503 with no Hindi explanation, retry control, navigation, or recovery action. F12 high: Failure states provide no recovery |
be-fast-and-stablegood-core-web-vitals | pass | high | The successful trace measured FCP/LCP 1511.67 ms and TBT 127.54 ms; layout observation measured CLS 0. |
be-fast-and-stablevisual-stability | pass | medium | The measured load had CLS 0 with no recorded shifts, although missing image dimensions are reported separately as an asset hygiene risk. |
be-fast-and-stableefficient-main-thread | pass | medium | The trace found two long tasks, longest 150.56 ms, with 127.54 ms total blocking time, acceptable for this load but worth monitoring. |
be-fast-and-stableefficient-resource-delivery | issues | high | Thirteen images were over 2x displayed size, 29 lacked dimensions, and a successful load initiated 136 resources across many origins. F13 medium: Resource delivery wastes image bytes |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | low | The captured successful page used deferred scripts and no direct duplicate-code signal was observed in the authored resource inventory; confidence is low because Lighthouse code coverage was unavailable. |
be-inclusivenames-roles-labels | issues | high | axe found serious aria-hidden-focus, prohibited ARIA, and nested-interactive violations; the custom probe also found unnamed controls and image links. F14 high: Serious names, roles, and nesting defects |
be-inclusivesufficient-contrast | issues | high | Axe reported serious WCAG AA contrast failures, including 1.75:1 secondary banner text and repeated 3.29:1 metadata text. F15 high: Text contrast falls below WCAG AA |
be-inclusivestructure-and-focus | issues | high | Axe found non-unique and nested landmarks, while computed focus styling was outline none with no replacement shadow. F16 high: Landmarks and focus structure impede navigation |
be-inclusivelegible-text | pass | medium | Primary headings and card titles are visibly legible at desktop size with clear weight and spacing; contrast defects are recorded separately. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The page declares a scalable viewport but does not reflow: content remains 1030 px wide in a 360 px visual viewport. F17 high: The interface does not reflow at mobile width |
follow-best-practicesno-console-errors | issues | high | A successful page load logged a 503 for the search-history API and an identity-provider sign-in error. F18 medium: Successful loads still emit console errors |
follow-best-practicessound-document-and-assets | issues | high | Doctype, UTF-8, and viewport are sound, but 29 of 36 images lack explicit width/height and one image lacks alt text. F19 medium: Image asset markup lacks dimensions and complete alternatives |
follow-best-practicesbrowser-platform-hygiene | pass | medium | No on-load geolocation or notification prompt, paste prevention, or deprecated interactive API was observed; the document uses standard HTML controls for search. |
be-discoverabletitle-and-description | pass | high | A descriptive Hindi title and meta description are present in both rendered and raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Raw content is crawlable, but the mobile-friendly part fails with 670 px horizontal overflow at a 360 px viewport. F20 high: Crawlable page is not mobile-friendly |
be-discoverablecanonical-and-indexing-signals | pass | medium | The entry document returned 200, exposes a canonical URL and robots.txt, and has no noindex signal; the sitemap endpoint was intermittently 503 but indexing of the entry page remains signaled. |
be-discoverablestructured-and-shareable-metadata | issues | high | No JSON-LD and no Open Graph metadata were present on the representative homepage. F21 medium: Pages lack structured and social metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used and no client secret was found, but CSP, HSTS, nosniff, frame protection, Referrer-Policy, and Permissions-Policy are all absent. F22 high: Core security headers are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before consent resolution, a successful load initiated 136 resources including collector, Google, tsyndicate, flixcdn, and multiple CDN origins. F23 high: Third-party requests begin before consent resolution |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No browser permission prompt fired on load; account entry is user-initiated from signup/login controls rather than forced. |
be-private-and-securedefensive-browser-policies | issues | high | All defensive policy headers were absent; settings and CSRF cookies were reported without Secure, and settings used SameSite=None. F24 high: Cookies and browser policies are weak |
be-resilientprogressive-enhancement | pass | high | The server returns substantive HTML: 67% of rendered content words, title, H1, and description survive without JavaScript, and it is not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | Normal route and API requests intermittently return 503, producing brittle runtime behavior despite an otherwise rendered shell. F25 high: Runtime dependencies fail intermittently |
be-resilientoffline-and-installable | not-applicable | medium | Offline media playback or installation is not necessary for the public streaming/listing task; service-worker support exists but offline behavior was not treated as a requirement. |
be-resilientnetwork-and-http-failure-states | issues | high | Search, signup, category, manifest, sitemap, and unknown-route requests intermittently returned a bare nginx 503 with no retry or stale-data fallback. F26 high: Network and HTTP failures are not resilient |
be-internationalisedlang-dir-and-logical-properties | issues | medium | The Hindi document has lang=hi, but captured CSS contains roughly 173 physical left/right declarations and only one logical-property match, limiting robust bidirectional adaptation. F27 medium: Localized CSS relies heavily on physical directions |
be-internationalisedlocale-aware-data | pass | medium | Navigation, consent, headings, category names, and counts are presented consistently in the Hindi locale. |
be-internationalisedtime-zone-correctness | not-applicable | high | No date, schedule, recurring event, or time-zone-sensitive value appears in the audited paths. |
be-trustworthyno-dark-patterns | pass | medium | Accept and reject are presented side by side with equal visual weight, and the copy links to cookie and privacy policies. |
be-trustworthyhumane-error-handling | issues | high | The failed primary search returns an infrastructure error rather than contextual, humane language and a recovery action. F28 high: Infrastructure errors are not humane |
be-trustworthytrustworthy-input-assistance | issues | medium | The prominent search field explicitly sets autocomplete=off, preventing useful browser assistance for repeated searches. F29 low: Search disables browser input assistance |
be-trustworthysafe-commercial-and-account-flows | pass | low | The signup entry is explicit, uses an email sign-up action, and does not expose hidden pricing or forced subscription in the inspected entry state; deeper authenticated flows were not available. |
be-sustainableoptimised-assets | issues | high | Thirteen images are oversized, 15 use legacy formats, 29 omit intrinsic dimensions, and eight below-fold images are not lazy-loaded. F30 medium: Media assets are not consistently optimized |
be-sustainableno-wasteful-work | pass | medium | The trace showed only two bounded long tasks and the repeated scroll test ended around 24.6 MB used JS heap with 1,916 DOM nodes; no runaway idle work was observed. |
be-sustainablethird-party-and-media-budget | issues | high | The page initiated 136 resources across at least 13 origins, including ad/identity origins, while multiple thumbnails were oversized or legacy-format. F31 medium: Third-party and media footprint is broad |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public media browser exposes no transactional agent task that requires WebMCP tools; conventional crawlable links and search remain the appropriate interface. |
be-agent-readyon-device-inference | not-applicable | high | The page has no summarisation, translation-generation, or other user task that requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Across successful fresh sessions, used JS heap was about 22.7 MB at baseline and 24.6 MB after ten end-to-end scroll cycles; this bounded change does not show a retained-growth leak. |
be-memory-efficientbounded-footprint | pass | medium | The exercised page used about 24.6 MB JS heap with 1,916 live DOM nodes after repeated scrolling, proportionate to a media feed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | The post-scroll heap summary contains no Detached constructor entry and the exercised state remained at 1,916 DOM nodes and 12 animations; confidence is low because listener instrumentation was unavailable. |
Provenance
Canonical report: results/atomic/reports/0653-hi_xhamster1_desi.json
Report SHA-256: 5fdb03012ec1e626b837e5ea72a25cf55c3d2339579466187fd9dcb879eec1c5
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster1_desi/2026-07-22T04-15-11-593Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/hi_xhamster1_desi/2026-07-22T04-15-11-593Z
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.