Manifest position 277 · CrUX rank bucket 1000
https://www.fpo.xxx
Coverage complete
Coverage-complete representative audit of listing, video-detail, sites-index, and error templates. The third-party age-verification flow itself was assessed from its entry state but not completed.
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 | Dark emulation leaves color-scheme normal and the same white page/blue-white age gate as light mode. F01 medium: 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. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, document.getAnimations() returned no active animations. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast capture keeps the age-verification text and Start control visible. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules and navigation is conventional full-document replacement. F02 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The representative pages contain no parallax, scrollytelling, or scroll-linked animation to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, carousel, drag, or other gesture-driven surface was present on the representative pages. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long 6,562 px mobile listing has static navigation and no scroll-state query, progress indicator, or position-aware chrome. F03 low: 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. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or contextual menu requiring anchored placement appeared on the audited templates. |
provide-guided-navigationdirects-attention | issues | high | Primary icon navigation links have no text, title, or accessible label, and focused controls receive no visible outline, so location and focus movement are not cued. F04 medium: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial viewport is completely obscured by a third-party age-verification overlay before any content can be inspected; only an unexplained Start action is offered. F05 medium: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The rendered DOM contains no dialog, popover, or details primitive while the screenshot shows a modal age gate. F06 medium: 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. |
maximize-content-reduce-noisereduced-chrome | issues | high | The 404 state begins with multiple promotional/ad calls before the error and recovery content, while the first viewport is dominated by third-party gate chrome. F07 medium: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, both home and sites templates reported 0 px horizontal overflow with viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Stylesheet inspection found no @container rules (container-type normal); reused cards adapt only through page-wide CSS. F08 medium: 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. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probe found outline-style none and no replacement box-shadow on links, search input, menu button, and content cards. F09 medium: 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. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Title, description, listing cards, and video-detail H1 clearly identify the site purpose and primary content choices. |
support-core-task-successprimary-flow-completion | issues | high | The primary watch flow is intercepted on load by a third-party age check that exposes only “Start”, with no up-front explanation of steps, data use, alternatives, or return path. F10 high: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | pass | high | A nonexistent route renders a clear “404 / Page not found” state and retains working navigation/content links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.8 s (poor), CLS 0.047, and TBT 20 ms; trace corroborated LCP 3.45 s with no long tasks. F11 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observed CLS 0.018 and Lighthouse measured CLS 0.047, both in the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0 ms TBT; Lighthouse TBT was 20 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found missing cache headers on core CSS, JS, font, logo, and thumbnails; Lighthouse estimated 930 ms render-blocking savings. F12 medium: 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. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 125 KiB unused JavaScript and 18 KiB unused CSS; third-party scripts account for substantial transfer cost. F13 medium: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | axe reports a nameless menu button and untitled iframe; the search input has no label, and several nav anchors have no accessible text. F14 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | axe measured repeated listing metadata at 2.42:1 and 1.89:1 against white, below the 4.5:1 requirement. F15 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | axe found no main landmark and no H1 on home; focus probe found no visible focus indicator on tested controls. F16 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | Computed styles show 12 px navigation/card metadata; axe confirms low-contrast metadata, reducing reading comfort. F17 medium: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The detail page exposes videos with no caption/subtitle tracks; top links are only about 14 px tall, despite otherwise successful mobile reflow. F18 medium: 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. |
follow-best-practicesno-console-errors | pass | high | Lighthouse console-error audit passed; observed failed age-verification analytics requests were network aborts rather than uncaught page exceptions. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but image audit found 2 images without dimensions and 21 without responsive srcset. F19 medium: 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.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three BFCache failure reasons and DevTools inspector issues. F20 low: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | Home and detail pages have descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport meta and robots are sound, but Sign up, Log in, and Support are anchors without href; Lighthouse crawlable-anchors failed. F21 medium: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home/detail canonical URLs are present, robots permits public content, sitemap index exists, and tested pages return successful indexable responses. |
be-discoverablestructured-and-shareable-metadata | pass | high | Detail page supplies breadcrumb JSON-LD and comprehensive Open Graph video metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, and nosniff are absent; all seven cookies were flagged insecure, including PHPSESSID without Secure or HttpOnly. F22 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Load contacted 14 third-party origins, including analytics and ad-tech trackers; 19 third-party requests transferred 219,033 bytes. F23 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login/signup surfaces exist, but runtime/source inspection found no WebAuthn/passkey capability; the third-party age check starts without data-use context. F24 medium: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | X-Frame-Options is present, but HSTS, Referrer-Policy, Permissions-Policy, CSP/frame-ancestors, and nosniff are absent. F25 medium: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 99% raw-HTML content coverage and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | MPA content renders from HTML, mobile templates have no overflow, and no clipped contextual menus were present. |
be-resilientoffline-and-installable | not-applicable | high | This streaming/catalog site is intrinsically network-dependent and is not positioned as an installable app; the manifest has no start_url and no service worker is registered. |
be-resilientnetwork-and-http-failure-states | pass | high | A tested missing route returns HTTP 404 and shows a clear page-not-found state with navigation options rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=en is correct, but stylesheet inspection counted 195 physical left/right declarations and zero logical inline/block properties. F26 medium: 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. |
be-internationalisedlocale-aware-data | issues | high | Visible dates use hard-coded forms such as 17/7/26, with no locale selection or locale-aware rendering signal. F27 low: Dates, numbers, currencies, durations and calendar systems are formatted locale-aware (Intl), location-agnostic where stored, and recurring intervals and event differentials are modelled correctly. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled events, timestamps, recurring intervals, or timezone-sensitive user data occur in the representative templates. |
be-trustworthyno-dark-patterns | issues | high | The 404 state places multiple sexually charged promotional calls before recovery content, and the age gate provides only “Start” without explaining the consequence. F28 medium: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | pass | high | The tested 404 state is plainly named and keeps navigation available without blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | The search field has no programmatic label and no visible instruction beyond a generic Search value; signup/login are href-less scripted anchors. F29 medium: 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. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Signup/login and age verification are offered without visible privacy, data-use, cancellation, or account-flow context in the initial state. F30 medium: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | Image audit found 17 below-fold images without native lazy loading, 21 without srcset, and 8 legacy-format images. F31 medium: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | Lighthouse reports 125 KiB unused JavaScript and 18 KiB unused CSS, while analytics/ad scripts run before the gate is completed. F32 medium: 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. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 19 requests and 219,033 transferred bytes; 14 third-party origins include ad-tech and analytics. F33 medium: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site is a conventional public media catalog with no declared agent workflow or in-page generative feature. |
be-agent-readyon-device-inference | not-applicable | high | The site is a conventional public media catalog with no declared agent workflow or in-page generative feature. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The third-party age gate prevented a safe repeatable first-party interaction; synthetic scrolling was not treated as a valid leak workflow. |
be-memory-efficientbounded-footprint | pass | high | Independent loaded-state heap summaries were about 8.02 MB and 8.03 MB, a ~15.7 KB difference, with no evidence of an unbounded footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Single-state heap summaries showed only a 201-node difference across independent loads; no Detached constructor growth or repeated-listener signal was observed. |
Provenance
Canonical report: results/atomic/reports/0277-www_fpo_xxx.json
Report SHA-256: 0fb973d88174bb3373a415b009ac056bbb7cf916e5358e26d88df013edc33dc7
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fpo_xxx/2026-07-19T15-56-54-826Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fpo_xxx/2026-07-19T15-56-54-826Z
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.