Manifest position 730 · CrUX rank bucket 1000
https://www.livescore.cz
Coverage complete
Atomic coverage complete: all 58 registered checks have a conclusive outcome.
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 colorScheme was normal and body remained rgb(255,255,255); CSS contained no prefers-color-scheme rule. F01 medium: Honours prefers-color-scheme: observed implementation diverges from the expected outcome. |
respect-user-preferencesrespects-reduced-motion | pass | high | The page exposed no active animations, so there was no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found consent text contrast as low as 1.06:1, 1.82:1, and 2.8:1. F02 medium: Honours prefers-contrast / forced-colors: observed implementation diverges from the expected outcome. |
implement-natural-interactionsview-transitions | issues | high | The MPA route changes are abrupt and CSS contains no view-transition declarations. F03 medium: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps.: observed implementation diverges from the expected outcome. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, reveal, or scrollytelling interaction exists on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The site exposes ordinary links only, with no gesture-driven control to evaluate. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The 6,123px results page has no sticky context, progress indicator, or scroll-state-aware chrome. F04 medium: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling.: observed implementation diverges from the expected outcome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, menu, or popover overlay requiring anchored positioning was present. |
provide-guided-navigationdirects-attention | issues | medium | Score-only links open a new detail page abruptly and the Top links provide no transition or highlight cue. F05 medium: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved.: observed implementation diverges from the expected outcome. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A full-screen consent wall obscures all scores on every audited route before interaction. F06 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first.: observed implementation diverges from the expected outcome. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The modal is a div with role=dialog rather than native dialog, while the page has zero dialog/popover/details elements. F07 medium: Overlays and rich controls use the right primitive: observed implementation diverges from the expected outcome. |
maximize-content-reduce-noisereduced-chrome | pass | high | Behind the consent layer, pages use compact navigation and devote most space to scores, match details, tables, or dates. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Home and match templates report 10px horizontal overflow at a 360px visual viewport; standings and calendar do not overflow. F08 medium: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints.: observed implementation diverges from the expected outcome. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS contains no @container rules; dense score rows retain tiny desktop-like text and targets on mobile. F09 medium: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints.: observed implementation diverges from the expected outcome. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Many links are only 12px high and score links are about 10x12px; the focused consent dialog had only a transparent outline. F10 medium: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike.: observed implementation diverges from the expected outcome. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The brand, sport/date/status filters, live scores, and REFRESH NOW action make the site purpose and next actions clear. |
support-core-task-successprimary-flow-completion | pass | high | Score and Standings links resolve to populated detail and table pages with Back and Top recovery links. |
support-core-task-successclear-system-state-and-recovery | issues | high | The error page says the page cannot be displayed and to try later, has no title, and offers only a generic home link with no retry or cause. F11 medium: 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.: observed implementation diverges from the expected outcome. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.5s and TTI 8.1s; the trace measured LCP 3.06s. CLS and TBT were good. F12 high: Core Web Vitals are in the good range: observed implementation diverges from the expected outcome. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS ranged from 0.052 to 0.088 across templates, below the 0.1 good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded zero long tasks and 0ms total blocking time; Lighthouse TBT was 30ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | A parser-inserted stylesheet is render-blocking with an estimated 810ms saving; total transfer was 872KB and LCP was slow. Scripts identified by HAR were defer/async. F13 medium: Critical resources are delivered efficiently: observed implementation diverges from the expected outcome. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 382KiB unused JS, including 141KB ad code and 118KB first-party vendor code; 14KiB consent CSS was unused. F14 medium: 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.: observed implementation diverges from the expected outcome. |
be-inclusivenames-roles-labels | issues | high | An icon-only toggle button has no accessible name, five iframes have no title, and six images lack alt text. F15 high: 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.: observed implementation diverges from the expected outcome. |
be-inclusivesufficient-contrast | issues | high | Consent text and controls fail WCAG contrast, with measured ratios from 1.06:1 to 2.8:1. F16 high: Text and essential UI meet WCAG colour-contrast minimums against their background.: observed implementation diverges from the expected outcome. |
be-inclusivestructure-and-focus | issues | high | The homepage skips from H2 to repeated H4 headings, and focus on the consent dialog has a transparent outline. F17 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves.: observed implementation diverges from the expected outcome. |
be-inclusivelegible-text | issues | high | Core navigation and score links render around 12px high in a very dense layout, harming scanning and reading comfort. F18 medium: Text is legible and inclusively rendered: observed implementation diverges from the expected outcome. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Many actionable links are far below 44x44 CSS pixels and home/match pages overflow horizontally by 10px. F19 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling.: observed implementation diverges from the expected outcome. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse best-practices scored 1.0 and reported no console-error or uncaught-exception failure. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and charset are valid, but all seven images omit width/height attributes; six decorative GIFs also lack alt. F20 medium: 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.): observed implementation diverges from the expected outcome. |
follow-best-practicesbrowser-platform-hygiene | issues | high | The 135KB first-party vendor bundle has no source map, reducing inspector/debugging hygiene. F21 medium: The page uses the platform cleanly: observed implementation diverges from the expected outcome. |
be-discoverabletitle-and-description | issues | high | The calendar page duplicates the generic homepage title and description rather than describing the calendar route. F22 medium: The page has a unique, descriptive <title> and a meta description.: observed implementation diverges from the expected outcome. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport metadata is present, but many match links use only scores or a dash as link text, and public detail/table routes declare noindex,nofollow. F23 medium: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive.: observed implementation diverges from the expected outcome. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical links and 200 responses exist, but robots.txt and sitemap.xml returned 403 to the audit fetch and useful match/standings pages are noindex,nofollow. F24 medium: Public pages expose the indexing signals search engines need: observed implementation diverges from the expected outcome. |
be-discoverablestructured-and-shareable-metadata | issues | high | No JSON-LD describes sports events or results; og:image incorrectly points to the site root rather than an image. F25 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.: observed implementation diverges from the expected outcome. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used and no secrets were exposed, but CSP/HSTS/nosniff are missing and all five cookies lack Secure and use SameSite=None. F26 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells.: observed implementation diverges from the expected outcome. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacted 12 third-party origins and four known trackers; 31/41 requests and 692KB/872KB were third-party. The consent text names 210 partners. F27 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.: observed implementation diverges from the expected outcome. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication flow or browser permission request exists in the representative public score experience. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, and CSP frame-ancestors are all absent. F28 high: Browser-enforced defenses are configured where appropriate: observed implementation diverges from the expected outcome. |
be-resilientprogressive-enhancement | pass | high | Homepage raw HTML retains 93% of rendered content words and is not a JS shell; detail raw HTML retains core matchup content although live enrichment lowers coverage to 45%. |
be-resilientresilient-runtime-behaviour | pass | medium | The consent overlay remains within mobile and desktop viewports and first-party scripts are deferred rather than parser-blocking. |
be-resilientoffline-and-installable | issues | high | The site declares display:standalone with install icons and start_url, but has zero service-worker registrations and therefore no offline fallback. F29 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: observed implementation diverges from the expected outcome. |
be-resilientnetwork-and-http-failure-states | issues | high | The failure page has an empty title, generic try-later text, and no retry/status detail; it does provide only a homepage link. F30 medium: HTTP errors, network failures, timeouts and stale data states are handled intentionally: observed implementation diverges from the expected outcome. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The document is lang=en while the mandatory consent UI is Czech; dir is absent and inspected CSS contains no logical inline/block properties. F31 medium: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes.: observed implementation diverges from the expected outcome. |
be-internationalisedlocale-aware-data | issues | medium | The English match page hard-codes a 22.07.2026 numeric date while geolocated consent is Czech, with no locale switch or locale-labelled formatting. F32 medium: Dates, numbers, currencies, durations and calendar systems are formatted locale-aware (Intl), location-agnostic where stored, and recurring intervals and event differentials are modelled correctly.: observed implementation diverges from the expected outcome. |
be-internationalisedtime-zone-correctness | issues | high | Global fixtures show bare times such as 19:00 and 19:30 without a time-zone label or user-zone explanation. F33 medium: Time handling survives time zones and DST: observed implementation diverges from the expected outcome. |
be-trustworthyno-dark-patterns | issues | medium | A blocking consent wall appears before content and presents extensive processing by 210 partners. Reject is available and equally styled, reducing but not removing the nagging-wall concern. F34 medium: No deceptive design: observed implementation diverges from the expected outcome. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-input form exists in the audited score, detail, standings, calendar, or error paths. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up, or other text-entry form exists in scope. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | No account or checkout flow exists; consent provides equally prominent accept/reject buttons and management options, and betting links identify their destination. |
be-sustainableoptimised-assets | issues | medium | All seven images use legacy PNG/GIF formats and omit intrinsic dimensions; six below-fold GIFs are not lazy-loaded, though byte cost is small. F35 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.: observed implementation diverges from the expected outcome. |
be-sustainableno-wasteful-work | issues | high | The page transfers an estimated 382KiB of unused JavaScript, much of it advertising and analytics work unrelated to viewing scores. F36 medium: Background work and fetching are not wasteful: observed implementation diverges from the expected outcome. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 31 requests and 692KB, including 257KB ads, 154KB tag manager, 148KB consent tooling, and 84KB fonts. F37 medium: 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.: observed implementation diverges from the expected outcome. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent, transactional tool surface, WebMCP registration, or agentic form exists; this emerging capability is out of scope. |
be-agent-readyon-device-inference | not-applicable | high | The live-score experience has no summarisation or language-model task for which on-device inference is necessary. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | This MPA exposes navigation and one-shot consent rather than a representative repeatable same-document interaction; fabricating a loop would not model real use. |
be-memory-efficientbounded-footprint | issues | medium | A simple text-centric results page retained 311,295 heap nodes and 18.65MB self size, with 6,258 DOM elements, 5 iframes, and 1,406 interactive/tabbable nodes. F38 medium: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated.: observed implementation diverges from the expected outcome. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | The heap summary exposed no Detached* constructor among reported constructors; no repeatable same-document interaction existed to provoke listener/timer accumulation. |
Provenance
Canonical report: results/atomic/reports/0730-www_livescore_cz.json
Report SHA-256: d078639bc3c086492119046b7bbc35996c956ab7c5a0232dc6fa551505327e3b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_livescore_cz/2026-07-22T17-17-16-815Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_livescore_cz/2026-07-22T17-17-16-815Z
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.