Manifest position 174 · CrUX rank bucket 1000
https://ara.xhamster.com
Coverage complete
Coverage-complete model-led audit across five representative archetypes and one recovery route.
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 | Light and dark emulation changed body text from rgb(48,48,48) to rgb(245,245,245), and CSS contains prefers-color-scheme support. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found eight running 2-second animations while matchMedia(prefers-reduced-motion: reduce) was true. F01 medium: Motion continues when reduced motion is requested |
respect-user-preferencesrespects-contrast | issues | high | CSS inspection found no prefers-contrast or forced-colors rules, and Lighthouse found 13 color-contrast failures. F02 medium: Contrast preferences are not handled |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition usage across the MPA navigation surfaces. F03 low: Route and state changes lack continuity cues |
implement-natural-interactionsscroll-driven-animations | issues | high | CSS inspection found no animation-timeline, scroll-timeline, or view-timeline usage on the long listing. F04 low: Scrolling enhancements are not compositor-driven |
implement-natural-interactionsphysical-gestures | issues | high | CSS inspection found no scroll snap or overscroll affordance on dense horizontal and vertical media surfaces. F05 low: Long media listings provide no gesture-oriented affordances |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage exposes no scroll-state query, progress indicator, or shrinking-header behavior. F06 low: Navigation chrome does not reflect scroll state |
provide-guided-navigationanchored-positioning | issues | high | The load screenshot shows a custom centered overlay; DOM inspection found no dialog, popover, or anchor-positioning primitive. F07 medium: The consent overlay is not anchored or edge-aware |
provide-guided-navigationdirects-attention | pass | high | Screenshots and DOM show a single H1, conventional navigation landmarks and clear section headings across listing pages. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, category, signup, and video screenshots all show a large consent panel obscuring the primary page before interaction. F08 high: Consent blocks the primary content on every fresh load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probing found zero dialog or role=dialog elements and zero popovers while the blocking consent UI was visible. F09 high: The blocking consent panel is not exposed as a dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop first viewport is dominated by a consent panel, promotional strip, header and side chrome; the mobile capture leaves only a narrow content column. F10 high: Promotions and navigation crowd out the media content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The layout primitive measured scrollWidth 1024px and 664px horizontal overflow at a 360px visual viewport; the screenshot shows a wide sidebar consuming most of the screen. F11 critical: The 360px layout renders a 1024px-wide page |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no container queries, while the mobile screenshot shows desktop sidebar and cards compressed into a 360px viewport. F12 high: Components do not adapt to their available space |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first focused link computed to outline-style none and no box shadow; Lighthouse also found target-size failures. F13 high: Keyboard focus and touch targets are inadequate |
support-core-task-successclear-purpose-and-primary-action | issues | high | The first viewport places consent, age verification and promotion ahead of the video browsing task, and the 360px view exposes only a sliver of content. F14 high: Primary content and actions are obscured at entry |
support-core-task-successprimary-flow-completion | pass | high | The signup path exposed Google, X and email choices and the email panel opened without navigation failure. |
support-core-task-successclear-system-state-and-recovery | pass | high | Invalid signup produced Arabic error messages, and a nonexistent route presented a localized explanation plus a home recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.9s and scored performance 0.85; FCP was 2.4s. F15 high: Mobile LCP misses the good threshold |
be-fast-and-stablevisual-stability | pass | high | Layout and Lighthouse both measured CLS 0 during the observed load. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 160.27ms, with 149.12ms total blocking time. F16 medium: Load work includes blocking main-thread tasks |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 147 requests and 1.73MB transferred, including 61 scripts; Lighthouse estimated 1.05s savings from render-blocking resources. F17 high: The initial page ships a large, render-blocking dependency set |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 57KiB unused CSS (up to 94.6% in one file) and 26KiB unused JavaScript. F18 medium: Substantial CSS and JavaScript are unused at load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two unnamed buttons, two unnamed links and nine visible-label/accessibility-name mismatches; the DOM probe also found an unlabeled icon button and filter input. F19 high: Controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 13 color-contrast failures and links that rely on color alone. F20 high: Text and controls fail contrast requirements |
be-inclusivestructure-and-focus | issues | high | Focused content had no visible outline, and Lighthouse found malformed list structure. F21 high: Focus treatment and list semantics are unreliable |
be-inclusivelegible-text | pass | high | Desktop screenshots show readable Arabic body and heading typography with logical RTL layout. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360px capture overflows by 664px; Lighthouse also failed meta-viewport zoom and target-size checks. F22 critical: The mobile and zoom experience does not reflow |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no recorded items. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 29 of 36 images without dimensions, 12 oversized images, eight below-fold images not lazy-loaded and one missing alt. F23 medium: Image sizing and delivery metadata are incomplete |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices score was 1.0 and bfcache audit passed. |
be-discoverabletitle-and-description | pass | high | Home DOM has a distinct Arabic title and non-empty meta description; detail and signup titles are route-specific. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The layout primitive measured scrollWidth 1024px and 664px horizontal overflow at a 360px visual viewport; the screenshot shows a wide sidebar consuming most of the screen. F11 critical: The 360px layout renders a 1024px-wide page |
be-discoverablecanonical-and-indexing-signals | pass | high | Main and detail pages return 200 and expose self-referencing canonicals; robots.txt was reachable and discoverability fetch succeeded. |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative video page had Open Graph tags but no JSON-LD, so machine-readable VideoObject details are absent. F24 medium: Video pages omit structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Headers lacked X-Content-Type-Options and a response Referrer-Policy; two first-party cookies lacked Secure and settings used SameSite=None. F25 high: Security headers and cookies are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence observed 16 third-party origins and requests to collector.xhamster.com and tsyndicate.com on initial load. F26 high: The pre-consent load has a broad third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The sign-up surface offers Google, X and email options; source and DOM probes found no WebAuthn or passkey affordance. F27 medium: Sign-up offers no passkey path |
be-private-and-securedefensive-browser-policies | issues | high | CSP only declared frame-ancestors, Referrer-Policy and nosniff were absent, and Permissions-Policy allowed only client hints rather than restricting sensitive features. F28 high: The defensive policy set is narrow |
be-resilientprogressive-enhancement | pass | high | Raw HTML was 423KB, retained title/H1/description and 54% of rendered content words; the page was not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Navigation and the custom overlay remained rendered across sampled templates; no runtime error was observed. |
be-resilientoffline-and-installable | pass | high | An active service worker registration and manifest with name, start_url, display and three icons were present. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid URL rendered a localized not-found explanation and a return-home recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=ar and dir=rtl; CSS inspection found logical properties and the rendered layout is RTL. |
be-internationalisedlocale-aware-data | issues | high | The Arabic listing renders compact counts such as “1.9M مشاهدات” and “16.2M”, mixing English compact notation into Arabic copy. F29 medium: Arabic UI mixes non-localized compact number notation |
be-internationalisedtime-zone-correctness | not-applicable | high | Recon found no applicable authored surface. |
be-trustworthyno-dark-patterns | pass | high | Consent presents Accept and Reject as equal-size adjacent controls and the signup page states data use before account creation. |
be-trustworthyhumane-error-handling | issues | high | Empty signup produced Arabic messages, but inputs remained :valid with no aria-invalid and the assertive live region was empty. F30 medium: Signup errors are visible but not programmatically tied to fields |
be-trustworthytrustworthy-input-assistance | issues | high | The email field uses autocomplete=off and the password field is named new-password rather than using a complete, standards-based autocomplete token set. F31 high: Email signup disables expected autofill |
be-trustworthysafe-commercial-and-account-flows | issues | high | The sign-up surface offers Google, X and email options; source and DOM probes found no WebAuthn or passkey affordance. F27 medium: Sign-up offers no passkey path |
be-sustainableoptimised-assets | issues | high | The image audit found 12 oversized images, 16 legacy-format results, three without srcset and 29 without dimensions. F32 medium: Thumbnail assets are often oversized or missing delivery hints |
be-sustainableno-wasteful-work | issues | high | The page loaded 61 scripts; Lighthouse identified unused CSS/JS and the trace recorded two long tasks. F33 medium: Initial rendering performs avoidable script and style work |
be-sustainablethird-party-and-media-budget | issues | high | The initial load transferred 1.73MB across 147 requests, with 1.03MB of scripts and 16 third-party origins. F34 high: Third-party and script budgets are not constrained |
be-agent-readystructured-agent-capabilities | issues | high | The public site has search and signup flows, but probing found no WebMCP or registered agent-readable tools. F35 medium: Core search and signup capabilities are not machine-exposed |
be-agent-readyon-device-inference | not-applicable | high | Recon found no applicable authored surface. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | A baseline-to-post heap comparison after ten synchronous menu-toggle attempts showed only modest growth (37.0MB to 39.1MB); no runaway order-of-magnitude growth was observed. |
be-memory-efficientbounded-footprint | pass | high | Heap summaries measured 37.0–39.1MB self size for a media-rich listing, proportionate to the page purpose. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Heap top-constructor summaries did not surface Detached* populations; ten toggle attempts produced bounded node growth (689k to 731k). |
Provenance
Canonical report: results/atomic/reports/0174-ara_xhamster_com.json
Report SHA-256: 3af4d08c5e2ebe3c0073578c179e6edb1c2208e56c45c79948cb85deac807f84
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ara_xhamster_com/2026-07-18T22-45-03-756Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ara_xhamster_com/2026-07-18T22-45-03-756Z
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.