Manifest position 331 · CrUX rank bucket 1000
https://www.xnxx.es
Coverage complete
Coverage-complete representative audit of entry, search listing, video detail, account, and 404 recovery templates.
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 DOM/CSS probe found no color-scheme or prefers-color-scheme rule, and the dark-condition screenshot is pixel-identical in appearance to the default age gate. F01 medium: The interface ignores the system colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Emulated prefers-reduced-motion:reduce matched, and getAnimations() returned zero active animations on the entry state. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found neither prefers-contrast nor forced-colors handling; essential custom controls rely on fixed blue/white styling. F02 medium: No authored high-contrast or forced-colours adaptation is present. |
implement-natural-interactionsview-transitions | issues | high | The CSS/DOM probe found no view-transition usage across the home, search, and account templates. F03 low: Route and state changes use abrupt swaps rather than directional view transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked effects or main-thread scroll animation behavior were observed; CSS contained no animation-timeline and layout captured no long tasks. |
implement-natural-interactionsphysical-gestures | pass | medium | Representative pages rely on native scrolling and links; no custom pointer-driven gesture surface that fought platform behavior was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The search template is a long paginated feed, but CSS inspection found no scroll-state container query, progress cue, or responsive shrinking-header behavior. F04 low: Long listing chrome does not react to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | The templates expose menu/filter controls, while CSS inspection found no anchor-name, position-anchor, position-try, or native popover usage. F05 low: Menus and transient header controls are not anchored with resilient platform positioning. |
provide-guided-navigationdirects-attention | issues | high | The home-to-search-to-detail journey uses full page swaps; no view-transition, highlight, scroll-marker, or other focus-movement cue was found. F06 low: Navigation changes do not provide an attention cue. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | The only load-time interstitial is the site-purpose-specific age gate; it clearly states why access is blocked and provides explicit entry choices. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The visible gate is #disclaimer_background with three buttons; DOM inspection found zero dialog elements and the background page remains a large underlying interaction surface. F07 high: The mandatory age gate is a custom full-screen div rather than a semantic modal. |
maximize-content-reduce-noisereduced-chrome | issues | high | The 360px search screenshot shows two stacked header bars, seven icon controls, filter/report chrome, and the age gate before the first result. F08 medium: Dense navigation chrome competes with the listing content on mobile. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, search and detail both reported scrollWidth=clientWidth=360 and horizontalOverflowPx=0 with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection across home, search, and account templates found no @container or container-type usage. F09 low: Reusable cards and controls rely on viewport rules rather than component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused required account field computed outline-style:none; probes counted 151 sub-44px targets on search and 19 on account. F10 high: Keyboard focus is not reliably visible and many targets are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The gate identifies adult content and its primary entry buttons; search and detail titles communicate their purpose. |
support-core-task-successprimary-flow-completion | pass | medium | The representative journey is connected by real hrefs: entry page to /search/ai, then to a concrete /video-* detail URL; all three returned rendered templates. Playback itself was not started to avoid unnecessary media transfer. |
support-core-task-successclear-system-state-and-recovery | pass | high | A nonexistent route renders a titled Spanish not-found state with an h1 and a visible return-to-home action; forms use native required constraints. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.8s and Time to Interactive 10.2s (performance 0.75), despite low CLS and TBT. F11 high: The measured mobile load misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | CLS was 0.053 on home, 0.0037 on mobile search, and 0.00008 on mobile detail, all within the good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms total blocking time; Lighthouse TBT was 74ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR summary identifies one parser-blocking stylesheet and four parser-inserted script candidates; Lighthouse estimates 1.25s render-blocking savings and 4.9MiB cache-lifetime savings. F12 high: Critical delivery is slowed by blocking resources and weak cache/font/image delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 386KiB unused JavaScript, 123KiB unused CSS, and 51KiB legacy-JavaScript savings. F13 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name and link-name; the DOM probe found an unnamed account icon, logo link, and many image-only thumbnail links. F14 high: Important buttons and links lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and the sampled account/age-gate screenshots show strong white/yellow-on-blue contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage has no h1, the account page starts at repeated h2 headings, and the focused account field reports outline-style:none. F15 high: Heading/landmark structure and focus treatment are inconsistent. |
be-inclusivelegible-text | pass | medium | Account and age-gate screenshots at 360px show readable type without clipping or horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport because scaling is constrained in its audited DOM, while the probes counted hundreds of controls below 44px; mobile reflow itself showed no horizontal overflow. F16 high: Zoom policy and small targets reduce inclusive input access. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no browser errors logged. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 100/100 images without width/height, 100 without srcset, 100 legacy-format images, and 11 oversized images; Lighthouse also failed unsized-images. F17 medium: Image assets are unsized and not responsively delivered. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed valid-source-maps for large first-party JavaScript; no console errors or deprecated API failures were observed. F18 low: Large first-party scripts ship without valid source maps. |
be-discoverabletitle-and-description | pass | high | Home and search have descriptive Spanish titles and meta descriptions; Lighthouse title and meta-description audits passed. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse reports crawlable anchors and indexability; robots.txt allows public routes and both mobile layouts have viewport metadata with no horizontal overflow. |
be-discoverablecanonical-and-indexing-signals | issues | high | DOM probes found no canonical or hreflang on the .es templates; https://www.xnxx.es/sitemap.xml lists only www.xnxx.com sitemap locations. F19 medium: Canonical and localization signals are incomplete and the sitemap host is inconsistent. |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative probes found titles/descriptions but no visible evidence of Open Graph, Twitter Card, or validated schema.org entity metadata. F20 medium: Public listing/detail templates lack verified rich/share metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Header evidence shows CSP allows unsafe-inline and unsafe-eval, HSTS and nosniff are absent; the 180-day session_token uses SameSite=None. F21 high: Transport is HTTPS, but the CSP and cookie/header posture are weaker than the baseline. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR captured 13 third-party requests and 346,610 transferred bytes, including www.tjk-njk.com; the tracker primitive found two third-party origins even though no known tracker signature matched. F22 medium: Third-party delivery occurs before any recorded preference choice. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The account probe found password sign-in fields and no WebAuthn/PublicKeyCredential integration; required sign-in fields also omit current-password/username autocomplete. F23 high: Account authentication is password-only and does not expose passkeys. |
be-private-and-securedefensive-browser-policies | issues | high | Headers show no HSTS, Permissions-Policy, or nosniff; Referrer-Policy is no-referrer-when-downgrade and CSP relies on X-Frame-Options rather than a visible frame-ancestors directive. F24 high: Several browser-enforced defensive policies are absent or weak. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 31% raw-to-rendered content coverage and reported the rendered title absent from raw HTML, despite a 200 response. F25 high: Most rendered content is unavailable to a crawler that does not execute JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative menu/list/detail/account templates rendered without cut-off horizontal overflow, uncaught console errors, or blank runtime states. |
be-resilientoffline-and-installable | issues | high | The PWA probe found zero service-worker registrations; manifest.json has name/icons/display but no start_url and no offline fallback was demonstrated. F26 medium: The standalone manifest is incomplete and there is no active service worker. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested nonexistent route provides a specific not-found message and a recovery link instead of a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | issues | high | All sampled pages correctly use lang=es, yet CSS inspection found no logical inline/block properties and no dir declaration across a site with language switching. F27 medium: Language is declared, but the layout is not writing-mode resilient. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative pages contain no dates, currencies, durations, or other locale-sensitive values to format. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative pages contain no events, schedules, or stored time concepts requiring time-zone or DST handling. |
be-trustworthyno-dark-patterns | pass | medium | The age gate states the condition and terms directly; account marketing consent is a separate unchecked checkbox and legal links are visible. |
be-trustworthyhumane-error-handling | pass | medium | Required account fields use native constraint validation and return specific fill-in messages; no premature visible error was present in the initial account screenshot. |
be-trustworthytrustworthy-input-assistance | issues | high | The account probe found empty autocomplete on email/login/password fields except new-password confirmation fields. F28 medium: Sign-up, sign-in, and recovery fields omit useful autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The account surface clearly separates sign-in, registration, recovery and social sign-in; terms and privacy links are visible and no paid commitment occurs in the sampled flow. |
be-sustainableoptimised-assets | issues | high | The image primitive found 100 legacy PNG/JPEG images, zero modern-format images, zero srcset, 11 oversized images, and 89 below-fold images without lazy loading. F29 high: The thumbnail-heavy experience does not optimise image formats or responsive delivery. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimates 509KiB unused CSS/JS and the image audit found 89 below-fold images not marked lazy. F30 medium: Large unused bundles and eager below-fold image work waste network and processing resources. |
be-sustainablethird-party-and-media-budget | pass | medium | The unloaded home/gate state transferred 1.24MiB with 346KiB third-party bytes and did not autoplay video; for a media catalog this sampled pre-playback footprint is proportionate, though asset waste is reported separately. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent exists for this public media catalog; this emerging opportunity is not treated as an obligation. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the sampled catalog requires on-device language-model or summarisation inference; this emerging check is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten mobile-menu open/close cycles, heap changed from 19.77MB/284,660 nodes to 20.27MB/289,247 nodes (about 2.5%/1.6% across fresh sessions), with no Detached constructor among top populations; no unbounded trend was established. |
be-memory-efficientbounded-footprint | pass | medium | The sampled page heap was about 19.8-20.3MB for a thumbnail-rich page, proportionate to the rendered catalog state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared in the top heap constructor summaries before or after ten menu cycles, and total growth was small rather than runaway. |
Provenance
Canonical report: results/atomic/reports/0331-www_xnxx_es.json
Report SHA-256: 3f801f33d74ea724130b1183f211f927964184dcaac376060ada8413e6722589
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xnxx_es/2026-07-20T00-05-39-112Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xnxx_es/2026-07-20T00-05-39-112Z
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.