Manifest position 284 · CrUX rank bucket 1000

https://www.goal.com

Coverage complete

Coverage-complete audit of five representative Goal.com UK archetypes. Not covered: authenticated account settings, checkout, betting transactions, forums posting, external shop and video playback because they are separate or destructive/regulated flows.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Dark and light emulation screenshots are byte-identical (660,976 bytes each); the DOM probe reports theme="dark" and computed colorScheme="normal". F03 medium: The site forces its stored dark theme instead of following the system light/dark preference on first visit.
respect-user-preferences `respects-reduced-motion`	issues	high	Under prefers-reduced-motion: reduce, getAnimations() still reported running pulse1 and pulse2 animations with 3,000 ms duration and unbounded iterations. F04 medium: Indefinite pulse animations continue when reduced motion is requested.
respect-user-preferences `respects-contrast`	pass	high	Forced-colors/prefers-contrast screenshot retained readable controls and text; Lighthouse reported no color-contrast failures.
implement-natural-interactions `view-transitions`	pass	high	CSS probe found view-transition rules on rendered routes; navigation links use real hrefs and preserve cross-document semantics.
implement-natural-interactions `scroll-driven-animations`	pass	high	CSS probe found animation-timeline/scroll-timeline declarations, supporting off-main-thread scroll-linked effects.
implement-natural-interactions `physical-gestures`	pass	high	CSS probe found scroll-snap declarations and no physical-only layout dependency; mobile navigation remained usable.
provide-guided-navigation `scroll-state-aware-chrome`	pass	medium	Rendered CSS contains scroll-position/timeline support and mobile screenshots show position-aware compact navigation.
provide-guided-navigation `anchored-positioning`	pass	medium	Rendered CSS contains anchor-name/position-anchor support; inspected navigation overlays did not visibly drift or clip.
provide-guided-navigation `directs-attention`	pass	medium	View-transition, scroll-snap and visible section headings provide direct attention cues across article and score surfaces.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Desktop article screenshot shows an 870×676 consent surface over dimmed editorial content; the mobile scores screenshot is entirely occupied by the same choice. F01 critical: A full-page consent/pay wall obscures the primary article before any interaction.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	A blocking modal is visible in screenshots, but the rendered DOM probe found zero dialog elements, zero popovers and zero details elements. F16 medium: The modal consent surface is not represented by native dialog/popover semantics in the inspected document.
maximize-content-reduce-noise `reduced-chrome`	issues	high	Desktop article screenshot shows an 870×676 consent surface over dimmed editorial content; the mobile scores screenshot is entirely occupied by the same choice. F01 critical: A full-page consent/pay wall obscures the primary article before any interaction.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	At 360×800, layout reported scrollWidth=clientWidth=360 with zero horizontal overflow and viewport metadata present.
adapt-to-the-form-factor `component-level-responsiveness`	pass	high	Rendered CSS probe found @container rules and the home/scores/team templates reflowed into distinct mobile compositions.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The home probe counted 51 visible controls below 24 px in one dimension; the live-scores probe measured date/action buttons around 35.7×32 px and several icon buttons at 16×16 px. F14 high: Many interactive targets are below comfortable touch size.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Home, article, scores and team screenshots/probes expose descriptive titles/headings and clear content destinations.
support-core-task-success `primary-flow-completion`	issues	high	Desktop article screenshot shows an 870×676 consent surface over dimmed editorial content; the mobile scores screenshot is entirely occupied by the same choice. F01 critical: A full-page consent/pay wall obscures the primary article before any interaction.
support-core-task-success `clear-system-state-and-recovery`	pass	high	The invalid-route journey rendered a clear Sorry message and a visible Homepage recovery action rather than a blank shell.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP at 14.0 s (performance 47); the independent trace measured LCP at 4.87 s and FCP at 2.45 s. F05 high: The homepage misses the good LCP range by a wide margin.
be-fast-and-stable `visual-stability`	pass	high	Layout observer measured CLS 0.0098 and Lighthouse CLS 0.008, both in the good range.
be-fast-and-stable `efficient-main-thread`	issues	high	Lighthouse reported 410 ms TBT; the trace found three long tasks, 206 ms TBT and a longest task of 208.87 ms. F06 medium: Startup JavaScript blocks the main thread.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR captured 145 requests and 2.62 MB transferred, including 62 scripts (1.10 MB), 52 images (1.15 MB), and at least nine parser-inserted VeryHigh-priority stylesheets confirmed by DOM CSS links. F07 high: The initial load has a large fragmented critical path.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	HAR captured 145 requests and 2.62 MB transferred, including 62 scripts (1.10 MB), 52 images (1.15 MB), and at least nine parser-inserted VeryHigh-priority stylesheets confirmed by DOM CSS links. F07 high: The initial load has a large fragmented critical path.
be-inclusive `names-roles-labels`	issues	high	Lighthouse failed button-name (4 elements) and link-name (2 elements); the scores probe found multiple 16–35 px buttons with empty text and null/empty aria-label. F12 high: Icon-only controls and links lack accessible names.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse color-contrast audit passed and forced-colors screenshot retained legible text and controls.
be-inclusive `structure-and-focus`	issues	high	DOM quality probe found zero H1 elements on the homepage, while article, team, and scores templates each expose one descriptive H1. F13 medium: The homepage has no H1 and begins its content hierarchy at H2/H3.
be-inclusive `legible-text`	pass	high	Article screenshot shows readable line lengths and hierarchy; narrow screenshots reflow without clipping or horizontal overflow.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The homepage viewport is width=device-width, initial-scale=1, maximum-scale=1; target probes found 51 sub-24 px controls despite mobile layout itself having no overflow. F15 high: The viewport policy limits user zoom and combines with undersized targets.
follow-best-practices `no-console-errors`	issues	high	Lighthouse errors-in-console audit failed with 28 recorded items. F11 medium: The homepage emits numerous browser console errors.
follow-best-practices `sound-document-and-assets`	issues	high	The images primitive found 63 of 100 images without width/height, 28 oversized images, 99 legacy-format URLs, and 2 images without responsive sources. F08 medium: Image delivery is frequently oversized or lacks intrinsic dimensions.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse BFCache audit passed; no geolocation/notification prompt appeared on load and the page used a valid modern document.
be-discoverable `title-and-description`	pass	high	Home, article, scores and team probes all found descriptive titles and meta descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	Real href links, viewport metadata, indexable robots policy and robots.txt Allow were directly observed; Lighthouse SEO was 92.
be-discoverable `canonical-and-indexing-signals`	pass	high	Canonical, 70 hreflang links, HTTP 200 and non-noindex robots signals were present; robots.txt points to localized sitemaps.
be-discoverable `structured-and-shareable-metadata`	pass	high	Article probe found JSON-LD plus Open Graph; team probe found four JSON-LD blocks; metadata matched visible content.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers primitive found no Strict-Transport-Security header; CSP script-src allows both unsafe-inline and unsafe-eval. F09 high: Transport is HTTPS, but HSTS is absent and CSP allows unsafe script execution.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Consent copy names 252 technology partners; network evidence found six third-party origins, while the only observed cookie used SameSite=None for 365 days. F10 high: The default experience exposes a large partner/third-party surface before a humane consent choice.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No permission prompt or password form appeared on audited public paths; permissions policy disables geolocation/camera/microphone by default.
be-private-and-secure `defensive-browser-policies`	issues	high	Headers primitive found no Strict-Transport-Security header; CSP script-src allows both unsafe-inline and unsafe-eval. F09 high: Transport is HTTPS, but HSTS is absent and CSP allows unsafe script execution.
be-resilient `progressive-enhancement`	pass	high	Raw-vs-rendered comparison found 77% homepage and 95% article content coverage without JavaScript; neither is a JS shell.
be-resilient `resilient-runtime-behaviour`	pass	high	Mobile navigation, article and scores surfaces rendered without clipped overlays outside the separately identified consent wall.
be-resilient `offline-and-installable`	issues	high	DOM links site.webmanifest, but the platform probe found zero service-worker registrations and could not parse a manifest payload. F17 medium: The site advertises a web manifest but no active service worker or usable manifest payload was observed.
be-resilient `network-and-http-failure-states`	pass	high	The deliberate invalid route displayed an explicit 404 recovery page with a Homepage link.
be-internationalised `lang-dir-and-logical-properties`	pass	medium	html lang=en-GB, dir=ltr, 70 hreflang links and logical CSS properties were observed.
be-internationalised `locale-aware-data`	pass	medium	Localized /en-gb routing and relative time labels were rendered without hand-formatted ambiguous numeric dates on sampled paths.
be-internationalised `time-zone-correctness`	pass	medium	Sampled content uses relative times and locale-specific routes; no ambiguous stored local timestamp was exposed in the audited paths.
be-trustworthy `no-dark-patterns`	issues	high	Load screenshots show two primary choices: accept personalized advertising for free or “Reject & Pay”; no free reject-all control is visible despite 252 technology partners. F02 high: The consent flow presents “Accept All & Continue” as the only free path; rejection is coupled to a £3.49 monthly payment.
be-trustworthy `humane-error-handling`	not-applicable	high	No authored form submission is part of the representative public news, article, score, team or error journeys; the consent UI is a separate vendor flow already judged for deceptive design.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, sign-in or sign-up input flow was present in the representative public journeys, so autocomplete assistance is not applicable to these paths.
be-trustworthy `safe-commercial-and-account-flows`	issues	high	Load screenshots show two primary choices: accept personalized advertising for free or “Reject & Pay”; no free reject-all control is visible despite 252 technology partners. F02 high: The consent flow presents “Accept All & Continue” as the only free path; rejection is coupled to a £3.49 monthly payment.
be-sustainable `optimised-assets`	issues	high	The images primitive found 63 of 100 images without width/height, 28 oversized images, 99 legacy-format URLs, and 2 images without responsive sources. F08 medium: Image delivery is frequently oversized or lacks intrinsic dimensions.
be-sustainable `no-wasteful-work`	issues	high	Lighthouse reported 410 ms TBT; the trace found three long tasks, 206 ms TBT and a longest task of 208.87 ms. F06 medium: Startup JavaScript blocks the main thread.
be-sustainable `third-party-and-media-budget`	issues	high	HAR measured 2.62 MB across 145 requests; consent JS alone was about 95 KB, with six third-party origins and 12 consent-host requests. F18 medium: Third-party and consent code consumes a material portion of an already heavy initial load.
be-agent-ready `structured-agent-capabilities`	issues	high	Discoverability is strong (77% homepage, 95% article) and metadata is rich, but DOM/platform probes expose no WebMCP or agent-tool registration. F19 low: Editorial and live-score capabilities are machine-readable as HTML but are not exposed as structured agent tools.
be-agent-ready `on-device-inference`	not-applicable	high	The audited pages publish server-rendered editorial/scores content and expose no private user-authored summarisation task where on-device inference would materially improve privacy or latency.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten repeated full-feed scroll cycles, heap self-size was 34,284,616 bytes versus baseline 34,317,717 bytes and node count fell from 563,460 to 561,138.
be-memory-efficient `bounded-footprint`	pass	high	Baseline heap self-size was 34.3 MB on the data-rich scores page, proportionate to the rendered feed and stable after exercise.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	No Detached* constructor appeared among the retained top constructors and total nodes decreased after repeated scrolling.

Provenance

Canonical report: results/atomic/reports/0284-www_goal_com.json
Report SHA-256: e1885ff83f076af2f4df8ac804e3f7f3979286eda5e7facece8315f06ee66d69
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_goal_com/2026-07-19T17-09-41-428Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_goal_com/2026-07-19T17-09-41-428Z
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.