Manifest position 739 · CrUX rank bucket 1000
https://pl.xhamster.com
Coverage complete
Coverage-complete audit of four representative archetypes plus a 404 recovery state.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | pass | high | Light and dark screenshots show the complete surface retinted, and CSS contains both prefers-color-scheme branches. |
respect-user-preferencesrespects-reduced-motion | issues | high | The evaluate probe under prefers-reduced-motion: reduce found eight running animations, each with a 2,000 ms duration, and the CSS scan found no reduced-motion media rule. F01 medium: Reduced-motion preference does not suppress ongoing animation. |
respect-user-preferencesrespects-contrast | issues | high | The stylesheet scan found color-scheme rules only, with no prefers-contrast or forced-colors handling; Lighthouse also measured age-banner contrast as low as 1.75:1. F02 medium: High-contrast preferences are not explicitly supported. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition rules or names even though document.startViewTransition is available. F03 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked storytelling, parallax, carousel, or reveal interaction was present on the representative paths. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No custom gesture-driven primary interaction was present; covered paths use ordinary links, buttons, and native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long listing has fixed header and navigation chrome, while the CSS probe found no scroll-state query, progress indicator, or scroll timeline. F04 low: Page chrome does not respond to scroll position. |
provide-guided-navigationanchored-positioning | not-applicable | high | No edge-sensitive tooltip or spatially anchored transient overlay was required in the covered core journeys. |
provide-guided-navigationdirects-attention | pass | high | Active navigation uses a red underline and headings clearly identify listing and category destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots of the home and category pages show a large centered consent panel covering the listing before interaction. F05 high: The cookie notice obscures the primary content on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe found zero dialog, popover, and details elements; signup uses a custom role=dialog surface. F06 medium: Overlays use custom dialog markup instead of native primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop screenshot shows two header rows, an age-verification banner, a persistent sidebar, filters, and the consent panel competing with the video grid. F07 medium: Navigation and promotional chrome crowd the content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800, layout metrics reported scrollWidth 1024, clientWidth 360, and 664 px horizontal overflow; the screenshot shows most content clipped off-screen. F08 critical: The desktop layout is forced into a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container query rules; the clipped mobile state shows desktop-sized header, sidebar, banner, and grid components. F09 medium: Reusable components do not adapt at container level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatic focus on the first link produced outline-style none and no box shadow; a DOM probe counted 20 visible controls smaller than 24x24 px. F10 high: Keyboard focus and small controls are not reliably usable. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, category, video, and signup pages have descriptive headings and clear next actions. |
support-core-task-successprimary-flow-completion | pass | high | The representative browse-to-detail and signup-to-email-form journeys exposed predictable controls and no broken navigation; legal age verification remained explicit. |
support-core-task-successclear-system-state-and-recovery | pass | high | Invalid signup fields show specific Polish errors, and a true 404 returns status 404 with an explanation and home link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 3.9 s, while the independent trace measured 1.74 s under a different run, showing condition-sensitive loading performance. F11 high: Mobile LCP misses the good threshold. |
be-fast-and-stablevisual-stability | pass | high | Layout and Lighthouse both recorded CLS 0 with no observed shift entries. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded two long tasks, 149 ms TBT, and Lighthouse measured 0 ms TBT and 0.5 s main-thread work, acceptable for the sampled load. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 143 requests and 1.79 MB transferred, including 62 scripts totaling 1.02 MB and three VeryHigh-priority parser-inserted stylesheets. F12 medium: The initial network graph is script-heavy. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 26 KiB unused JavaScript and 56 KiB unused CSS, with two stylesheets about 90 to 95 percent unused. F13 low: The mobile page ships avoidable unused code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility found an unnamed button in the content filter list; the images primitive also found one image without alt text. F14 high: At least one button has no accessible name. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 1.75:1 and 2.15:1 text in the age banner, 3.29:1 view counts, and 4.04:1 subscription text. F15 high: Important text fails WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The focus probe returned outline none and no box shadow for the focused anchor, despite otherwise useful main, nav, header, footer, and heading structure. F16 high: Visible keyboard focus is missing on a primary link. |
be-inclusivelegible-text | pass | high | Desktop light and dark screenshots show readable card titles, headings, and signup copy without clipping at the sampled desktop viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360 px audit showed 664 px overflow and 20 undersized controls; the sampled video-detail probe found no track elements. F17 critical: The page does not reflow on a narrow viewport and sampled media has no caption track. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors on load. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 29 of 36 images missing width or height, 12 oversized images, 8 below-fold images without lazy loading, and 16 legacy-format URLs. F18 medium: Image markup does not consistently reserve or right-size media. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse found no DevTools inspector issues and no console errors; no permission prompt occurred on load. |
be-discoverabletitle-and-description | pass | high | Home, signup, and video detail expose descriptive unique titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse confirmed crawlable links, valid robots, and viewport metadata, but direct mobile layout evidence showed 664 px horizontal overflow. F19 high: The entry page is crawlable but not mobile-friendly. |
be-discoverablecanonical-and-indexing-signals | issues | high | The Polish home page has a canonical URL and valid robots policy but the metadata probe found zero hreflang links despite links to more than 40 locale hosts. F20 medium: Localized pages do not expose hreflang links. |
be-discoverablestructured-and-shareable-metadata | issues | high | The home page had no JSON-LD or Open Graph tags; the sampled video detail had seven Open Graph tags but no JSON-LD VideoObject. F21 medium: Entity metadata is incomplete. |
be-private-and-securesecure-transport-and-headers | issues | high | The cookie audit found settings and x_csrf_token without Secure; settings also uses SameSite=None. HTTPS, HSTS, CSP, and frame protection were present. F22 high: Two first-party cookies are missing Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The HAR attributed 117 of 143 requests and 1.68 MB of 1.79 MB to other origins; the tracker probe observed 14 third-party origins, including accounts.google.com and an ad syndication origin. F23 high: The pre-consent page has a broad third-party request footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The signup surface offers Google, X, and email/password; the auth probe found no WebAuthn or passkey affordance and no permission request on load. F24 medium: Authentication offers federated and password flows but no passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lacked X-Content-Type-Options and Referrer-Policy; CSP only defined frame-ancestors, and Permissions-Policy only named two client-hint features. F25 high: Browser-enforced policy coverage is incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 85 percent raw-HTML content coverage, with title, h1, and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Covered menus, consent, category, video, and signup states remained rendered and usable without console or inspector errors. |
be-resilientoffline-and-installable | not-applicable | high | Video streaming is intrinsically online. A manifest and active service worker exist, but offline playback is not a reasonable core expectation. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent route returned HTTP 404 with a clear Polish explanation, support direction, and home recovery link. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page correctly sets html lang=pl, but the stylesheet scan counted about 700 physical left/right declarations and only a small number of logical-property uses across a site offering RTL languages. F26 high: The localized layout relies heavily on physical CSS directions. |
be-internationalisedlocale-aware-data | not-applicable | high | The covered Polish listing, category, video, and signup paths did not render dates, currencies, or other locale-sensitive structured values. |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, schedules, recurring intervals, or time-zone-sensitive values appeared on the covered paths. |
be-trustworthyno-dark-patterns | issues | high | After choosing Odrzuć, the signup flow displayed a message that some features may be unavailable and continued to present Akceptuj wszystkie pliki cookie. F27 medium: Rejecting optional cookies leaves a persistent prompt to accept all cookies. |
be-trustworthyhumane-error-handling | issues | high | Submitting the empty email form produced clear Polish messages, but the probe found no role=alert or populated aria-live region and no aria-invalid state. F28 medium: Signup errors are visible but not announced programmatically. |
be-trustworthytrustworthy-input-assistance | issues | high | The expanded signup form exposes two email inputs with autocomplete=off; only the password input uses autocomplete=new-password. F29 medium: Email signup disables useful autofill. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The signup surface states age-verification requirements, terms, privacy policy, and that personal data may be public before submission. |
be-sustainableoptimised-assets | issues | high | The images primitive found 12 oversized images, 29 without dimensions, 3 without srcset, and 16 legacy-format URLs. F30 medium: Many thumbnails are oversized or lack responsive delivery metadata. |
be-sustainableno-wasteful-work | pass | high | The sampled load had only four XHR/fetch requests, Lighthouse reported 0.5 s main-thread work, and no autoplaying video element was present. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR recorded 1.68 MB from third-party origins, including 1.08 MB from the static CDN classification and 122 KB from Google accounts before the primary flow needed sign-in. F31 medium: Third-party code dominates initial transferred bytes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing capability or intent was present for this public media site. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the covered scope required built-in on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten search focus/input/clear cycles, heap self size rose 2.1 MB (5.7 percent) without an unbounded trend or detached-node signal in the summary; confidence is medium because runs used isolated browser sessions. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contained 682,503 nodes, 3.20 million edges, and 36.7 MB of self size for a listing page. F32 medium: The entry page has a large initial object graph. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary listed Detached constructors among the retained populations; closures rose about 2.2 percent after ten search cycles, not an unbounded accumulation signal. |
Provenance
Canonical report: results/atomic/reports/0739-pl_xhamster_com.json
Report SHA-256: 6b38e7939484ed37c7fe6af8c2dd6ef419159072dcf54f4c8450f1f1c2df9f99
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pl_xhamster_com/2026-07-22T18-56-15-457Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pl_xhamster_com/2026-07-22T18-56-15-457Z
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.