Manifest position 924 · CrUX rank bucket 1000
https://www.xvideos.es
Coverage complete
Coverage-complete audit across six representative paths. No source was supplied, so this is critique only.
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 | The dark-mode screenshot is visually unchanged from the default capture, and the CSS probe found no prefers-color-scheme, color-scheme, or light-dark() use. F01 medium: The interface does not honor the user’s dark-theme preference. |
respect-user-preferencesrespects-reduced-motion | issues | medium | The CSS probe found no prefers-reduced-motion rule. The listing currently had no active animations, but player and navigation effects have no preference-aware safeguard. F02 low: Reduced-motion preferences are not handled explicitly. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast capture retains the default styling, while the CSS probe found no prefers-contrast or forced-colors handling. F03 medium: High-contrast preferences are not explicitly supported. |
implement-natural-interactionsview-transitions | issues | medium | The platform probe found no View Transition CSS, and navigation among listing, search, account, and detail pages performs ordinary visual swaps. F04 low: Route changes use abrupt full-document swaps. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS probe found no scroll-linked animation and trace observed only one 53.5ms long task; no scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile captures and DOM showed native document scrolling with no custom gesture surface or pointer-driven replacement. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | CSS inspection found no scroll-state queries or scroll-position-aware styling on long listing pages. F05 low: Page chrome does not respond to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or anchored menu was present on the representative paths, so anchored overlay positioning was not applicable. |
provide-guided-navigationdirects-attention | issues | medium | The search and listing captures show static page swaps; the probe found no directional transition or highlight mechanism. F06 low: Navigation does not visually guide attention after a route or in-page state change. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | The age-confirmation gate is purpose-specific, clearly labelled, and offers a direct completion action rather than advertising or an upsell. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The load screenshot shows a blocking age-entry overlay, but the DOM probe found zero dialog, popover, details, or aria-modal elements. F07 medium: The age-entry overlay is implemented without a semantic dialog primitive. |
maximize-content-reduce-noisereduced-chrome | pass | high | Mobile and desktop screenshots prioritize the listing grid and search; permanent header chrome remains compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout primitive measured scrollWidth=clientWidth=360 and horizontalOverflowPx=0 with a viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Mobile layout has no overflow, but CSS inspection found no container queries or container-type on reused card/search components. F08 low: Reusable listing components are responsive only at page level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found user-scalable=no/maximum-scale=1, and the probe counted 106 visible interactive elements below 24px in at least one dimension. F09 high: Zoom is disabled and many interactive targets are too small. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly presents search, category navigation, content cards, and a direct age-confirmation action. |
support-core-task-successprimary-flow-completion | pass | high | Search results and a representative detail page loaded successfully from crawlable homepage links without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid-route probe showed a localized not-found message and a direct return-to-home link; native form validation focuses the first invalid field. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.1s and performance 0.74, while the trace’s warmer desktop-like run measured LCP 1.60s, showing a material condition-dependent gap. F10 high: Mobile loading misses the good LCP range. |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer measured CLS 0.272 across six shifts; 99 of 100 images lack width/height attributes. F11 high: The mobile listing shifts substantially during load. |
be-fast-and-stableefficient-main-thread | pass | high | Trace measured one 53.5ms long task and 3.51ms total blocking time; no sustained main-thread blocking was observed. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR/DOM confirmation found a head parser script without async/defer plus additional parser scripts, and the HAR summary lists multiple images without cache headers. F12 medium: Critical delivery includes parser-blocking scripts and weak image caching. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated about 594KB unused JavaScript and 211KB unused CSS on the audited load. F13 medium: The homepage ships substantial unused code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, and image-alt; the image primitive found 98 of 100 images without alt text. F14 high: Many controls and images lack accessible names or alternatives. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s color-contrast audit failed on both homepage and account surfaces. F15 high: Text and UI contrast fail WCAG minimums. |
be-inclusivestructure-and-focus | issues | high | The homepage probe found no headings and no main element; Lighthouse also failed the account page for lacking one main landmark. F16 medium: Pages lack a logical heading and main-landmark structure. |
be-inclusivelegible-text | issues | high | Computed body text is 12px across homepage/account DOM captures, and the mobile screenshots show dense metadata and legal text. F17 medium: Core text is rendered too small and densely for comfortable reading. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse recorded a viewport meta value with maximum-scale=1 and user-scalable=no. The media detail also exposed no caption track in the sampled video. F18 high: User zoom is prevented. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a Google FedCM NetworkError and a “Not signed in with the identity provider” console message during account load. F19 low: The account page logs identity-provider errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 99 images without dimensions; Lighthouse reported the deprecated internal cast-button selector. F20 medium: Document assets omit sizing and use a deprecated media-control selector. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found missing/404 source maps for large first-party, HLS, and verification scripts, plus a deprecated API warning. F21 low: Browser-development hygiene is incomplete. |
be-discoverabletitle-and-description | issues | high | Lighthouse SEO scored the account page 0.92 but specifically failed meta-description; homepage and detail titles were descriptive. F22 medium: The account template has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors; the DOM probe counted four href anchors with empty names and one anchor without href. F23 medium: Some links are not crawlable or have no discernible text. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage and detail metadata probes found hreflang alternates but no rel=canonical URL. F24 medium: Canonical signals are absent on sampled public templates. |
be-discoverablestructured-and-shareable-metadata | pass | high | The detail page exposes VideoObject JSON-LD, matching Open Graph video metadata, and localized hreflang alternates. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HTTPS and CSP, but no HSTS or nosniff; CSP allows unsafe-inline and unsafe-eval. F25 high: Transport defenses are incomplete and CSP permits unsafe script execution. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker capture found no known tracker domains; four third-party origins were mainly thumbnail CDNs, and the only cookie was first-party Secure and HttpOnly. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The account DOM exposes email/password forms with no WebAuthn/passkey UI or source marker; no permission prompt appeared on load. F26 high: Authentication is password-only on the sampled account surface. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack Permissions-Policy and HSTS, use no-referrer-when-downgrade, and rely on X-Frame-Options without a CSP frame-ancestors directive. F27 high: Defensive browser policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 98% raw-HTML content coverage, isJsShell=false, and visually captured a populated crawler view. |
be-resilientresilient-runtime-behaviour | pass | high | Representative listing, account, and detail paths loaded without clipped overlay/menu failures; error recovery remained navigable. |
be-resilientoffline-and-installable | issues | high | A manifest exists, but no service-worker registration was found and its start_url points to xvideos.com rather than the audited .es locale. F28 medium: The installed-app/offline story is incomplete and locale-inconsistent. |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route rendered a localized not-found state with a visible return-to-home recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | high | HTML lang is es and pages expose extensive locale-specific hreflang alternates; the sampled left-to-right Spanish layout reads correctly. |
be-internationalisedlocale-aware-data | pass | high | Rendered Spanish surfaces use localized decimal grouping and translated labels; no contradictory locale formatting was observed. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled public listing, account, and media surfaces exposed no user-facing scheduled time or time-zone-sensitive workflow. |
be-trustworthyno-dark-patterns | pass | high | The age gate states its purpose and terms, marketing is unchecked by default, and account consent labels are visible. |
be-trustworthyhumane-error-handling | issues | high | Submitting empty Spanish sign-in fields yields English native messages, no aria-invalid, and zero aria-live/alert regions, although focus moves to the first invalid field. F29 medium: Form errors are not localized or announced accessibly. |
be-trustworthytrustworthy-input-assistance | issues | high | Email, username, and current-password fields on the account page have empty autocomplete values; only new-password is declared. F30 medium: Sign-in and sign-up inputs omit autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account path offers password sign-in/recovery only; marketing is opt-in and terms are visible, but no passkey management or reauthentication surface was found. F31 medium: Account flows do not offer phishing-resistant authentication. |
be-sustainableoptimised-assets | issues | high | All 100 images lack srcset, 99 use legacy formats, and 90 below-fold images are not lazy-loaded. F32 high: Thumbnail delivery is not responsive or format-efficient. |
be-sustainableno-wasteful-work | pass | high | Trace found only 3.51ms blocking time and tracker evidence showed no known analytics suite; no persistent background processing was observed. |
be-sustainablethird-party-and-media-budget | issues | high | HAR captured 121 requests and 2.79MB transferred before video playback, including 106 images/1.69MB and 90 below-fold images loaded eagerly. F33 high: The initial media/listing budget is disproportionate. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and no declared intent or transactional agent surface was present; absence is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task was part of the representative user journeys, so on-device inference was not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, heap self-size fell from 26,887,370 to 26,868,398 bytes while node count changed only +405, showing no retained-growth signal. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 26.9MB self-size and 375,406 nodes for a 100-card media listing; this remained bounded after interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries remained effectively flat after ten scroll cycles, with no aggregate retention trend suggesting accumulating nodes/listeners. |
Provenance
Canonical report: results/atomic/reports/0924-www_xvideos_es.json
Report SHA-256: e4ea5ba188168a5810c2a4e4c58c883539d43a1b3e8f05c9ce3c81c9cf9a8dca
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xvideos_es/2026-07-23T21-38-29-028Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xvideos_es/2026-07-23T21-38-29-028Z
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.