Manifest position 825 · CrUX rank bucket 1000
https://www.livescore.com
Coverage complete
Coverage-complete agentic audit across six representative paths. Sports other than football were not separately audited because they share the score-list template; authentication, checkout, and account flows were not exposed in the public 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 | The platform probe reports computed color-scheme "normal" and the dark-emulation capture does not establish any preference-driven retinting; no color-scheme declaration was found. F001 medium: The interface is hard-coded to a dark palette rather than responding to the system theme. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the active probe found two running animations, each with a 1000 ms duration, and zero reduced-motion CSS rules. F002 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | medium | Screenshot under forced-colors and prefers-contrast shows text, links, and outlined age controls remain visible. |
implement-natural-interactionsview-transitions | pass | medium | Live CSS inspection found five view-transition rules and the browser View Transition API is available. |
implement-natural-interactionsscroll-driven-animations | pass | medium | Live CSS inspection found one animation-timeline/scroll-timeline rule, avoiding a purely scroll-event implementation for the observed scroll-linked effect. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, drag, pull-to-refresh, carousel, or other custom gesture was present on the representative score, match, news, article, or settings surfaces. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | The CSS probe found a declarative scroll-timeline rule and the mobile capture shows persistent, position-aware top navigation. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, transient popover, or edge-positioned menu was exposed in the representative paths; there was no anchored overlay to test. |
provide-guided-navigationdirects-attention | pass | medium | Active navigation pills and five view-transition rules provide visible location and movement cues across score/news states. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show the score experience fully covered by either an age gate or a privacy panel. The interruption probe measured a fixed 780x493 element covering the full 780x493 viewport and body overflow hidden. F003 high: Full-viewport age and privacy gates obscure the primary score content on arrival. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The interruption probe found a full-screen fixed DIV and the modern UI probe found zero dialog elements, popovers, or aria-modal dialogs. F004 medium: The blocking age experience is a custom fixed div rather than a semantic modal. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Behind the required decision layer, the rendered DOM is dominated by score rows and direct sport/date navigation rather than ornamental application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800 the layout reported scrollWidth 360, innerWidth 360, zero horizontal overflow, and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The platform probe found zero CSS container rules despite reusable match, league, navigation, and footer components rendered in several widths. F005 low: Reusable score components appear to depend on viewport rules rather than container-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The interaction probe found favourite buttons rendered at 16x16 px and multiple controls at 40x40 px. The focused first link computed to outline-style none. F006 high: Several controls are too small for touch and the first focused link has no visible outline style. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The H1 identifies live football scores and direct sport, date, league, and match links expose the next action. |
support-core-task-successprimary-flow-completion | pass | medium | The rendered DOM contains current fixtures linking directly to detailed match pages, and the selected detail URL rendered a specific match H1 and metadata. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The intentional unknown route visibly reports 404, explains the failure, and offers Try again plus contact links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 11.4 s, Speed Index at 5.3 s, TBT at 240 ms, and a performance score of 0.67. A separate unthrottled trace measured LCP at 2.434 s, showing a material slow-network sensitivity. F007 high: The throttled load misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | medium | The mobile layout observer measured CLS 0.0098; Lighthouse measured CLS 0.023, both within the good range. |
be-fast-and-stableefficient-main-thread | pass | medium | The trace recorded two long tasks, 73.26 ms longest, and 28.49 ms total blocking time in the unthrottled run; no sustained main-thread blockage was observed. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR records 102 requests and 1,161,947 transferred bytes, including 43 scripts (609,529 bytes), 11 stylesheets, and 355,212 third-party bytes. Lighthouse flags the network dependency tree. F008 high: A script-heavy dependency chain and third-party payload delay useful rendering. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR records 102 requests and 1,161,947 transferred bytes, including 43 scripts (609,529 bytes), 11 stylesheets, and 355,212 third-party bytes. Lighthouse flags the network dependency tree. F008 high: A script-heavy dependency chain and third-party payload delay useful rendering. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails button-name and link-name. The DOM probe identifies two date-navigation anchors containing only SVG with no aria-label or meaningful text. F009 high: Icon links lack accessible names. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse did not report a contrast failure, and the forced-colors screenshot preserves high-contrast readable text and controls. |
be-inclusivestructure-and-focus | issues | high | Lighthouse fails heading-order and accessibility-tree checks; the rendered heading sequence jumps from H1 to H4, and the first focused link has outline-style none. F010 medium: Heading order and keyboard focus presentation are not robust. |
be-inclusivelegible-text | pass | medium | Desktop, mobile, news, and article captures show readable line lengths and unclipped text at the tested widths. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The match probe shows maximum-scale=1.0 and Lighthouse fails meta-viewport because maximum-scale is less than 5. F011 high: The viewport metadata restricts user zoom. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse best-practices score was 0.92 and did not list errors-in-console or uncaught exception audits among failures. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse fails image-aspect-ratio and image-size-responsive; the image probe reports 23 of 32 images as oversized and 21 in legacy PNG format. F012 medium: Some images are served at unsuitable dimensions or aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | Lighthouse did not flag deprecated APIs, paste prevention, permission prompts, vulnerable libraries, or BFCache blockers; permission states remained prompt without an on-load browser prompt. |
be-discoverabletitle-and-description | pass | medium | Homepage, match, news, and article probes all returned specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Real href links, viewport metadata, robots Allow: /, and descriptive content links were observed; Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Canonical URLs, 18 hreflang alternates, robots Allow, sitemap declaration, and HTTP 200 responses were observed without accidental noindex. |
be-discoverablestructured-and-shareable-metadata | pass | medium | The article has NewsArticle JSON-LD and matching Open Graph title, description, image, and URL; homepage/match pages also expose JSON-LD. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive reports no Content-Security-Policy, no X-Content-Type-Options, and no Referrer-Policy. The OptanonConsent cookie is not Secure. HTTPS, HSTS, X-Frame-Options, and Permissions-Policy are present. F013 high: Important browser security headers are missing and the consent cookie lacks Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The privacy UI names 745 partners. Network evidence records 32 third-party requests and 355,212 third-party bytes, including Permutive and GeoEdge scripts; the tracker probe sees nine third-party origins. F014 high: The pre-consent page has a large third-party and partner footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | Geolocation and notifications remained in prompt state with no on-load browser prompt; no authentication flow is present on the representative public paths. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive reports no Content-Security-Policy, no X-Content-Type-Options, and no Referrer-Policy. The OptanonConsent cookie is not Secure. HTTPS, HSTS, X-Frame-Options, and Permissions-Policy are present. F013 high: Important browser security headers are missing and the consent cookie lacks Secure. |
be-resilientprogressive-enhancement | issues | high | The no-JavaScript crawler screenshot replaces the score list with an out-of-date/disabled-browser warning and a legacy-site link. Discoverability coverage is only 48%, although title, H1, and some server-rendered text remain. F015 high: Core live-score content is not usable without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Anchor-position and scroll-timeline CSS rules were present, representative routes rendered without blank shells, and the tested 404 recovered intentionally. |
be-resilientoffline-and-installable | pass | medium | A service-worker registration is active and the manifest supplies name, start_url, fullscreen display, theme/background colors, and install icons. |
be-resilientnetwork-and-http-failure-states | pass | medium | The intentional unknown route provides a clear 404 message, retry/home action, and support contact rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Across readable stylesheets, the CSS probe counted hundreds of physical left/right declarations but only 17 logical-property occurrences. The document does correctly declare lang=en and dir=ltr and exposes 18 localized alternates. F016 medium: The stylesheet relies overwhelmingly on physical left/right properties. |
be-internationalisedlocale-aware-data | pass | medium | The site exposes 18 localized alternates; the article uses a machine-readable ISO datetime and the settings surface explicitly supports timezone preferences. |
be-internationalisedtime-zone-correctness | pass | medium | Article time is stored as unambiguous UTC (2026-07-22T15:22:15.498Z) and rendered as local-facing text; settings copy exposes timezone customization. |
be-trustworthyno-dark-patterns | issues | high | The mobile privacy screenshot gives equal visual prominence to “I Accept” and “Pay to Reject”, while describing 745 partners and blocking the news content until a choice is made. F017 high: Rejecting partner processing is presented as “Pay to Reject”. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-data form is part of the representative public score, news, match, or settings journey; only age and privacy decisions are present. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up text-input flow is present in the audited public surfaces. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The mobile privacy screenshot gives equal visual prominence to “I Accept” and “Pay to Reject”, while describing 745 partners and blocking the news content until a choice is made. F017 high: Rejecting partner processing is presented as “Pay to Reject”. |
be-sustainableoptimised-assets | issues | high | The image probe marks 23 of 32 images oversized, five without responsive srcset, and 21 using legacy formats. A stadium image alone transfers 163,490 bytes. F018 medium: Image delivery is not consistently resolution- or format-efficient. |
be-sustainableno-wasteful-work | issues | high | Third parties account for 355,212 of 1,161,947 transferred bytes; Permutive and GeoEdge scripts are two of the three largest non-image resources and load on the initial route. F019 medium: Third-party scripts consume a disproportionate share of the initial route budget. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 355,212 of 1,161,947 transferred bytes; Permutive and GeoEdge scripts are two of the three largest non-image resources and load on the initial route. F019 medium: Third-party scripts consume a disproportionate share of the initial route budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public score/news experience exposes content rather than an agent-facing transactional capability; emerging WebMCP tooling is not required for the audited scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or language-processing task in the audited core score journey requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After the repeated favourite-toggle exercise, heap self size was 25.36 MB versus 23.67 MB baseline (+7.1%); ordinary Object/Array populations were flat and no unbounded retained-growth pattern was established in this bounded run. |
be-memory-efficientbounded-footprint | pass | medium | The loaded score page heap was 23.67 MB with 482,510 snapshot nodes, proportionate to a live data application in the tested state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Baseline/post summaries did not show Detached* constructors among top retained constructors; Object and Array populations were flat after the exercise. |
Provenance
Canonical report: results/atomic/reports/0825-www_livescore_com.json
Report SHA-256: 4c1352c0d1378a8de7d69379c0c6ee63c51924d9439eddc953b1a5b2c6efda81
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_livescore_com/2026-07-23T06-28-23-758Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_livescore_com/2026-07-23T06-28-23-758Z
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.