Manifest position 58 · CrUX rank bucket 1000
https://www.youjizz.com
Coverage complete
Coverage complete. Public entry, listing, detail, search, login, and HTTP failure templates were sampled. Age verification was not bypassed, playback was not started, and authenticated/account-management states were not covered.
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 platform probe found zero prefers-color-scheme rules and color-scheme remained normal. Dark appearance is fixed/manual rather than preference-driven. F01 medium: Theme does not follow the system color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, three 1200 ms animations remained running and the stylesheet contained zero reduced-motion rules. F02 medium: Motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot shows the backdrop and panel but no visible logo, text, or controls, making the primary gate unusable. F03 high: The age-verification UI disappears under increased contrast. |
implement-natural-interactionsview-transitions | pass | high | Platform inspection found 19 view-transition CSS rules, providing direct transition support for route/state changes. |
implement-natural-interactionsscroll-driven-animations | pass | high | No parallax, scrollytelling, or custom scroll-linked animation was present in the representative listing states; scrolling remained native. |
implement-natural-interactionsphysical-gestures | pass | high | Representative pages use native scrolling and ordinary links/forms; no custom pointer-drag gesture that fights the platform was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 2,983 px mobile document has no progress or scroll-state-aware chrome; the platform probe found no container-query support and recon showed static navigation. F04 low: Long listings provide no scroll-position feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned transient menu requiring anchored positioning was present in the representative states. |
provide-guided-navigationdirects-attention | issues | high | Representative listing, search, and detail routes use full page changes without a current-location heading on the listing and search templates; their DOMs have no h1. F05 low: Navigation changes do not visibly guide attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | The blocking first-view overlay is a clearly explained legal age gate with explicit verify and underage exits, not an unrelated promotional popup. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe found div#ageVerificationModal role=dialog without aria-modal, plus a separate custom overlay. No native dialog was used. F06 medium: The mandatory overlay is a custom div rather than a complete modal primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first load creates 16 third-party origins, ad widgets, duplicated desktop/mobile menus, and 2.59 MB of third-party transfer before the gate is completed. F07 medium: Advertising and duplicated navigation compete with the content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360 by 800, layout metrics reported scrollWidth=clientWidth=360 and zero horizontal overflow; the gate fit the viewport width. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero container rules across loaded stylesheets although cards, headers, forms, and overlays are reused in different-width regions. F08 low: Reusable components rely on viewport styling only. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found outline-style none and no box shadow on the first 20 focusable controls. Many links were about 31 px high and Lighthouse failed target-size. F09 high: Keyboard focus is invisible and many targets are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly states the adult-only purpose and presents one prominent VERIFY AGE action plus an underage exit. |
support-core-task-successprimary-flow-completion | pass | high | Public listing, search, detail, and login destinations returned structured content and real GET/POST forms. The age gate itself exposes a clear continuation action; verification was not bypassed. |
support-core-task-successclear-system-state-and-recovery | issues | high | A nonexistent route returned a bare nginx-style 404 with only a heading and no search, home link, explanation, or retry action. F10 medium: HTTP failure has no useful recovery path. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 13.5 s, CLS 0.278, FCP 4.7 s, and performance 0.42. The first-party mobile layout probe also measured CLS 0.142. F11 high: Mobile load performance and stability miss Core Web Vitals targets. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse found 11 shifts and CLS 0.278; the layout probe measured 0.142, including a 0.13 shift. All 33 inspected images lacked numeric dimensions. F12 high: Late overlays and unsized images cause large layout shifts. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse recorded 2.8 s of main-thread work, including 783 ms script evaluation. The trace also found a 73 ms long task. F13 medium: Third-party and application script create substantial main-thread work. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified parser-inserted headerScripts and jQuery Tagify without async/defer, three blocking stylesheets, and resources without cache headers. The live DOM confirmed the head scripts are synchronous. F14 high: The critical path includes blocking scripts and weak cache hygiene. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse failed unused CSS and unused JavaScript. The DOM loaded four gtag/Analytics configurations plus another analytics bundle; scripts transferred 1.13 MB. F15 medium: Repeated analytics and unused code inflate the load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, image-alt, and select-name. The image probe found 28 of 33 images without alt text. F16 high: Controls and media lack accessible names and alternatives. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found white text at 3.16:1 on the green age-verification CTA and 4.26:1 on red ad labels, below WCAG AA for normal text. F17 high: Text contrast fails on primary and advertising UI. |
be-inclusivestructure-and-focus | issues | high | The platform probe found no main, nav, header, or footer landmarks and no h1 on the homepage/listing/detail templates. The focus probe showed no visible outline or box shadow. F18 high: Landmarks, heading hierarchy, and visible focus are missing. |
be-inclusivelegible-text | issues | high | At 360 by 800, the fixed-height gate truncates the parent-safety paragraph behind the CTA while the desktop version shows more text. F19 medium: The mobile gate clips explanatory text. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport meta sets maximum-scale=1 and user-scalable=0. Lighthouse failed meta-viewport and target-size, and the detail probe found no caption tracks on seven video elements. F20 high: The page prevents zoom and media lacks text alternatives. |
follow-best-practicesno-console-errors | issues | high | Lighthouse reported a security console error: Not allowed to load local resource: blob:, attributed to the main document. F21 medium: The page logs a browser error during load. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse failed image aspect ratio, responsive image sizing, and unsized images. The image probe found all 33 images missing width/height and 25 missing srcset. F22 medium: Image sizing and aspect-ratio handling are unsound. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported inspector issues, legacy JavaScript, and a restricted zoom viewport. The page also uses javascript: links for language controls. F23 medium: Inspector and platform hygiene checks fail. |
be-discoverabletitle-and-description | issues | high | The homepage title is a keyword list, while the sampled detail page had an empty meta description. Listing and login routes reused generic metadata. F24 medium: Metadata is not consistently descriptive across templates. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Recon found javascript: language links and href=# controls, while the viewport disables user scaling. Lighthouse failed meta-viewport and several links lacked discernible names. F25 medium: Some controls are not crawlable and mobile metadata blocks scaling. |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical URL was found on the homepage probe. sitemap.xml returned 200 but its sampled lastmod values were all from 2018, despite currently changing listings. F26 medium: Canonical and sitemap signals are stale or missing. |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage declares og:type video.movie and og:video pointing to the homepage URL with an empty duration, while the detail page has no meta description. F27 low: Share metadata does not accurately represent every page. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, frame protection, Referrer-Policy, and Permissions-Policy were all absent. All 13 first-party cookies lacked Secure, and sessionId lacked HttpOnly. F28 high: Security headers and cookie attributes are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The gate load contacted 16 third-party origins and known Google trackers. HAR attributed 59 of 63 requests and 2.59 MB of 2.63 MB to third parties. F29 high: Tracking and third-party activity start before user intent. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login form exposes username and password fields, no WebAuthn or navigator.credentials integration was found, and no passkey option is presented. F30 medium: Authentication is password-only. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, or CSP; all cookies were SameSite=None and non-Secure. F31 high: Browser-enforced defenses are not configured. |
be-resilientprogressive-enhancement | pass | high | Discoverability fetched HTTP 200 raw HTML with 66% rendered-word coverage, title and description present, and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | The gate remained fully within both desktop and 360 px viewports, and representative pages returned populated server-rendered DOM rather than broken shells. |
be-resilientoffline-and-installable | not-applicable | high | Offline playback/installability is not a reasonable requirement for this intrinsically online streaming site; core no-JS reachability was judged separately. |
be-resilientnetwork-and-http-failure-states | issues | high | The sampled nonexistent route rendered a bare server 404 without site navigation, search, retry, or explanation. F32 medium: Network/HTTP failure states are not integrated with the site. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Although html lang=en-GB is present, rendered navigation exposes untranslated keys such as header.category.newest and header.loginmenu.login across homepage recon. F33 medium: Localization is visibly incomplete. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public surfaces did not present dates, prices, currencies, or locale-sensitive numeric data to format. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, event, or time-zone-dependent workflow was present in the representative public surfaces. |
be-trustworthyno-dark-patterns | issues | high | Lighthouse identified ad-widget links with empty href values that are rewritten on mouse events, while the page starts advertising/tracking before age verification is completed. F34 high: Advertising is visually mixed with site content and tracking starts behind the gate. |
be-trustworthyhumane-error-handling | issues | high | The login probe found username and password fields labelled as required with an asterisk, but required=false and no aria-invalid/error relationship. This prevents consistent native and accessible feedback. F35 medium: Login fields do not expose native validation state. |
be-trustworthytrustworthy-input-assistance | issues | high | The username and password fields have empty autocomplete attributes; search explicitly sets autocomplete=off. F36 medium: Sign-in and search fields do not provide useful autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The sampled account entry offers only username/password with no passkey path, while sessionId is neither Secure nor HttpOnly. F37 medium: Account entry lacks phishing-resistant authentication assistance. |
be-sustainableoptimised-assets | issues | high | Of 33 images, 29 used legacy formats, 25 lacked srcset, 18 below-fold images were not lazy, and 4 were oversized. F38 medium: Image delivery is not resolution or format efficient. |
be-sustainableno-wasteful-work | issues | high | The initial gate load downloaded a 1.0 MB media asset, four analytics configurations, multiple ad providers, and 2.59 MB of third-party data before user intent. F39 high: Large non-essential work runs before the gate is completed. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 98% of transferred bytes on the gate load, and the detail DOM contains four muted autoplay video elements without the primary media being started. F40 high: Third-party and autoplay media cost is disproportionate to the entry state. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing workflow exists, and exposing sensitive adult-site actions to agents is not an assumed requirement. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or inference task was part of the declared or observed core experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top listing scroll cycles, heap self size was 25.24 MB versus 24.83 MB baseline (+1.6%) and node count rose only 0.2%, with no evidence of unbounded growth in this bounded test. |
be-memory-efficientbounded-footprint | pass | high | Heap summaries measured about 25 MB self size for the media listing, proportionate to the loaded DOM, scripts, ads, and thumbnails in the tested state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap constructor summaries showed no Detached* population among dominant constructors and only small bounded total growth after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0058-www_youjizz_com.json
Report SHA-256: f1d62b6e4f31edafd7c922215353105599130e294b1ddff57511aec52267f131
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_youjizz_com/2026-07-18T03-09-34-178Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_youjizz_com/2026-07-18T03-09-34-178Z
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.