Manifest position 433 · CrUX rank bucket 1000

https://sportowefakty.wp.pl

Coverage complete

Coverage-complete audit of six representative paths/templates. Excluded: authenticated SSO/account management, quiz completion and bookmaker flows because they are distinct external/gated journeys and not required to judge the public newsroom templates.

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	The dark-condition screenshot remains a white consent surface, and the platform probe found no prefers-color-scheme, light-dark(), or color-scheme implementation. F01 medium: The site does not adapt to the user’s dark theme preference.
respect-user-preferences `respects-reduced-motion`	issues	high	The reduced-motion probe found two running 1500 ms animations while the platform probe found no prefers-reduced-motion rule. F02 medium: Motion continues when reduced motion is requested.
respect-user-preferences `respects-contrast`	issues	high	The platform probe found no forced-colors or prefers-contrast CSS, while Lighthouse also found ordinary color-contrast failures. F03 medium: High-contrast preferences are not explicitly supported.
implement-natural-interactions `view-transitions`	issues	high	The platform probe found no view-transition CSS across the loaded styles. F04 low: Route and state changes have no declarative transition treatment.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation or scrollytelling surface was present on the representative templates, so there is no applicable implementation to judge.
implement-natural-interactions `physical-gestures`	not-applicable	high	No swipe, drag, pull-to-refresh, carousel gesture or other custom gesture flow was present in the audited paths.
provide-guided-navigation `scroll-state-aware-chrome`	pass	high	Screenshots show persistent category and score navigation that preserves location context across long listings.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip or edge-positioned transient menu was exposed on the audited anonymous paths.
provide-guided-navigation `directs-attention`	pass	high	Representative section/article captures use clear section color bars, headlines and linked cards to direct attention.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Homepage, article, results and live screenshots all show a full-screen blurred backdrop and consent panel before content can be used. F05 high: A consent wall obscures the entire site on every audited first-visit path.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	DOM evidence found one [role=dialog] but no <dialog>; the panel uses custom fixed-position chrome. F06 medium: The consent modal is custom role-based UI rather than the native dialog primitive.
maximize-content-reduce-noise `reduced-chrome`	issues	high	The full-page homepage screenshot shows repeated chrome and ad placeholders across an 11,895 px page, with content cards occupying a minority of several sections. F07 medium: Dense navigation, score strips, category bars, advertising slots and side rails compete with editorial content.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	The viewport meta is width=970; a requested 360 px viewport produced a 989 px layout viewport scaled to 0.364, and section/article probes reported 972 px scroll width against 780 CSS px inner width. F08 high: The mobile experience is a scaled desktop canvas rather than a responsive layout.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The platform probe found no @container rules; narrow captures retain desktop-density cards and navigation. F09 medium: Reusable components do not use component-level responsiveness.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The focused Zaloguj link computed to outline none/0 px; 64 of 475 visible controls measured below 24 px in at least one dimension. F10 high: Keyboard focus is invisible and many controls are undersized.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Homepage, section, article, scores and live templates have descriptive titles and recognizable primary content/actions.
support-core-task-success `primary-flow-completion`	issues	high	Results and live-page screenshots expose only “Ustawienia zaawansowane” and a prominent accept action; the requested content cannot be used until this detour is completed. F11 high: First-visit core journeys are blocked behind a consent decision with rejection hidden in advanced settings.
support-core-task-success `clear-system-state-and-recovery`	issues	high	The URL returned HTTP 404, but the rendered DOM had no h1 and reused the homepage title/content behind the consent wall, with no “not found” explanation or recovery action. F12 medium: The 404 response does not present an explicit error or recovery state.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP 6.7 s, FCP 3.9 s, TTI 7.5 s and performance 0.64; the trace’s unthrottled LCP was 1.64 s, showing network/CPU conditions expose the problem. F13 high: The lab mobile load misses the LCP performance target.
be-fast-and-stable `visual-stability`	pass	high	Layout observer measured CLS 0.014 and Lighthouse measured 0, both in the good range.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace found 3 long tasks, 99.6 ms TBT and 102 ms longest task; Lighthouse TBT was about 200 ms, near the good threshold.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR found a parser-blocking stylesheet and synchronous head script plus a 529 KB uncached PNG; Lighthouse estimated 410 ms render-blocking, 440 KiB cache and 120 ms font-display savings. F14 medium: Resource delivery includes render blockers and weak cache/font behaviour.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 292 KiB unused JavaScript and 15 KiB legacy JavaScript; HAR recorded 36 scripts and 605 KB transferred script bytes. F15 medium: The page ships substantial unused and legacy JavaScript.
be-inclusive `names-roles-labels`	pass	high	Lighthouse passed button-name, link-name, image-alt, label, main-landmark and html-lang audits on the homepage.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse’s color-contrast audit failed on the homepage. F16 high: Some foreground/background combinations fail WCAG contrast.
be-inclusive `structure-and-focus`	issues	high	Lighthouse failed heading-order; the homepage h1 is empty and the explicit focus probe found no visible outline on the focused login link. F17 high: Heading sequence and focus visibility are not reliable.
be-inclusive `legible-text`	pass	high	Article and section captures show readable body copy and unclipped editorial text at the delivered layout scale.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The page declares width=970 rather than device width; Lighthouse failed meta-viewport and the probe counted 64 controls below 24 px. F18 high: The fixed viewport prevents genuine reflow and leaves controls too small.
follow-best-practices `no-console-errors`	pass	high	Lighthouse errors-in-console audit scored 1.
follow-best-practices `sound-document-and-assets`	issues	high	Lighthouse failed image aspect-ratio and responsive-resolution audits and partially failed explicit dimensions; image inspection found 60/100 without srcset. F19 medium: Image asset presentation has quality and sizing defects.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse passed console, source-map, BFCache, notification/geolocation-on-load and paste-prevention checks.
be-discoverable `title-and-description`	pass	high	Homepage, section and article probes each found descriptive title and meta description.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Lighthouse failed crawlable-anchors and meta-viewport; the live DOM otherwise had many real href links and robots allowed normal indexing. F20 medium: Some links are not crawlable and the viewport is not mobile friendly.
be-discoverable `canonical-and-indexing-signals`	pass	high	200 responses, canonical links, permissive general robots rules and a sitemap index were directly inspected.
be-discoverable `structured-and-shareable-metadata`	pass	high	Homepage has JSON-LD/Open Graph and the article exposes NewsArticle JSON-LD plus 11 Open Graph fields matching its visible title.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS is used, but header inspection found no CSP, HSTS, nosniff, clickjacking, Referrer-Policy or Permissions-Policy. Cookie inspection found 13 insecure cookies and widespread SameSite=None, including 390–400 day identifiers. F21 high: Baseline transport defenses and cookie attributes are missing.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	The consent copy names 1,017 IAB plus 846 other partners; network evidence saw 12 third-party origins, 69/91 requests and 957 KB third-party bytes, including Salesmanago and Survicate. F22 high: The first-visit data/third-party footprint is disproportionate.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	No browser permission request or authentication flow was part of the anonymous news, score and live-content scope; the separate SSO flow was not exercised.
be-private-and-secure `defensive-browser-policies`	issues	high	HTTPS is used, but header inspection found no CSP, HSTS, nosniff, clickjacking, Referrer-Policy or Permissions-Policy. Cookie inspection found 13 insecure cookies and widespread SameSite=None, including 390–400 day identifiers. F21 high: Baseline transport defenses and cookie attributes are missing.
be-resilient `progressive-enhancement`	pass	high	Discoverability showed 81% homepage and 65% article content coverage in raw HTML, with title/h1/description present and no JS shell.
be-resilient `resilient-runtime-behaviour`	pass	high	Loaded homepage, results and live templates retained usable navigation/content DOM without blank shells; no cut-off transient menu was exposed.
be-resilient `offline-and-installable`	issues	high	A manifest and active service-worker registration exist, but the controlled-page probe was false and Cache Storage had no keys after load. F23 medium: Installability exists, but no offline cache/fallback was evident.
be-resilient `network-and-http-failure-states`	issues	high	A real 404 response renders homepage-like content with no not-found heading or explicit recovery controls. F24 high: HTTP failure handling is misleading.
be-internationalised `lang-dir-and-logical-properties`	pass	high	The document declares lang=pl-PL and the CSS probe found logical properties in use.
be-internationalised `locale-aware-data`	pass	high	Rendered article and match dates use Polish day-month-year conventions, consistent with lang=pl-PL.
be-internationalised `time-zone-correctness`	not-applicable	high	The audited pages expose Polish publication/match display times but no cross-zone scheduling or user-entered time workflow requiring a DST/time-zone transformation.
be-trustworthy `no-dark-patterns`	issues	high	The consent wall gives a large green “Akceptuję” action while rejection is hidden behind “Ustawienia zaawansowane”; copy proposes sharing identifiers with 1,863 partner entries. F25 high: Consent choices are visually and procedurally asymmetric.
be-trustworthy `humane-error-handling`	not-applicable	high	No submit form with validation was present in the representative anonymous paths.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, sign-up or sign-in input flow was present in the representative anonymous paths.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No checkout, subscription or account-management flow was part of the public newsroom scope.
be-sustainable `optimised-assets`	issues	high	HAR’s largest asset is a 529 KB PNG; Lighthouse estimates 109 KiB image savings and image inspection found 60/100 images without srcset. F26 medium: Image delivery is not consistently resolution-efficient.
be-sustainable `no-wasteful-work`	pass	high	Trace and layout evidence found bounded main-thread work after load (3 long tasks and about 100 ms trace TBT), with no autoplay media on the homepage.
be-sustainable `third-party-and-media-budget`	issues	high	Third parties account for 69/91 requests and 957 KB of 1.61 MB transferred; multiple marketing/survey origins load before a consent decision. F27 high: Third-party script cost is high relative to the core reading task.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	No declared agent-facing capability exists; this emerging principle is optional, while crawler-readable article content was assessed under discoverability.
be-agent-ready `on-device-inference`	not-applicable	high	No user task on the audited public news paths requires on-device inference; this emerging feature is optional.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	Baseline heap was 508,411 nodes/31,023,652 bytes; after ten full-page scroll cycles it was 508,859 nodes/31,146,966 bytes, a small ~0.4% size change rather than unbounded growth.
be-memory-efficient `bounded-footprint`	issues	high	The baseline heap summary contained 508,411 nodes and 31.0 MB self size for a news listing. Repeated-scroll capture stayed similar, but the one-state footprint is disproportionate. F28 medium: The homepage has a large initial memory/DOM footprint.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Before/after heap totals remained effectively stable across repeated scrolling, with no population-scale growth signal in the summary.

Provenance

Canonical report: results/atomic/reports/0433-sportowefakty_wp_pl.json
Report SHA-256: 3108bb318e3ee992c4e8922f7c8ca8d2c49ebc7d27de3290c7b4076b75d04f1f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sportowefakty_wp_pl/2026-07-20T19-21-06-534Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sportowefakty_wp_pl/2026-07-20T19-21-06-534Z
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.