Manifest position 114 · CrUX rank bucket 1000

https://www.jennymovies.com

Coverage complete

Coverage-complete audit across six representative routes/conditions. The age-verification provider handoff was not submitted because it requires real user identity; the on-site gate itself was fully inspected.

Attempts

2 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Direct evidence for Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. F01 medium: The interface ignores the user’s light/dark preference.
respect-user-preferences `respects-reduced-motion`	issues	high	Direct evidence for Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. F02 medium: Reduced-motion users still receive dozens of infinite shimmer animations.
respect-user-preferences `respects-contrast`	pass	high	The prefers-contrast screenshot kept modal text, borders, controls, and actions visible; axe found no confirmed contrast violation.
implement-natural-interactions `view-transitions`	issues	high	Direct evidence for State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. F03 low: Page and state changes are abrupt despite browser support for View Transitions.
implement-natural-interactions `scroll-driven-animations`	pass	high	No scroll-linked animation exists, and CSS inspection found no scroll-event replacement or scroll-timeline misuse; trace recorded zero long tasks.
implement-natural-interactions `physical-gestures`	pass	high	The observed browse and form surfaces rely on native links, scrolling, and controls rather than custom pointer-drag handlers; mobile layout preserves native scrolling.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	Direct evidence for Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. F04 low: Scroll-aware chrome is implemented as static/legacy class toggling rather than declarative scroll state.
provide-guided-navigation `anchored-positioning`	issues	high	Direct evidence for Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. F05 low: Dropdown and overlay positioning does not use anchored fallback positioning.
provide-guided-navigation `directs-attention`	pass	high	Desktop and mobile screenshots show persistent labeled navigation and route-specific page headings; disclosure text clearly announces its effect.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	The only load-time interstitial is a clearly explained, safety/regulatory age-verification choice with multiple providers and legal/support links, not a marketing interruption.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	Direct evidence for Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. F06 high: The age-verification modal is a visual div, not an accessible modal, and background controls remain focusable.
maximize-content-reduce-noise `reduced-chrome`	pass	high	The content and contact screenshots use a compact header and simple full-width content/form treatment without decorative side rails or excessive framing.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	At the requested narrow mobile condition the layout primitive reported 0 horizontal overflow and the mobile screenshots show a two-column/stacked adaptive layout.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	Direct evidence for Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. F07 low: Reusable components respond only to viewport breakpoints.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Direct evidence for Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. F08 high: Keyboard focus is globally suppressed and invisible.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The homepage gate states “Please verify your age” and offers clearly named providers; the contact page has a specific heading and a single “Send Your Message” action.
support-core-task-success `primary-flow-completion`	pass	high	The legal entry flow exposes several explicit verification providers and support/privacy links without hidden fields; the contact flow presents all fields and its submit action in one view.
support-core-task-success `clear-system-state-and-recovery`	issues	high	Direct evidence for Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. F09 high: Required contact fields are not programmatically required and the error is not announced.
be-fast-and-stable `good-core-web-vitals`	pass	high	Lighthouse measured LCP 1.50s, CLS 0, and TBT 0; the trace measured FCP 349ms/LCP 365ms and zero blocking time.
be-fast-and-stable `visual-stability`	pass	high	Layout observation measured CLS 0 on mobile and 0.006 on desktop, both comfortably good; the gate uses bounded media boxes.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace and layout observers recorded no long tasks and 0ms total blocking time during the representative load.
be-fast-and-stable `efficient-resource-delivery`	issues	high	Direct evidence for Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. F10 medium: Static resources lack useful cache headers.
be-fast-and-stable `trim-unused-and-duplicate-code`	pass	high	The HAR captured only 15 requests/134,490 transferred bytes, no JavaScript resource category, and no third-party code on the gated entry surface.
be-inclusive `names-roles-labels`	pass	high	axe reported no names/roles/labels violation; image inspection found no missing alt text, and contact controls have associated labels.
be-inclusive `sufficient-contrast`	pass	medium	Visible screenshots are legible and axe/Lighthouse produced no confirmed color-contrast failure, although axe marked 18 nodes for manual contrast review.
be-inclusive `structure-and-focus`	issues	high	Focus probing found no visible indicator on controls; the homepage also has no main landmark and the visual modal lacks dialog semantics. F06 high: The age-verification modal is a visual div, not an accessible modal, and background controls remain focusable. F08 high: Keyboard focus is globally suppressed and invisible.
be-inclusive `legible-text`	pass	high	Contact and privacy screenshots show readable sizing, line height, wrapping, and spacing without clipping at their representative viewport.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Direct evidence for The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. F11 high: The viewport explicitly disables user zoom.
follow-best-practices `no-console-errors`	pass	high	Lighthouse best-practices completed at 0.96 and did not report the errors-in-console binary audit as a failure.
follow-best-practices `sound-document-and-assets`	issues	high	Direct evidence for Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) F12 low: Verification images omit intrinsic dimensions and one logo is delivered at the wrong density.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse reported no deprecated API, vulnerable-library, permission-on-load, or browser-platform binary failure; no cookies or prompts appeared on load.
be-discoverable `title-and-description`	issues	high	Homepage has a title/description, but /tags/ repeats the homepage title and heading instead of unique browse metadata. F14 medium: Browse routes and rich previews lack route-specific metadata.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Links use real hrefs and the viewport exists, but both response and page-level robots directives block indexing of a public sitemap entry. F13 medium: Public indexing signals conflict with the site’s sitemap and public routes.
be-discoverable `canonical-and-indexing-signals`	issues	high	Direct evidence for Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. F13 medium: Public indexing signals conflict with the site’s sitemap and public routes.
be-discoverable `structured-and-shareable-metadata`	issues	high	Direct evidence for Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. F14 medium: Browse routes and rich previews lack route-specific metadata.
be-private-and-secure `secure-transport-and-headers`	issues	high	Direct evidence for Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. F15 high: The CSP permits any origin plus unsafe inline script and eval, and defensive headers are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	pass	high	Initial-load tracker and HAR captures found zero third-party requests, zero known trackers, and zero cookies; the secrets scan found no client-side secret.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No geolocation/notification prompt or authentication form fires on load; identity verification is initiated only after a user chooses a named provider.
be-private-and-secure `defensive-browser-policies`	issues	high	HSTS and clickjacking protection are present, but CSP is broadly permissive and nosniff/Permissions-Policy are missing. F15 high: The CSP permits any origin plus unsafe inline script and eval, and defensive headers are incomplete.
be-resilient `progressive-enhancement`	issues	high	Direct evidence for Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles. F16 medium: Core forms do not progressively enhance without JavaScript.
be-resilient `resilient-runtime-behaviour`	pass	high	The age overlay itself scrolls within the viewport, the disclosure toggled repeatedly without state corruption, and heap growth remained bounded.
be-resilient `offline-and-installable`	issues	high	Direct evidence for Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) F17 low: The site advertises a standalone web app but has no active service worker or offline fallback.
be-resilient `network-and-http-failure-states`	pass	high	A synthetic missing route resolved to a real HTTP 404 response rather than a misleading 200 shell; representative pages remained server-rendered.
be-internationalised `lang-dir-and-logical-properties`	issues	high	Direct evidence for Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. F18 high: Localized routes declare the wrong document language and provide no hreflang.
be-internationalised `locale-aware-data`	not-applicable	high	No locale-sensitive values were present on the homepage, contact, tags, or privacy templates.
be-internationalised `time-zone-correctness`	not-applicable	high	No time-zone-sensitive journey was present in representative routes.
be-trustworthy `no-dark-patterns`	pass	high	The legally required age gate describes each verification choice, marks recommendations explicitly, and links privacy/terms/contact information without confirmshaming.
be-trustworthy `humane-error-handling`	issues	high	Direct evidence for Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. F19 medium: Contact form recovery is delayed to custom JavaScript instead of native, humane validation.
be-trustworthy `trustworthy-input-assistance`	issues	high	Direct evidence for Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. F20 low: Contact inputs omit autofill hints.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	Recon found browse, legal, age-verification, search, and contact surfaces only.
be-sustainable `optimised-assets`	issues	high	Assets are modern and the transfer is light, but five images lack intrinsic dimensions and one verification logo is oversized/incorrect density. F12 low: Verification images omit intrinsic dimensions and one logo is delivered at the wrong density.
be-sustainable `no-wasteful-work`	issues	high	Direct evidence for Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. F21 medium: Hidden and placeholder cards run continuous shimmer work even when reduced motion is requested.
be-sustainable `third-party-and-media-budget`	pass	high	HAR and tracker capture found zero third-party requests and a light 134,490-byte initial transfer with no autoplay media.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	Recon found ordinary navigation, search, age verification, and a contact form only.
be-agent-ready `on-device-inference`	not-applicable	high	Representative pages contain no inference workflow.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After 20 open/close disclosure toggles, heap self-size rose only 9,596 bytes (0.34%) and node count 330, with no monotonic leak signal.
be-memory-efficient `bounded-footprint`	pass	high	Baseline heap self-size was 2.86MB for a 134KB/15-request entry surface, proportionate to the rendered modal and navigation.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	medium	Repeated toggling did not produce a Detached constructor in either summary; closures increased by only 15 and objects by 6 after 20 toggles.

Provenance

Canonical report: results/atomic/reports/0114-www_jennymovies_com.json
Report SHA-256: 83936fe751ba2fb54a298015e7767a03e9881e5fa7d29b9a9e22a134c98afb16
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_jennymovies_com/2026-07-25T20-09-37-038Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_jennymovies_com/2026-07-25T20-09-37-038Z
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.