Manifest position 22 · CrUX rank bucket 1000
https://www.disneyplus.com
Coverage complete
Coverage-complete representative audit of the public UK landing, plan, login-entry, and recovery surfaces. Authenticated playback, payment submission, account cancellation, and media captions were not covered because they require an account or transaction.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | pass | medium | Screenshot comparison under default and prefers-color-scheme: dark remained usable and consistently dark. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Reduced-motion emulation was active; getAnimations() returned none on the loaded state. |
respect-user-preferencesrespects-contrast | pass | medium | Forced-colors screenshot retained readable text, links, controls, and focus borders. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules; homepage-to-login is a full abrupt route change. F03 low: Primary route changes do not expose View Transition styling. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation was present on the representative public pages, so there is no implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | medium | Native DETAILS/SUMMARY interactions are used and no custom pointer-driven gesture handler was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The page is 5,057px tall at desktop, while CSS inspection found no scroll-state queries or progress affordance. F04 low: The long marketing page has no scroll-state-aware navigation affordance. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or viewport-edge menu was present in the tested public flow. |
provide-guided-navigationdirects-attention | pass | medium | Headings, plan links, FAQ disclosure state, and recovery links provide clear directional cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a modal consent wall covering the hero; on 360x800 it occupies nearly the entire viewport. F01 medium: The privacy prompt obscures the primary content on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe found two DIV role=dialog aria-modal=true overlays and no dialog element. F02 medium: The consent experience is a custom ARIA dialog rather than the platform dialog primitive. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Outside the consent interruption, the visual hierarchy is content-led with restrained persistent chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800, scrollWidth equalled clientWidth (360px), with zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The mobile layout avoids overflow, but CSS inspection found no @container rules despite reusable plan and media-card components. F05 low: Responsive behavior relies on viewport styling rather than component containment. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The target probe found Learn more links at 14px high and many footer links at 22px high. F06 medium: Several interactive targets are shorter than recommended touch dimensions. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The hero states the streaming offer and exposes SIGN UP NOW plus LOG IN. |
support-core-task-successprimary-flow-completion | pass | medium | Plan and login entry paths loaded successfully with clear pricing/identity progression; payment was intentionally not submitted. |
support-core-task-successclear-system-state-and-recovery | pass | medium | A nonexistent route rendered a specific error, explanation, and DISNEY+ HOME recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 8.4s, LCP 30.8s, TBT 580ms and performance 0.41; the first-party trace still measured LCP 5.18s. F07 high: The public landing page is slow under lab conditions. |
be-fast-and-stablevisual-stability | pass | medium | Layout observers measured CLS 0 on desktop and mobile. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured FCP 8.4s, LCP 30.8s, TBT 580ms and performance 0.41; the first-party trace still measured LCP 5.18s. HAR recorded 1.47MB of script transfer and a 1,009,508-byte _app chunk; Lighthouse estimated 581KiB unused JavaScript and 66KiB unused CSS. F07 high: The public landing page is slow under lab conditions. F08 high: A large JavaScript payload dominates startup. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse measured FCP 8.4s, LCP 30.8s, TBT 580ms and performance 0.41; the first-party trace still measured LCP 5.18s. HAR recorded 1.47MB of script transfer and a 1,009,508-byte _app chunk; Lighthouse estimated 581KiB unused JavaScript and 66KiB unused CSS. F07 high: The public landing page is slow under lab conditions. F08 high: A large JavaScript payload dominates startup. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 1.47MB of script transfer and a 1,009,508-byte _app chunk; Lighthouse estimated 581KiB unused JavaScript and 66KiB unused CSS. F08 high: A large JavaScript payload dominates startup. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility was 0.99 but failed heading-order and label-content-name-mismatch; the overall heading sequence is not strictly descending. F09 medium: Heading order and accessible-name consistency have defects. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse accessibility scored 0.99 and did not report a contrast failure; forced-colors remained legible. |
be-inclusivestructure-and-focus | issues | high | Lighthouse accessibility was 0.99 but failed heading-order and label-content-name-mismatch; the overall heading sequence is not strictly descending. F09 medium: Heading order and accessible-name consistency have defects. |
be-inclusivelegible-text | pass | medium | Images had alt text, labels were present on login, focus-visible produced an outline, and text remained readable. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The target probe found Learn more links at 14px high and many footer links at 22px high. F06 medium: Several interactive targets are shorter than recommended touch dimensions. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse did not report console-error or uncaught-exception failures. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 22/43 images missing dimensions, 17 oversized, and 19 without srcset; the logo source was 3837px wide for a 91px display. F13 medium: Many images are oversized or lack intrinsic/responsive metadata. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found three BFCache failure reasons and Inspector Issues; best-practices scored 0.77. F16 medium: The page reports browser hygiene problems. |
be-discoverabletitle-and-description | pass | medium | The page exposes title, description, canonical, JSON-LD, Open Graph, sitemap and bot-specific robots allowances. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability measured 52% rendered-word coverage; the raw response lacked the final title and H1, although server HTML was not an empty shell and bot-specific robots rules allow indexing. F14 medium: Important rendered semantics are incomplete in raw HTML. |
be-discoverablecanonical-and-indexing-signals | pass | medium | The page exposes title, description, canonical, JSON-LD, Open Graph, sitemap and bot-specific robots allowances. |
be-discoverablestructured-and-shareable-metadata | pass | medium | The page exposes title, description, canonical, JSON-LD, Open Graph, sitemap and bot-specific robots allowances. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, X-Content-Type-Options, frame protection, Referrer-Policy, or Permissions-Policy. Cookie inspection found OptanonConsent and _dd_s without Secure on an HTTPS-only property. F10 high: The main document lacks baseline defensive headers. F11 medium: Two first-party cookies are set without Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The consent copy states 77 partners; HAR recorded 91 cross-origin requests and 2.62MB cross-origin transfer, including consent and logging services, though the tracker matcher found no known tracker domains. F17 medium: The unauthenticated landing page has a broad partner and third-party surface. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found autocomplete="" on the email field and no visible passkey path on the tested entry screen. F12 medium: The login entry does not advertise passkey support and omits email autocomplete. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no CSP, HSTS, X-Content-Type-Options, frame protection, Referrer-Policy, or Permissions-Policy. F10 high: The main document lacks baseline defensive headers. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured 52% rendered-word coverage; the raw response lacked the final title and H1, although server HTML was not an empty shell and bot-specific robots rules allow indexing. F14 medium: Important rendered semantics are incomplete in raw HTML. |
be-resilientresilient-runtime-behaviour | pass | medium | FAQ controls use native SUMMARY elements and the tested 404 state provides recovery. |
be-resilientoffline-and-installable | not-applicable | high | Video streaming and account commerce are intrinsically online; a manifest exists, but offline playback is not a reasonable public landing-page requirement. |
be-resilientnetwork-and-http-failure-states | pass | medium | The tested nonexistent route produced a clear message and home recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The localized /en-gb page declares html lang=en and rendered left-to-right English correctly. |
be-internationalisedlocale-aware-data | not-applicable | high | The tested public paths rendered no dates, currencies requiring locale transformation, or numeric data entry. |
be-internationalisedtime-zone-correctness | not-applicable | high | The tested public paths expose no event scheduling or time-zone-sensitive values. |
be-trustworthyno-dark-patterns | pass | medium | The mobile consent surface gives Accept All and Reject All equal visual prominence and provides customization. |
be-trustworthyhumane-error-handling | pass | medium | The login field has a visible label and the browser flow did not show premature errors before interaction. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe found autocomplete="" on the email field and no visible passkey path on the tested entry screen. F12 medium: The login entry does not advertise passkey support and omits email autocomplete. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The tested plans and login entry pages identify plan pricing and explain the MyDisney account transition. |
be-sustainableoptimised-assets | issues | high | The image primitive found 22/43 images missing dimensions, 17 oversized, and 19 without srcset; the logo source was 3837px wide for a 91px display. F13 medium: Many images are oversized or lack intrinsic/responsive metadata. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 1.47MB of script transfer and a 1,009,508-byte _app chunk; Lighthouse estimated 581KiB unused JavaScript and 66KiB unused CSS. F08 high: A large JavaScript payload dominates startup. |
be-sustainablethird-party-and-media-budget | issues | high | The image primitive found 22/43 images missing dimensions, 17 oversized, and 19 without srcset; the logo source was 3837px wide for a 91px display. The consent copy states 77 partners; HAR recorded 91 cross-origin requests and 2.62MB cross-origin transfer, including consent and logging services, though the tracker matcher found no known tracker domains. F13 medium: Many images are oversized or lack intrinsic/responsive metadata. F17 medium: The unauthenticated landing page has a broad partner and third-party surface. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing surface was found; this emerging capability is contextual and is not required for the public streaming landing page. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the tested public journey; on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | Ten native FAQ open/close cycles produced no Detached* constructor among top retained constructors; separate-load variance limits confidence. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contained 736,670 nodes and 42.6MB self size; the interaction variant reached 867,880 nodes and 50.3MB, though separate-load variance lowers causal confidence. F15 medium: The initial page has a large memory and DOM footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Neither heap summary exposed Detached* constructors among the top retained groups. |
Provenance
Canonical report: results/atomic/reports/0022-www_disneyplus_com.json
Report SHA-256: ef4f19bc8613c9c7d2804edf7fcac29aecdd00f90397af83c207e786315b30ce
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_disneyplus_com/2026-07-17T21-58-08-007Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_disneyplus_com/2026-07-17T21-58-08-007Z
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.