Manifest position 927 · CrUX rank bucket 1000
https://www.rat.xxx
Coverage complete
Atomic coverage complete: 58/58 checks judged across seven representative paths.
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-emulated screenshot is visually identical to the light capture; computed body remains rgb(244,244,244), color-scheme is normal, and the stylesheet probe found no prefers-color-scheme or light-dark(). F01 medium: The site ignores the user’s dark-colour preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned none; no auto-advance or essential motion was observed. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is unchanged, the CSS probe found no prefers-contrast or forced-colors rules, and axe found 63 contrast failures on the home page. F02 medium: High-contrast preferences receive no adaptation. |
implement-natural-interactionsview-transitions | issues | medium | DOM/CSS probes across the MPA templates found no view-transition-name or @view-transition usage. F03 low: Page changes are abrupt full-document swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists; native scrolling is static. |
implement-natural-interactionsphysical-gestures | pass | high | The exercised catalogue uses native links and scrolling and showed no custom pointer handlers that fight platform gestures. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The mobile home is 8,428px tall, while CSS inspection found no scroll-state query, progress indicator, or position-aware header behavior. F04 low: Long pages have static chrome and no scroll-position feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned overlay was present in the exercised paths. |
provide-guided-navigationdirects-attention | issues | medium | Representative MPA route changes reload without directional transition, target highlight, breadcrumb, or other attention cue. F05 low: Navigation does not cue where attention moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show the legal age-verification notice inline without obscuring the catalogue; content remains immediately visible. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No transient overlay or disclosure control was encountered; the legal age banner is inline content. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop and mobile screenshots are content-dense, with compact navigation and the primary catalogue occupying most of the viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All mobile layout captures report scrollWidth=clientWidth=360 and no horizontal overflow; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | All five template probes found no @container or container-type declarations despite reusable card grids and nav components. F06 low: Responsiveness is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size with 11 nodes; the probe found 36 visible controls below 24px on home and the first focused link had outline: none and no box shadow. F07 high: Touch and keyboard affordances are inadequate. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Headings, thumbnails and search make the catalogue purpose and next actions immediately clear across listing/detail pages. |
support-core-task-successprimary-flow-completion | issues | medium | The detail page exposes a custom .fake-player anchor and div-based player shell; no native video/iframe was present before interaction, and the anonymous click did not produce verifiable playback state. F08 high: The core watch flow is not predictably actionable. |
support-core-task-successclear-system-state-and-recovery | issues | high | A real 404 returns HTTP 404 but only renders “File not found.” with no title, viewport, navigation, search, or recovery action. F09 high: The 404 state is a dead end. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse performance is 0.93/0.94; traces show LCP 2.50s/2.38s, zero blocking time and layout CLS at or below 0.0034. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observers measured CLS 0 on home and 0.0034 on detail, both comfortably in the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Both traces report zero long tasks and zero total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | Trace LCP was 2,497ms home and 2,376ms detail; HAR shows the main document taking about 2.27s plus parser-inserted blocking CSS and non-deferred bundle/rat.js candidates. F10 medium: Document latency and blocking delivery delay meaningful paint. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse flags unused CSS and four unused-JS resources; HAR attributes 515,654 of 839,441 transferred bytes to scripts, led by duplicate Google tag payloads and Yandex. F11 medium: Unused and third-party JavaScript dominates transfer. |
be-inclusivenames-roles-labels | issues | high | axe reports a critical unnamed search button and an unnamed footer-logo link; both search inputs have no label or aria-label. F12 high: Important controls lack accessible names and labels. |
be-inclusivesufficient-contrast | issues | high | axe reports 63 serious contrast failures on home and 48 on the video template, including dates, metadata and age-verification subtext. F13 high: Text contrast fails at scale. |
be-inclusivestructure-and-focus | issues | high | axe reports no main landmark and content outside landmarks; the focused-link probe computed outline none and no box shadow. F14 high: Main landmarks and visible focus are missing. |
be-inclusivelegible-text | pass | high | Visual review at desktop and 360px shows readable line lengths and no clipping or overlapping text in primary cards/headings. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse target-size failed on 11 nodes; the video probe found no caption/subtitle tracks and no native media element before activation. F15 high: Small targets and captionless custom media reduce access. |
follow-best-practicesno-console-errors | issues | high | Lighthouse errors-in-console failed on the representative video page. F16 medium: The video template logs browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 90/100 home images and 78/95 detail images without width/height; Lighthouse also failed image aspect ratio on detail. F17 medium: Image markup is structurally wasteful and one detail image is distorted. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Both Lighthouse runs failed inspector-issues and BFCache diagnostics; the detail score was 0.69 for best practices. F18 medium: DevTools issues and BFCache blockers remain. |
be-discoverabletitle-and-description | pass | high | Every representative public template has a descriptive title and meta description; the detail page title is entity-specific. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse crawlable-anchors failed with five home links and four detail links; recon includes javascript:void(0) for “Our network”. F19 medium: Several links are not crawlable. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt advertises Sitemap: http://www.rat.xxx/sitemap.xml while public canonical URLs and the site are HTTPS. F20 low: The sitemap signal uses an insecure URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The video page has useful Open Graph tags but no JSON-LD or other structured data for VideoObject despite representing a rich video entity. F21 medium: Video entities lack structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP and nosniff are absent; 11 cookies were flagged insecure and PHPSESSID is not HttpOnly and uses SameSite=None. F22 high: Security headers and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence records six third-party origins and Google Analytics plus Yandex; HAR attributes 775,254/839,441 home bytes to non-main-origin requests and analytics cookies persist up to 400 days. F23 high: Tracking is broad and starts without an observed consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The signup surface exposes username/email/password fields, no passkey/WebAuthn signal, no autocomplete tokens, and a five-character minimum. F24 medium: Authentication is password-only and lacks modern credential support. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include X-Frame-Options and HSTS but omit Referrer-Policy, Permissions-Policy, CSP/frame-ancestors and X-Content-Type-Options. F25 high: Defensive browser policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures report 100% home and 99% detail content coverage without JavaScript; both are server-rendered rather than shells. |
be-resilientresilient-runtime-behaviour | pass | high | Representative listing, search and detail templates rendered without cut-off overlays or unstable async state; mobile overflow remained zero. |
be-resilientoffline-and-installable | issues | high | A standalone manifest with 192/512 icons is linked, but navigator.serviceWorker.getRegistrations() returned an empty array. F26 medium: The manifest suggests an app but there is no offline worker. |
be-resilientnetwork-and-http-failure-states | issues | high | A real 404 returns HTTP 404 but only renders “File not found.” with no title, viewport, navigation, search, or recovery action. F09 high: The 404 state is a dead end. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=en is correct, but all representative stylesheet probes found no logical sizing/spacing properties and no direction strategy. F27 medium: The globally accessible layout is not writing-mode ready. |
be-internationalisedlocale-aware-data | issues | medium | Cards render hard-coded-looking strings such as “9 years ago”; no locale selection or Intl-driven output was evident in representative DOM/CSS evidence. F28 low: Rendered dates are English-only relative strings. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, absolute time, recurring interval, or cross-zone coordination appears in the representative content. |
be-trustworthyno-dark-patterns | issues | high | The prominent age-verification banner says “we don’t store personal data,” while the initial load sets analytics identifiers lasting up to 400 days and contacts Google/Yandex trackers before any observed choice. F29 high: The privacy message conflicts with observed tracking. |
be-trustworthyhumane-error-handling | issues | high | The signup fields rely on placeholders, omit labels and required attributes, and provide empty generic field-error containers without observed accessible announcement semantics. F30 medium: Signup fields lack humane validation semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | Username, email and password inputs all have empty autocomplete values; email is type=text rather than email. F31 medium: Signup blocks useful autofill metadata. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Signup uses a password with a five-character minimum, no passkey option, no visible field labels, and consent is bundled into the submit action. F32 high: Account creation is weakly specified and not phishing-resistant. |
be-sustainableoptimised-assets | issues | high | The image audit found 96/100 home images in JPG/PNG/GIF and 62 without srcset; 90 lack intrinsic dimensions. F33 medium: Most images use legacy formats and lack responsive sources. |
be-sustainableno-wasteful-work | issues | high | On home, 59/62 requests and 775KB/839KB are outside the main origin; the largest scripts are duplicate Google tag payloads and Yandex. Detail adds a 155KB advertising origin. F34 high: Analytics and advertising work is disproportionate to page value. |
be-sustainablethird-party-and-media-budget | issues | high | On home, 59/62 requests and 775KB/839KB are outside the main origin; the largest scripts are duplicate Google tag payloads and Yandex. Detail adds a 155KB advertising origin. F34 high: Analytics and advertising work is disproportionate to page value. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This anonymous media catalogue exposes no agent-facing transactional capability; WebMCP is not presently applicable. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the representative media-browsing journey requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | A 20-toggle mobile menu exercise kept DOM nodes fixed at 2,301, added no listeners or intervals, and showed only 369KB heap variance between fresh equivalent sessions. |
be-memory-efficientbounded-footprint | pass | medium | The home state used about 12.5MB heap with 2,301 DOM elements, proportionate to a large thumbnail catalogue. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Twenty menu toggles added zero listeners/intervals and left live DOM count unchanged; no accumulating-session signal was observed. |
Provenance
Canonical report: results/atomic/reports/0927-www_rat_xxx.json
Report SHA-256: 9486f05dfbbbf3c6d2e1fd3c08955ccc1a8340d71fd0a58f63ec473b8416d9dc
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_rat_xxx/2026-07-23T22-08-35-194Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_rat_xxx/2026-07-23T22-08-35-194Z
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.