Manifest position 815 · CrUX rank bucket 1000
https://www.fifa.com
Coverage complete
Coverage-complete model-driven audit of representative homepage, article, listing, search, error, and account-entry surfaces.
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 | Computed-style probe reports color-scheme: normal, and the dark-emulated capture retains the same hard-coded palette rather than declaring a user-preference-driven scheme. F-01 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 | issues | high | Under prefers-reduced-motion: reduce, the page still runs a 10.5 s hero animation and more than 100 repeating 1 s skeleton animations; the probe found zero reduced-motion CSS rules. F-02 high: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | pass | medium | The forced-colors/prefers-contrast capture preserves visible text, controls, outlines, and consent actions. |
implement-natural-interactionsview-transitions | pass | medium | Computed styles expose view-transition-name: root and the recorded search route change provides direct transition evidence. |
implement-natural-interactionsscroll-driven-animations | pass | medium | DOM/CSS inspection found no scroll-timeline rules and the reviewed pages did not present parallax or scrollytelling that would require a scroll-linked implementation. |
implement-natural-interactionsphysical-gestures | issues | medium | The homepage contains carousel-style content but computed-style inspection found no scroll-snap or overscroll treatment on any element, so gesture behavior is not platform-native. F-03 medium: Gesture-driven interactions and entry/exit motion feel native (declarative overscroll/scroll-snap, physics-based easing, animating to intrinsic sizes, pull/swipe gestures) rather than fighting the platform with custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Computed styles identify the primary header as position: sticky at top: 0, keeping navigation available as content scrolls. |
provide-guided-navigationanchored-positioning | not-applicable | medium | The representative pages exposed full-screen search/consent dialogs but no tooltip or edge-attached popover whose position needed CSS anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Opening the search route moves focus directly to the search input, and the overlay visibly separates the active task from the underlying page. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first viewport is simultaneously obscured by a centered Play Zone promotion and a large consent wall; on mobile the consent wall occupies essentially the entire viewport. F-04 high: 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 consent and privacy overlays are DIV elements with role=dialog; the primary banner lacks aria-modal and the search overlay is custom rather than a native dialog/popover. F-05 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 | Two stacked overlays plus two navigation bars leave the actual football content dimmed and largely unavailable in the initial viewport. F-06 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 the layout primitive reports scrollWidth=clientWidth=360, zero horizontal overflow, and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | CSSOM inspection found 16 container rules, and the tested homepage/article/category surfaces reflowed to the 360 px viewport without overflow. |
adapt-to-the-form-factorinput-modality-aware | pass | medium | Keyboard focus probes show visible outlines on navigation, search, account, consent, and menu controls; the mobile target inventory found only two text controls below 24 px high. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The homepage H1 and dominant action describe Play Zone rather than the FIFA news/content destination, while promotional and consent overlays compete for the first action. F-07 high: The page communicates what it is for and exposes the primary next action without requiring users to hunt through decorative content, generic copy, or competing calls to action. |
support-core-task-successprimary-flow-completion | pass | medium | The representative discovery flow completes from homepage links to a fully rendered article, and the search route opens with focus in the query field. |
support-core-task-successclear-system-state-and-recovery | issues | high | A nonexistent route returns HTTP 200, has an empty title, and shows only a joke message with no home, search, back, or retry link. F-08 high: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 29.3 s and TBT 1,860 ms; the article measured LCP 33.8 s, TBT 1,990 ms, and CLS 1.108. A separate trace measured LCP 5.84 s. F-09 critical: 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 | issues | high | The article Lighthouse run measured CLS 1.108, and the mobile layout observer recorded CLS 1.35 with two approximately 0.61 shifts after load. F-10 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded four long tasks, a 355 ms longest task, and 375 ms total blocking time; Lighthouse measured 1.86-1.99 s TBT. F-11 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR records 6.0 MB over 87 requests, 4.07 MB of script, eight fonts, missing cache headers on a 1.77 MB auth SDK, and multiple synchronous parser-inserted head scripts confirmed by DOM inspection. F-12 high: 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 | The homepage ships 35 scripts totaling 4.07 MB; a 1.77 MB PingOne SDK, 783 KB consent blocker, 325 KB PDF worker, and other integrations load before the user requests those capabilities. F-13 high: 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 | medium | Lighthouse found aria-prohibited-attr and label-content-name-mismatch on the homepage and an unnamed button on the article. F-14 medium: 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 | medium | Lighthouse color-contrast audits fail on both the homepage and article despite forced-colors remaining usable. F-15 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | medium | Lighthouse reports heading-order failure on the homepage; the DOM starts at H1 then repeated H3 cards and injects extensive consent-dialog headings into document structure. F-16 medium: 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 | pass | medium | Article screenshots show readable line length, clear hierarchy, and no clipped body text at desktop and mobile widths. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport content allows scaling, 360 px layouts have no horizontal overflow, focus remains visible, and the target probe found the primary controls appropriately sized. |
follow-best-practicesno-console-errors | issues | medium | Lighthouse reports errors-in-console on both the homepage and article. F-17 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | low | The document has valid HTML doctype/UTF-8, but the image audit found two images without intrinsic dimensions and one asset rendered from a source more than 15x wider than display size. F-18 low: 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 | medium | Lighthouse reports invalid source maps on both templates and a BFCache failure on the homepage. F-19 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 | Rendered homepage and article each have descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse reports non-descriptive link text on both pages and non-crawlable anchors on the article, even though viewport and robots basics are present. F-20 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 | issues | high | The article exposes no canonical link, its og:url incorrectly points to /fifaplus, Lighthouse flags hreflang, and nonexistent routes return HTTP 200. F-21 high: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | issues | medium | The news article has no JSON-LD structured data and its Open Graph URL is https://www.fifa.com/fifaplus rather than the visible article URL. F-22 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS and nosniff are present, but CSP allows unsafe-inline and unsafe-eval and the bm_sz cookie is not Secure with SameSite=None. F-23 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 | The consent wall names 1,017 partners; the HAR records 47 third-party requests transferring 4.11 MB and the tracker inventory finds 12 third-party origins. F-24 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 | medium | Notification/geolocation remain prompt rather than being requested on load, but the account/auth surface exposed no passkey or WebAuthn flow and the inspected /auth route produced an empty-title dead end. F-25 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 | medium | HSTS, SAMEORIGIN, no-referrer and nosniff are configured, but Permissions-Policy is missing and the CSP relies on unsafe-inline/unsafe-eval with an exceptionally broad allowlist. F-26 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 | issues | high | Raw HTML for homepage, category and article is an empty #root shell: 0% rendered content coverage, no raw title/H1/description, and blank crawler screenshots without JavaScript. F-27 critical: Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles. |
be-resilientresilient-runtime-behaviour | pass | medium | Search remains focused and usable as a full-width overlay, while inspected sticky navigation stays within the viewport and no clipped edge menus appeared on tested paths. |
be-resilientoffline-and-installable | issues | low | A standalone web app manifest exists, but navigator.serviceWorker.getRegistrations() returned no registrations, so no offline fallback is active. F-28 low: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | issues | high | The tested missing route returns a soft-404 HTTP 200 and offers no actionable recovery control, title, or link. F-29 high: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The page declares lang=en and dir=ltr and exposes ten localized hreflang variants; alternate-language URLs are present for the article. |
be-internationalisedlocale-aware-data | pass | medium | The article renders a localized human-readable publication date and supplies distinct language-specific article URLs for ten locales. |
be-internationalisedtime-zone-correctness | not-applicable | medium | The representative news, listing, search, and error surfaces exposed no event times, scheduling, recurrence, or cross-time-zone interaction to evaluate. |
be-trustworthyno-dark-patterns | pass | medium | The consent wall presents I Accept and Reject All as equally prominent controls and states the consequences of each choice; no preselected purchase or forced-continuity flow was observed. |
be-trustworthyhumane-error-handling | not-applicable | medium | The exercised first-party surfaces contained search but no required-input form or validation flow; article, listing, and search navigation did not solicit error-prone user data. |
be-trustworthytrustworthy-input-assistance | not-applicable | medium | The only first-party text input exercised was site search, which does not require address, payment, sign-in, or sign-up autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | Store, ticketing, rewards and Play Zone are separate linked products; no checkout, subscription, cancellation, or account-management flow was available within the audited fifa.com templates. |
be-sustainableoptimised-assets | issues | medium | The page transfers 437 KB of images and the image audit finds an oversized logo source (1178 px natural width for 74 px display) plus a legacy PNG. F-30 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 | The initial load fetches a PDF worker, a 1.77 MB auth SDK, consent/analytics integrations, and 35 scripts before those capabilities are requested, while trace/Lighthouse show substantial blocking work. F-31 high: 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 47 requests and 4.11 MB, about 69% of transferred bytes; PingOne and OneTrust alone transfer roughly 2.87 MB. F-32 high: 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 | issues | low | This globally prominent content site exposes no WebMCP/agentic form capability, while non-JavaScript agents receive an empty shell with 0% content coverage. F-33 low: Where it makes sense, the site exposes structured, safe capabilities to agents via WebMCP tools, agentic forms, and agentic JavaScript tools rather than leaving agents to scrape and guess. |
be-agent-readyon-device-inference | not-applicable | medium | The audited content, listing, search, and navigation tasks do not require on-device generation or summarisation; no user-facing inference feature was present. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated search-input updates, retained snapshot totals decreased slightly: nodes 1,491,962 to 1,491,952 and self size 80,838,979 to 80,804,689 bytes. |
be-memory-efficientbounded-footprint | issues | medium | A single homepage/search state retains about 80.8 MB across 1.49 million heap nodes, a large footprint for a content/search page before extended use. F-34 medium: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated-interaction snapshot did not grow overall nodes, edges, closures, Objects, or Arrays, and no Detached constructor appeared among size-leading constructors. |
Provenance
Canonical report: results/atomic/reports/0815-www_fifa_com.json
Report SHA-256: 4aa27718c67fd8b2681eab4316992c644702dc75c1563e6ff565ce209fd3043f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fifa_com/2026-07-23T05-03-41-342Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fifa_com/2026-07-23T05-03-41-342Z
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.