Manifest position 973 · CrUX rank bucket 1000
https://ww1.goojara.to
Coverage complete
Coverage-complete representative audit of homepage, listing, detail/watch, search and failure/crawler states. Playback and outbound direct links were not activated; the loaded player surface and embedding behavior were inspected.
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 preferences screenshot is pixel-identical to the normal capture while prefers-color-scheme: dark is active; computed body background remains transparent and the white cards/navigation do not retint. F01 medium: The interface is fixed to a light palette. |
respect-user-preferencesrespects-reduced-motion | pass | high | No active animations were returned under prefers-reduced-motion: reduce, so there is no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | issues | high | Under prefers-contrast: more the page remains unchanged, while axe reports 2.53:1 on the search control and 3.63:1 on media badges. F02 medium: High-contrast preference does not improve already weak control contrast. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no View Transition usage; navigation and injected search/list state swap instantly. F03 low: Route and state changes are abrupt. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The audited pages implement no scroll-linked visual motion, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The catalog exposes ordinary links and scrolling but no custom gesture-driven interaction requiring a gesture implementation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 2,213px mobile homepage has static, non-sticky navigation and no progress or scrolled-state treatment. F04 low: Long catalog pages provide no scroll-state cue or persistent orientation. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or menu overlay exists on the audited templates. |
provide-guided-navigationdirects-attention | pass | high | Active nav/tab styling, breadcrumbs on detail pages and clear current-item headings orient users after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across home, listing and detail show content immediately with no popup or interstitial covering it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlay, modal, disclosure or rich picker exists on the audited templates. |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots show compact navigation and content-dominant catalog/detail layouts without excessive application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | 360x800 layout metrics report 0px horizontal overflow on home and detail; both reflow into usable single-column layouts. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Captured CSS uses @media min-width rules and fixed percentages but no container queries, despite cards/components appearing in multiple-width contexts. F05 medium: Responsive behavior is tied only to viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | CSS globally sets a { outline: 0 }; many navigation/list links are only 30–36px high, below a comfortable touch target. F06 high: Keyboard focus and touch target support are weak. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage navigation, search, catalog cards and the detail player surface make browse/search/watch next steps visually apparent. |
support-core-task-successprimary-flow-completion | pass | high | The exercised browse-to-detail and search-result journeys returned usable content and a visible player surface without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | Search injects results without a live status/loading announcement; a nonexistent route returns a bare nginx 404 with no route back or retry guidance. F07 medium: Search and failure states lack useful status and recovery messaging. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse reports LCP 1.7s, CLS 0 and TBT 0ms; trace reports LCP 111ms and no long tasks in its capture. |
be-fast-and-stablevisual-stability | pass | high | Home CLS is 0; detail mobile CLS is 0.0353, within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout evidence report no long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR records 14 successful requests, 99KB transferred, no redirects/errors/uncompressed-text or missing-cache signals; one small parser stylesheet is the only blocking candidate. |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | high | Homepage HAR is small and ships no external JavaScript bundle; no duplicated or dominant script payload was observed. |
be-inclusivenames-roles-labels | pass | high | axe reports passes for link-name, image-alt, label and form-field-multiple-labels; poster images have descriptive alt text. |
be-inclusivesufficient-contrast | issues | high | axe and Lighthouse identify search text at 2.53:1, badges at 3.63:1, and an in-text link distinguishable only by weak color contrast. F08 high: Essential text and controls fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | axe reports landmark-one-main, page-has-heading-one and region violations; authored CSS removes anchor outlines. F09 high: The homepage lacks a main landmark, an H1, and robust focus styling. |
be-inclusivelegible-text | issues | high | Authored CSS uses 11px body text and 11–12px metadata/list labels across primary content, visible as cramped text in desktop and mobile captures. F10 medium: Body and metadata text are unusually small. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Mobile captures show 30–36px tab/navigation targets; the embedded iframe surface provides no host-page track or transcript metadata. F11 medium: Many controls are undersized for touch and the player exposes no caption evidence. |
follow-best-practicesno-console-errors | issues | high | Lighthouse records TypeError: Cannot read properties of null (reading classList) at the homepage XHR callback. F12 medium: The homepage throws an uncaught runtime error. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found width/height attributes missing on all eight homepage images; layout is currently held by wrapper CSS rather than intrinsic metadata. F13 low: Image markup omits intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices is 0.96 and evidence found no permission prompt, deprecated-library payload or paste prevention on load. |
be-discoverabletitle-and-description | issues | high | DOM captures show meta name="description" content="" on the homepage, listing and detail templates; Lighthouse fails meta-description. F14 medium: Public pages have empty meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability measured only 39% raw/rendered word coverage; its no-JS browser screenshot received Cloudflare Error 1015 rate limiting while browser rendering succeeded. F15 medium: Non-JavaScript crawler access is inconsistent and much content depends on XHR. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical links exist, but /sitemap.xml returns 404 and robots.txt contains rights-reservation prose without a sitemap declaration. F16 medium: Indexing support is incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The movie detail DOM contains visible title, duration, genre, date, description and cast but no JSON-LD or Open Graph metadata. F17 medium: Detail pages lack structured and social metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence reports no CSP, HSTS or nosniff; one first-party cookie lacks Secure/HttpOnly and both cookies use SameSite=None. F18 high: Transport is HTTPS, but core browser defenses and cookie attributes are weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The detail DOM immediately loads a wootly.ch iframe and script before playback intent; the homepage HAR already attributes 86% of bytes to another origin. F19 high: The detail page eagerly embeds third-party streaming code without an explicit privacy boundary. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission request or authentication surface is present in the representative public paths. |
be-private-and-securedefensive-browser-policies | issues | high | Only X-Frame-Options is present; HSTS, CSP/frame-ancestors, Referrer-Policy, Permissions-Policy and nosniff are absent. F20 high: Defensive browser policies are mostly absent. |
be-resilientprogressive-enhancement | issues | high | Only 39% of rendered content words occur in raw HTML and the crawler screenshot was replaced by Cloudflare Error 1015; recent results are XHR-injected. F21 high: Primary current-content coverage degrades without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Lighthouse captured an uncaught classList access in the XHR callback, demonstrating fragile runtime state handling. F22 medium: An asynchronous list callback assumes missing DOM state. |
be-resilientoffline-and-installable | not-applicable | high | Streaming playback is intrinsically online and the site does not present itself as an installable application; offline media/installability is not a credible requirement here. |
be-resilientnetwork-and-http-failure-states | issues | high | A representative missing route returns a bare nginx 404 with no branded explanation, search, retry or path back. F23 medium: HTTP failure handling falls through to a generic server page. |
be-internationalisedlang-dir-and-logical-properties | issues | high | All captured templates have html lang=null; CSS extensively uses left/right padding and positioning rather than logical properties. F24 high: The document does not declare its language and uses physical-direction CSS. |
be-internationalisedlocale-aware-data | issues | high | Detail markup renders “133min” and “April 2026” directly with no locale metadata or alternate formatting. F25 low: Visible dates and durations are hard-coded English strings. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited pages expose month/year release metadata but no event times, schedules or timezone-sensitive operations. |
be-trustworthyno-dark-patterns | pass | high | Audited surfaces show direct browse/watch labels, no consent nag, confirmshaming, forced continuity or disguised checkout. |
be-trustworthyhumane-error-handling | not-applicable | high | There is no submission form with required or invalid-field states; search is an immediate filter. |
be-trustworthytrustworthy-input-assistance | issues | high | The primary search input has placeholder text but no name, label, autocomplete or search input type. F26 low: Search input assistance is underspecified. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management flow is exposed. |
be-sustainableoptimised-assets | issues | high | The images primitive found eight legacy JPG/GIF assets, no modern formats, no srcset, and no intrinsic dimensions. F27 medium: Catalog images use only legacy formats and no responsive source selection. |
be-sustainableno-wasteful-work | pass | high | Trace has no long tasks and HAR is 99KB with 14 requests; no periodic background work or analytics chatter was observed. |
be-sustainablethird-party-and-media-budget | issues | high | The detail template eagerly creates a cross-origin player iframe and remote script on initial load rather than using a poster and click-to-load boundary. F28 high: Third-party media is loaded before playback intent. |
be-agent-readystructured-agent-capabilities | not-applicable | high | WebMCP is emerging and this public browse/watch site declares no intent to expose agent-facing actions; absence is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative feature exists for which on-device inference would currently improve the audited journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 real search updates, heap self-size rose about 8.4% to 1.80MB while closures remained exactly 1,945 and JS heap used remained about 1.17MB; the final DOM increase corresponds to the rendered result set, with no evidence of unbounded retention in this window. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is 1.66MB/37,982 snapshot nodes and Performance memory reports about 1.17MB used for a 432-element page, proportionate to this simple catalog. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries show stable closure/object counts and no Detached* constructor population; listener/timer internals were not directly introspectable, so confidence is medium. |
Provenance
Canonical report: results/atomic/reports/0973-ww1_goojara_to.json
Report SHA-256: 88986ce2b47c1cb9cf29e133bdb2da3a23c1303b77d232ef87e48775cf442f7e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ww1_goojara_to/2026-07-24T05-39-46-704Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ww1_goojara_to/2026-07-24T05-39-46-704Z
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.