Manifest position 776 · CrUX rank bucket 1000
https://fra.xhspot.com
Coverage complete
Coverage complete. Lighthouse and one HAR attempt encountered intermittent HTTP 503; first-party trace, raw CDP probes, screenshots, DOM, axe, headers, cookies, trackers, images, discoverability, and heap evidence completed all checks.
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 | pass | high | Screenshot and preference probe show a usable dark surface and authored prefers-color-scheme rules. |
respect-user-preferencesrespects-reduced-motion | issues | high | The preferences probe under prefers-reduced-motion: reduce found eight running shimmer-56cf2 animations, each with a 2000 ms duration. F001 medium: Loading shimmer animations continue when reduced motion is requested |
respect-user-preferencesrespects-contrast | issues | high | axe-core reported 48 color-contrast nodes; the preference/CSS probe found no prefers-contrast or forced-colors rule in accessible styles. F002 low: The default palette has widespread contrast failures and no observed contrast-specific adaptation |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no authored View Transition rules on the representative listing and detail routes, and route navigation performs full abrupt swaps. F003 low: Navigation changes are abrupt and do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was present on the representative paths. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, drag, or snap-based primary interaction was present on the representative paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Screenshots show the same tall header and persistent 190 px sidebar; DOM/CSS inspection found no scroll-state-driven treatment. F004 low: The large fixed navigation chrome does not adapt as users scroll |
provide-guided-navigationanchored-positioning | pass | high | Visible header/sidebar navigation remained attached without clipped transient overlays on all captured paths. |
provide-guided-navigationdirects-attention | pass | high | Active underline, headings, and persistent category navigation clearly indicate location on listing/category paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, categories, and detail screenshots all show a centered 525 px-wide consent overlay covering the page before interaction. Refuse is available, but the content remains obscured. F005 medium: A consent interstitial obscures the primary content on every fresh load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Recon found zero dialog or popover elements while the screenshot shows a modal-like blocking surface. F006 medium: The blocking consent overlay is not exposed as a native dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | At 360 px, the 190 px sidebar plus clipped content and the full header leave roughly half the visual viewport for the feed. F007 high: Persistent desktop chrome crowds out content on a narrow viewport |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout evidence reports 664 px horizontal overflow on both homepage and categories (scrollWidth 1024, visual viewport 360). The detail template lacks viewport meta and is scaled to 0.367. F008 critical: Homepage and category templates force a 1024 px desktop layout into a 360 px viewport |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The same desktop sidebar/content arrangement remains 1024 px wide on two narrow listing templates, clipping the content rather than adapting. F009 high: Reused listing/navigation components do not adapt to their available container |
adapt-to-the-form-factorinput-modality-aware | issues | high | axe-core found an aria-hidden login section containing focusable content and one nested interactive control, both of which can disrupt keyboard and assistive-technology interaction. F010 medium: Keyboard semantics and focus containment have serious defects |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and category screenshots have descriptive H1s and immediately visible linked media/cards. |
support-core-task-successprimary-flow-completion | pass | high | A homepage content link resolved to a detail page with matching H1, title, creator, and primary viewing action. |
support-core-task-successclear-system-state-and-recovery | issues | high | HAR and direct fetch attempts received HTTP 503 responses containing only the stock nginx “Service Temporarily Unavailable” page; no retry, status, or navigation action was offered. F011 high: Server failures expose a generic dead end with no recovery action |
be-fast-and-stablegood-core-web-vitals | pass | high | Trace measured FCP/LCP 1083.51 ms, TBT 116.17 ms; layout captures measured CLS 0. |
be-fast-and-stablevisual-stability | pass | high | Homepage and category layout observers recorded CLS 0 with no shift entries. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found two long tasks, longest 157.86 ms, with 116.17 ms total blocking time, acceptable for this load. |
be-fast-and-stableefficient-resource-delivery | issues | high | The image audit found 29/36 homepage images and 28/32 detail images without explicit dimensions, 12 oversized homepage images, and multiple below-fold images without lazy loading. F012 medium: Image delivery is inefficient across listing and detail templates |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The live tracker probe observed 139 resources from 15 origins, including 14 third-party origins and 81 requests to static-ah.xhcdn.com. F013 medium: A large third-party/request surface is loaded for the initial experience |
be-inclusivenames-roles-labels | issues | high | axe-core found prohibited ARIA on a video span, an aria-hidden region containing focusable content, and a nested interactive control. F014 high: ARIA role/name semantics contain serious violations |
be-inclusivesufficient-contrast | issues | high | axe-core reported 48 color-contrast failures across headings, active navigation, metadata, and consent text. F015 high: Text and controls fail WCAG AA contrast at scale |
be-inclusivestructure-and-focus | issues | high | axe-core reported non-unique landmarks, a nested complementary landmark, seven regions outside landmarks, and focusable content inside aria-hidden UI. F016 medium: Landmark and focus structure is not robust |
be-inclusivelegible-text | pass | high | Screenshots show readable text sizing and stable card-title wrapping, apart from separately reported contrast/reflow defects. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The detail layout reports hasViewportMeta=false and Chrome scales a 980 px layout to 0.367 on a 360 px device. F017 high: The detail page prevents proper mobile reflow by omitting viewport metadata |
follow-best-practicesno-console-errors | pass | high | A five-second active error/unhandledrejection observer recorded zero runtime errors after load. |
follow-best-practicessound-document-and-assets | issues | high | Image probes found dimensions missing on 29 of 36 homepage images and 28 of 32 detail images, with 12 homepage images over twice their display width. F018 medium: Most content images omit intrinsic dimensions and several are oversized |
follow-best-practicesbrowser-platform-hygiene | pass | high | No permission prompt appeared, Notification.permission remained default, and the representative paths completed without browser-blocking UI. |
be-discoverabletitle-and-description | pass | high | Homepage, category, and detail probes found unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The mobile detail layout directly reports hasViewportMeta=false; the page renders as a 980 px desktop canvas scaled down. F019 high: The public video-detail template has no viewport meta tag |
be-discoverablecanonical-and-indexing-signals | issues | high | Both in-page fetches returned HTTP 503 for /robots.txt and /sitemap.xml during the run, while the main document was otherwise reachable. F020 medium: robots.txt and sitemap.xml were intermittently unavailable |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail probe found Open Graph metadata but zero application/ld+json scripts for a page representing a video entity. F021 medium: The video detail has social tags but no structured VideoObject data |
be-private-and-securesecure-transport-and-headers | issues | high | CSP is only frame-ancestors self; three of four cookies were flagged insecure, including settings and x_csrf_token without Secure, and settings uses SameSite=None. F022 high: Transport is HTTPS, but XSS/header protection and cookie flags are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe observed 14 third-party origins, including accounts.google.com, tsydicate.com, img.doppiocdn.com, multiple CDNs, and collection endpoints. F023 medium: The initial page contacts a broad third-party surface |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No notification permission was requested on load (permission remained default); authentication was not forced into the public browsing flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no X-Content-Type-Options, no Referrer-Policy, a narrow Permissions-Policy, CSP limited to frame-ancestors, and HSTS max-age of only 86400 seconds. F024 medium: Several browser-enforced defenses are absent or too weak |
be-resilientprogressive-enhancement | pass | high | Discoverability evidence found 74% raw/rendered text overlap, title/H1/description in raw HTML, and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Three representative routes rendered stable navigation/content without cut-off overlays after load. |
be-resilientoffline-and-installable | pass | high | A valid manifest was fetched and an active service worker controlled the full origin scope. |
be-resilientnetwork-and-http-failure-states | issues | high | The captured 503 response is a generic server page with no explanation, retry control, or preserved site navigation. F025 high: Network/server failure handling falls back to an unhelpful nginx page |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=fr and recon exposes localized alternate-domain links for dozens of languages including RTL languages. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public paths display no dates, currencies, or locale-sensitive numeric input requiring formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public paths expose no scheduling or time-zone-sensitive event data. |
be-trustworthyno-dark-patterns | pass | high | The consent surface gives Accept and Refuse equal size/prominence and provides policy links and later preference management. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited public discovery flow has no data-entry form beyond site search; account and creator forms require separate account journeys. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The public flow contains only search/filter text inputs, for which address, payment, sign-in, or sign-up autocomplete tokens do not apply. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription management, and account controls were outside the unauthenticated representative paths and were not invoked. |
be-sustainableoptimised-assets | issues | high | The homepage image probe found 12 oversized images and 17 legacy-format resources; detail found two oversized and 18 legacy-format resources. F026 medium: Image bytes and formats are not consistently matched to rendered size |
be-sustainableno-wasteful-work | issues | high | The page recorded 139 resource entries and 14 third-party origins before user interaction, with one CDN alone receiving 81 requests. F027 medium: The initial route performs a high volume of distributed network work |
be-sustainablethird-party-and-media-budget | issues | high | Fourteen third-party origins are contacted during initial load, before the user selects a media item; this adds connection and processing overhead. F028 medium: Third-party integrations are disproportionate on the first view |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent or visible agent-facing capability exists; this emerging contextual capability is not expected for the public media-browsing surface. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited paths requires on-device inference, and no developer intent indicates it should be provided. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Baseline versus post-interaction heap summaries changed from 33.77 MB to 35.76 MB after ten player toggles; growth was modest (5.9%) and no Detached constructor entered top retained classes. |
be-memory-efficientbounded-footprint | pass | high | Live metrics reported 22.8 MB used JS heap and 1,804 DOM elements; heap summary was 33.77 MB, proportionate to a media listing/detail app. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries showed no Detached constructor among top retained classes after ten repeated toggles. |
Provenance
Canonical report: results/atomic/reports/0776-fra_xhspot_com.json
Report SHA-256: f0a22dad86191edcb56f01d34aa5d93e70557bf2a7b5f97f45e1362c67b17c5e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/fra_xhspot_com/2026-07-22T23-39-12-826Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/fra_xhspot_com/2026-07-22T23-39-12-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.