Manifest position 685 · CrUX rank bucket 1000
https://ar.xhamster.com
Coverage complete
Coverage-complete audit of seven representative guest paths/templates. Not covered: registration completion, authenticated account management, payment/subscription checkout, upload and live-chat flows because they require account creation, personal data or commercial commitment.
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 | pass | high | Under prefers-color-scheme: dark, computed root colors were black and the retained CSS contained explicit dark/light media-query token sets; the dark screenshot remained usable. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce emulated, document.getAnimations() returned eight running shimmer animations, each with a 2000ms duration. F02 medium: Loading shimmer animation continues under reduced motion. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found age-banner text at 2.15:1 and secondary banner text at 1.75:1 against green, plus repeated metadata text at 3.29:1 against the dark surface; expected minimum is 4.5:1 for this text. F07 high: Important banner and metadata text fail WCAG contrast. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection across the loaded styles found no view-transition rules or names, while browsing moved between separate listing, search and detail documents. F15 low: Navigation swaps pages without declarative view-transition support. |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | No scroll-linked animation was present on the representative listing, search, login, or detail templates, so there is no implementation to classify. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | No custom swipe, pull-to-reveal, or gesture-driven primary interaction was present on the audited desktop and mobile paths. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop and search screenshots show persistent, consistent two-tier navigation and an active section marker while moving across long listing states. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip or transient anchored overlay was required to complete the audited browsing, search, login, or detail journeys. |
provide-guided-navigationdirects-attention | pass | high | The screenshots show an active Videos marker, clear H1 labels and stable navigation hierarchy across home, search and detail templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots of the home and detail templates show the cookie panel centered over most primary content. DOM inspection found no dialog, popover, role=dialog or aria-modal semantics for this interruption. F03 high: A large consent overlay obscures the primary content on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Desktop screenshots of the home and detail templates show the cookie panel centered over most primary content. DOM inspection found no dialog, popover, role=dialog or aria-modal semantics for this interruption. F03 high: A large consent overlay obscures the primary content on every fresh visit. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop screenshots of the home and detail templates show the cookie panel centered over most primary content. DOM inspection found no dialog, popover, role=dialog or aria-modal semantics for this interruption. F03 high: A large consent overlay obscures the primary content on every fresh visit. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800, layout measured scrollWidth 1024px against clientWidth 360px, 664px horizontal overflow. The screenshot shows the left rail and clipped content instead of a reflowed mobile layout. F01 critical: The desktop layout is forced into the mobile viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At 360x800, layout measured scrollWidth 1024px against clientWidth 360px, 664px horizontal overflow. The screenshot shows the left rail and clipped content instead of a reflowed mobile layout. F01 critical: The desktop layout is forced into the mobile viewport. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found user-scalable=no in the effective mobile viewport meta and target-size failures, including a 194x20 link. The 360px screenshot also fails reflow due to 664px overflow. Programmatic focus inspection found the search input and button with outline-style none, outline width 0 and no box-shadow; Lighthouse separately flagged target-size failures. F16 high: Keyboard focus is not visibly exposed on key controls. F08 high: The mobile page prevents normal zoom and has undersized or crowded targets. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each representative page exposes a descriptive H1/title and direct content cards or sign-in action in the first viewport. |
support-core-task-successprimary-flow-completion | pass | high | The audit navigated from listing to category, search results, a detail page and login; each destination rendered its intended content without a dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The intentional missing route rendered a localized “Página no encontrada” state with a clear link back to the home page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.9s and scored performance 0.85. The independent trace was faster at 1.16s, indicating variable but materially slow throttled mobile loading. F04 high: Mobile LCP misses the good Core Web Vitals threshold. |
be-fast-and-stablevisual-stability | pass | high | Layout observer reported CLS 0 and no shifts; Lighthouse independently measured CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded two long tasks, 154ms longest and 106.5ms total blocking time; Lighthouse measured 0ms TBT in its separate run, acceptable for initial browsing. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse measured LCP 3.9s and scored performance 0.85. The independent trace was faster at 1.16s, indicating variable but materially slow throttled mobile loading. The image primitive found 29 of 36 images without explicit dimensions, 13 oversized, 8 below-fold images not lazy-loaded and 15 legacy-format resources. Lighthouse also flagged unsized images and estimated 21KiB image savings. F05 medium: Image sizing and delivery waste bytes and create avoidable stability risk. F04 high: Mobile LCP misses the good Core Web Vitals threshold. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The load transferred 1.76MB across 143 requests; 62 scripts accounted for 1.01MB and one index bundle was 400KB. Lighthouse estimated 56KiB unused CSS, 26KiB unused JavaScript and 11KiB legacy JavaScript. F14 medium: Startup JavaScript and third-party delivery are heavy for the listing shell. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility score was 0.75 and reported an unnamed button, accessible-name/visible-label mismatches on media cards, and invalid direct children inside a ul. The custom consent overlay had no dialog semantics. F06 high: Interactive controls and content structures have accessibility-tree defects. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found age-banner text at 2.15:1 and secondary banner text at 1.75:1 against green, plus repeated metadata text at 3.29:1 against the dark surface; expected minimum is 4.5:1 for this text. F07 high: Important banner and metadata text fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse accessibility score was 0.75 and reported an unnamed button, accessible-name/visible-label mismatches on media cards, and invalid direct children inside a ul. The custom consent overlay had no dialog semantics. Programmatic focus inspection found the search input and button with outline-style none, outline width 0 and no box-shadow; Lighthouse separately flagged target-size failures. F06 high: Interactive controls and content structures have accessibility-tree defects. F16 high: Keyboard focus is not visibly exposed on key controls. |
be-inclusivelegible-text | issues | high | Lighthouse found age-banner text at 2.15:1 and secondary banner text at 1.75:1 against green, plus repeated metadata text at 3.29:1 against the dark surface; expected minimum is 4.5:1 for this text. F07 high: Important banner and metadata text fail WCAG contrast. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found user-scalable=no in the effective mobile viewport meta and target-size failures, including a 194x20 link. The 360px screenshot also fails reflow due to 664px overflow. F08 high: The mobile page prevents normal zoom and has undersized or crowded targets. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed and reported no console-error items. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 29 of 36 images without explicit dimensions, 13 oversized, 8 below-fold images not lazy-loaded and 15 legacy-format resources. Lighthouse also flagged unsized images and estimated 21KiB image savings. F05 medium: Image sizing and delivery waste bytes and create avoidable stability risk. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices score was 1.0; no console/deprecation failure or on-load permission prompt was observed, and permission states remained prompt. |
be-discoverabletitle-and-description | pass | high | DOM probe found a descriptive localized title and meta description; discoverability confirmed both are present in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport metadata, indexable robots configuration and 86% no-JS content coverage were directly observed; Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | issues | high | The page exposes dozens of language/region variants, html lang is es-AR and canonical is present, but the link[rel=alternate] probe returned no hreflang entries. /sitemap.xml returned HTTP 404. F13 medium: Localized variants are linked in-page but hreflang discovery signals are absent. |
be-discoverablestructured-and-shareable-metadata | issues | high | Home DOM probes found zero JSON-LD blocks and no Open Graph metadata despite the page representing a large media listing; the inspected detail template likewise supplied no evidence of structured metadata in the retained DOM artifact. F12 medium: Rich media pages lack structured and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers showed CSP limited to frame-ancestors, with no nosniff or Referrer-Policy. Cookie inspection found settings and x_csrf_token without Secure; settings also uses SameSite=None. F09 high: Transport is HTTPS, but browser defenses and cookie flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The HAR captured 143 requests, 117 classified third-party and 1.65MB third-party transfer, including Google Accounts and an ad-syndication endpoint, while the consent overlay was still awaiting a choice. Tracker enumeration found 13 third-party origins. F10 high: The fresh load contacts a broad third-party surface before consent is chosen. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Permission states remained prompt on fresh load, with no geolocation/notification prompt displayed; login offers federated authentication and correctly identifies username, though password input assistance is separately flagged. |
be-private-and-securedefensive-browser-policies | issues | high | Headers showed CSP limited to frame-ancestors, with no nosniff or Referrer-Policy. Cookie inspection found settings and x_csrf_token without Secure; settings also uses SameSite=None. F09 high: Transport is HTTPS, but browser defenses and cookie flags are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability fetched HTTP 200 raw HTML with title, H1, description and 86% rendered-word coverage; the crawler screenshot retained meaningful content. |
be-resilientresilient-runtime-behaviour | pass | high | Listing, search, login and detail documents rendered without broken overlay clipping at desktop width, and navigation to each independent document completed. |
be-resilientoffline-and-installable | pass | high | A manifest link is present and navigator.serviceWorker had an active controller, directly establishing install/offline infrastructure on the loaded page. |
be-resilientnetwork-and-http-failure-states | pass | high | A synthetic missing route produced a localized not-found page with explanatory copy and a home recovery link rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The localized page declares html lang=es-AR and exposes equivalent language/region links; Spanish headings and controls render in the retained screenshots. |
be-internationalisedlocale-aware-data | not-applicable | medium | The inspected guest templates display no dates, prices, currency, durations requiring locale formatting beyond already-localized strings. |
be-internationalisedtime-zone-correctness | not-applicable | medium | The inspected guest templates expose no scheduled event or time-zone-sensitive flow. |
be-trustworthyno-dark-patterns | pass | high | The observed consent panel presents Accept and Reject with equal visual weight and links to cookie/privacy details; the login page exposes password recovery and free registration without preselected commercial commitment. |
be-trustworthyhumane-error-handling | not-applicable | medium | No validation-heavy data-entry flow is required for guest browsing; the only audited account form is a basic sign-in with a recovery link. |
be-trustworthytrustworthy-input-assistance | issues | high | On /login, the username input uses autocomplete=username but the sign-in password input uses autocomplete=new-password, which can obstruct password-manager autofill for returning users. F11 medium: The existing-password field advertises the wrong autocomplete purpose. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The inspected login page clearly separates Google, X and password sign-in, includes “remember me” and password recovery, and makes no purchase or subscription commitment. |
be-sustainableoptimised-assets | issues | high | The image primitive found 29 of 36 images without explicit dimensions, 13 oversized, 8 below-fold images not lazy-loaded and 15 legacy-format resources. Lighthouse also flagged unsized images and estimated 21KiB image savings. F05 medium: Image sizing and delivery waste bytes and create avoidable stability risk. |
be-sustainableno-wasteful-work | issues | high | The load transferred 1.76MB across 143 requests; 62 scripts accounted for 1.01MB and one index bundle was 400KB. Lighthouse estimated 56KiB unused CSS, 26KiB unused JavaScript and 11KiB legacy JavaScript. F14 medium: Startup JavaScript and third-party delivery are heavy for the listing shell. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR captured 143 requests, 117 classified third-party and 1.65MB third-party transfer, including Google Accounts and an ad-syndication endpoint, while the consent overlay was still awaiting a choice. Tracker enumeration found 13 third-party origins. The load transferred 1.76MB across 143 requests; 62 scripts accounted for 1.01MB and one index bundle was 400KB. Lighthouse estimated 56KiB unused CSS, 26KiB unused JavaScript and 11KiB legacy JavaScript. F14 medium: Startup JavaScript and third-party delivery are heavy for the listing shell. F10 high: The fresh load contacts a broad third-party surface before consent is chosen. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | This public media browsing site exposes no declared agent-facing task surface; emerging WebMCP capability is contextual and not required for this audit. |
be-agent-readyon-device-inference | not-applicable | medium | No summarisation or language-model task is part of the inspected guest journeys; on-device inference is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll down/up cycles, heap self-size changed from 36,634,431 to 37,303,870 bytes (+1.8%) and node count +2.3%; bounded small growth does not establish an unbounded leak. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap summary measured 36.6MB self-size on a media-rich listing; the post-interaction state remained 37.3MB, proportionate and bounded in this sample. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary’s top constructors contained Detached* populations, and repeated scrolling caused only 1.8% heap-size growth; no accumulating detached-DOM signal was observed. |
Provenance
Canonical report: results/atomic/reports/0685-ar_xhamster_com.json
Report SHA-256: dcef061d22b7c6c80a9fd229e0573e813a3825a4039f6ea0fff8b99a510053e1
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ar_xhamster_com/2026-07-22T09-52-51-686Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ar_xhamster_com/2026-07-22T09-52-51-686Z
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.