Manifest position 744 · CrUX rank bucket 1000
https://xhamster.desi
Coverage complete
Coverage-complete report-mode audit of seven representative public paths. Authenticated account management, paid checkout, creator upload, live chat, actual age-verification vendor completion, and explicit media playback were not covered because they require credentials/payment/sensitive interaction or duplicate other templates.
Attempts
2 / 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 | Light and dark emulation screenshots are visually equivalent and the platform probe reports computed colorScheme “normal”. F01 medium: The site does not follow the system color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, eight animations remain running with 2000 ms durations. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse reports contrast ratios as low as 1.75:1 on the age-verification banner and 3.29:1 on view counts; the high-contrast capture does not introduce a stronger theme. F03 high: Important controls and text do not survive enhanced-contrast needs. |
implement-natural-interactionsview-transitions | issues | high | The platform supports document.startViewTransition, but the CSS/DOM probe found no view-transition rules across the entry surface. F04 low: Route and state changes do not use authored View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or other scroll-linked animation was observed on the representative templates; there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-reveal, carousel drag, or other gesture-only core interaction was present in the audited public paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 4,486 px tall, while the platform probe found no scroll-timeline or container-query support and the mobile capture retains desktop-style fixed chrome. F05 low: The long listing has static chrome without scroll-state feedback. |
provide-guided-navigationanchored-positioning | issues | high | Rendered CSS inspection found physical left/right positioning throughout and no anchor-positioning declarations; overlays are custom fixed elements. F06 low: Menus and overlays rely on physical positioning rather than anchor-aware placement. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show persistent active navigation underlines, clear page headings, selected search tabs, and visible category/filter state. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Homepage, categories, search, video, and signup captures all show the same 780×493 fixed consent layer covering the primary content before interaction. F07 high: A full-screen consent overlay obscures every audited content route on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The overlay probe found the visible fixed consent surface with no role or aria-modal; the page has zero dialog and popover elements. F08 high: The consent modal lacks dialog semantics. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop captures stack two navigation rows, age verification, a seasonal promotion, side navigation, partner promotions, and consent over the content grid. F09 medium: Promotional chrome competes heavily with primary content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive reports scrollWidth 1024, visualViewportWidth 360, and 664 px horizontal overflow; the screenshot shows clipped navigation and content. F10 critical: The mobile layout renders a 1,024 px desktop canvas inside a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The stylesheet probe found no @container rules, while the 360 px capture keeps desktop sidebar/card geometry and clips the result grid. F11 medium: Reusable cards and navigation do not adapt at component level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The probe counted 52 controls smaller than 24 px and found many focused controls with outline-style none/0 px; Lighthouse also fails target-size. F12 high: Keyboard focus and touch sizing are unreliable. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, category, search, video, and signup captures have specific headings and visually prominent next actions. |
support-core-task-successprimary-flow-completion | pass | high | Direct navigation exercised discovery → search/category → video detail and account entry; all representative URLs rendered usable states, with legal age verification clearly separated. |
support-core-task-successclear-system-state-and-recovery | pass | high | The age gate explains why playback is unavailable, consent offers equal Accept/Reject actions, and the intentional 404 says “Page not found” with a Return to Home Page action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 3.5 s and LCP 3.8 s; the trace measured LCP 2.26 s in a separate run, showing the mobile result is the risk condition. F13 high: Mobile loading misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0 with no shifts; Lighthouse also reports CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace reports two long tasks, 123 ms TBT, and a 162 ms longest task; Lighthouse lab TBT is 0 ms, acceptable for initial interaction. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimates 1,210 ms savings from render-blocking requests; HAR confirms three VeryHigh parser-inserted stylesheets and 151 requests. F14 high: Render-blocking and dependency chains delay first content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 56 KiB unused CSS and 26 KiB unused JavaScript; HAR records 66 scripts and 1.02 MB script transfer. F15 medium: The entry page ships avoidable CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse finds two unnamed buttons and label/content-name mismatches; the email signup state exposes email/password inputs with zero associated labels. F16 high: Interactive controls and signup fields lack robust accessible names and labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse identifies age-banner text at 1.75:1 and 2.15:1 and metadata at 3.29:1 against dark surfaces. F17 high: Multiple text surfaces fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The focus probe found key controls with no outline/box-shadow and Lighthouse reports malformed list content plus an accessibility-tree failure. F18 high: Focus visibility and list structure are not consistently accessible. |
be-inclusivelegible-text | issues | high | At 360 px, the desktop canvas clips headings, navigation, and card text; Lighthouse reports 12 px view metadata at 3.29:1. F19 medium: Narrow-screen clipping and low-contrast metadata harm legibility. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse fails meta-viewport and target-size; layout evidence shows 664 px overflow at 360 px. F20 critical: Mobile reflow, zoom policy, and target sizing fail accessibility expectations. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit did not report a failing console-error condition in the retained run. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive reports 29/36 images without width/height and 13 oversized images, although the document has a valid doctype and UTF-8 charset. F21 medium: Most images lack intrinsic dimensions and several are oversized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three deprecation warnings and a best-practices score of 0.81. F22 medium: Deprecated APIs and platform hygiene warnings remain. |
be-discoverabletitle-and-description | pass | high | DOM and metadata probes show descriptive titles and meta descriptions on home and video detail. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Rendered DOM contains 359 real href links, a viewport meta tag, and robots.txt allows public catalog routes. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical URLs and robots.txt are present, but /sitemap.xml returns 404 and no hreflang links were found on English or German templates. F23 medium: Indexing signals are incomplete across a large multilingual catalog. |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative video has Open Graph/Twitter metadata but zero JSON-LD blocks, so crawlers must infer video properties. F24 medium: Video entities lack structured VideoObject data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP is only frame-ancestors; four of five cookies lack Secure and several use SameSite=None. F25 high: Cookie and CSP transport protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR records 117 third-party requests and 1.65 MB transferred from third-party origins; tracker evidence finds 12 third-party origins, including ad and Google account endpoints. F26 high: The initial load has a broad third-party footprint before consent. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load; signup source contains passkey/WebAuthn capability and no geolocation/notification request signal was found. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack X-Content-Type-Options and Referrer-Policy; CSP contains only frame-ancestors and Permissions-Policy allows only client hints rather than constraining sensitive features. F27 high: Defensive response policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability fetch reports HTTP 200, 85% raw-HTML content coverage, title/H1/description present, and isJsShell=false. |
be-resilientresilient-runtime-behaviour | issues | high | The visible consent layer is a custom fixed 780×493 element without dialog semantics, while the 360 px page retains 1,024 px layout width. F28 medium: Runtime overlays and fixed layout do not remain robust at narrow sizes. |
be-resilientoffline-and-installable | pass | high | PWA probe finds an active service worker, manifest with start_url/scope/icons/display, and populated Cache Storage. |
be-resilientnetwork-and-http-failure-states | pass | high | Intentional unknown route renders “Page not found”, explanatory recovery text, a home link, and useful navigation rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | English and German templates set html lang correctly; German UI is translated and stylesheet inspection finds logical inline/block properties alongside legacy physical rules. |
be-internationalisedlocale-aware-data | pass | high | The German locale serves translated navigation/category content and locale-specific copy from a dedicated locale URL; no user-entered locale-sensitive form data appeared. |
be-internationalisedtime-zone-correctness | not-applicable | high | No rendered times, appointments, recurring events, or time-zone-sensitive data were present on the audited templates. |
be-trustworthyno-dark-patterns | pass | high | Consent presents Accept and Reject as equal-size peer actions and the signup state links Terms and Privacy while stating public/partner data use. |
be-trustworthyhumane-error-handling | issues | high | After selecting email signup, email/password fields have no labels, required=false, and no aria-invalid state; error timing and announcement affordances are absent from the initial form state. F29 high: Email signup fields do not expose robust validation semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | Both email inputs report autocomplete="off" while the password correctly uses new-password. F30 high: Signup obstructs autofill for email. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Public signup clearly separates login, provider, and email choices and states age-verification and data-use commitments before submission. |
be-sustainableoptimised-assets | issues | high | The image audit reports 13 oversized images, 15 legacy-format images, 29 missing dimensions, and 8 below-fold images not lazy-loaded. F31 medium: Image delivery wastes bytes on oversized and legacy candidates. |
be-sustainableno-wasteful-work | issues | high | The initial load makes 151 requests, runs 66 scripts, and transfers 1.78 MB before the user chooses consent or starts media. F32 medium: The homepage performs disproportionate background/network work before interaction. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 117/151 requests and 1.65/1.78 MB transferred; static CDN JavaScript alone includes a 400 KB entry bundle. F33 high: Third-party code dominates the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing surface or intent was provided; this emerging capability is contextual and not required for the public media catalog. |
be-agent-readyon-device-inference | not-applicable | high | No experience requiring local summarisation or language-model inference was identified; this emerging capability is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After 10 bottom/top traversals, heap grows from 710,431 to 734,398 nodes and 37.62 MB to 39.20 MB (+1.58 MB); separate fresh-page captures make this medium-confidence rather than proof of a leak. F34 medium: Repeated feed traversal retains measurable heap growth. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap contains 710,431 nodes, 3.34 million edges, 95,643 closures, and 37.62 MB self size before media playback. F35 medium: The landing page has a large initial object/DOM footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | issues | medium | The post snapshot has +9,274 native nodes and +4,003 closures; no Detached* constructor appears in the compact top list, so the signal is accumulation risk rather than a confirmed detached-DOM leak. F36 medium: Repeated scrolling leaves substantial native and closure growth that needs leak investigation. |
Provenance
Canonical report: results/atomic/reports/0744-xhamster_desi.json
Report SHA-256: 673f22674c98f3239aeedfb5bb5ee2852fc2948da2100dd000bcd3f230d39884
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/xhamster_desi/2026-07-26T22-10-18-432Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/xhamster_desi/2026-07-26T22-10-18-432Z
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.