Manifest position 610 · CrUX rank bucket 1000
https://wiadomosci.wp.pl
Coverage complete
Coverage-complete audit of representative public news templates and the initial consent journey.
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 | Light and prefers-color-scheme:dark screenshots are byte-identical and retain a white consent surface even though the underlying site exposes a manual dark-mode control. F004 medium: The first-load privacy UI ignores the requested dark color scheme. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation reported no active animations; no auto-advancing media was observed. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse accessibility did not report color-contrast failures and the consent/content screenshots remain legible. |
implement-natural-interactionsview-transitions | issues | medium | DOM and CSS probes found no View Transition usage, while the representative flow uses conventional full-document links between the listing and article. F005 low: Navigation changes are abrupt rather than transition-guided. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation or JavaScript-driven parallax was observed in CSS/animation probes or long-page captures. |
implement-natural-interactionsphysical-gestures | pass | high | Representative reading, navigation and menu controls use ordinary browser scrolling/clicking; no custom pointer gesture that fights platform behavior was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The 10,834 px homepage screenshot shows a long feed, while DOM/CSS inspection found no scroll-state query or progress affordance. F006 low: Long pages provide no visible scroll progress or scroll-state-aware chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No edge-attached tooltip or contextual popover was present on the representative news, article, latest, or video surfaces. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, one H1, section headings, descriptive links and clear article hierarchy guide attention across listing and article paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show the consent dialog occupying the usable viewport before any article or headline can be read. F001 high: A full-viewport consent wall hides all news on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The structured probe found a DIV role=dialog for navigation and LABEL role=button controls; Lighthouse also flagged the menu label role as inappropriate. F007 medium: Overlays use custom role-based elements rather than native dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | issues | medium | The full-page capture shows repeated WP placeholder blocks, dense recommendation modules, and a large red promotional panel interleaved with headlines. F008 medium: Repeated promotional and placeholder modules dilute the news feed. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360×800 viewport the layout primitive measured scrollWidth 964 px versus clientWidth 360 px, with horizontalOverflowPx 604. The mobile screenshot is visibly clipped. F003 high: The narrow layout overflows by 604 px. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe counted zero container rules across a homepage that reuses news cards in hero, narrow-column, and grid contexts. F009 low: Reusable cards rely on viewport styling only. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found footer links with safe clickable height about 20.8 px, below the 24 px audit floor, and reported two target-size failures. F010 medium: Some touch targets are too small or too tightly spaced. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The title, H1 and headline hierarchy clearly identify a Polish news service and make article links prominent. |
support-core-task-successprimary-flow-completion | issues | high | The homepage-to-article walkthrough cannot reach content until the user accepts tracking or continues into a paid rejection path. F011 high: The primary read-news journey is blocked by a two-step consent/payment detour. |
support-core-task-successclear-system-state-and-recovery | pass | high | The tested 404 has a clear Polish explanation, countdown, pause control, destination link and alternative headlines. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 9,193 ms, FCP 5,554 ms and performance score 0.56; the separate trace measured LCP 3,045 ms and FCP 1,927 ms, still above the 2.5 s good LCP threshold. F012 high: Lab loading performance misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | The layout observer measured CLS 0 with no recorded shifts during the mobile observation window. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 165 ms and TBT 126 ms; Lighthouse reported 212 ms TBT and 40.7 ms forced reflow in the main bundle. F013 medium: Main-thread work includes long tasks and forced reflow. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse says fetchpriority=high is absent on the discoverable eager LCP image; the longest network dependency chain is 2,719 ms. HAR also identified a parser-inserted high-priority script candidate. F014 high: The LCP resource is not priority-hinted and the critical chain is long. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 226,505 bytes of unused JavaScript with up to 1,630 ms savings; HAR recorded 605,982 transferred script bytes. F015 medium: The page ships substantial unused JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found a UL with a direct SPAN child and an inappropriate role=button on a LABEL; the image audit found 5 images without alt text. F016 medium: Some semantics and alternatives are malformed or missing. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility found no contrast-rule failure; screenshots show high-contrast text and controls. |
be-inclusivestructure-and-focus | issues | high | Lighthouse agent accessibility reported the menu LABEL role=button as an inappropriate role, and the list audit found invalid child structure. F017 medium: The accessibility tree is not well formed. |
be-inclusivelegible-text | pass | high | Article typography uses clear hierarchy and comfortable body width; no clipping was observed in the crawler article view. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse inspected a viewport declaration containing maximum-scale=1 and user-scalable=no, which prevents low-vision users from zooming. F018 high: The production viewport disables user zoom. |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices scored 1.0 and did not report console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 40 of 100 images without both dimensions; Lighthouse found invalid UL child markup. F019 medium: Image sizing and list structure are not consistently sound. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three BFCache blockers, including cache-control:no-store on the main resource and a cookie-modifying no-store response. F020 low: Cache policy prevents back/forward cache restoration. |
be-discoverabletitle-and-description | pass | high | Home and article probes found unique descriptive titles and non-empty meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Rendered links have real href values, viewport metadata is present, and robots permits public pages. |
be-discoverablecanonical-and-indexing-signals | issues | high | /sitemap.xml returned 404. Discoverability found the article title and description in raw HTML but no raw H1, with 67% rendered-word coverage. F021 medium: The site has no sitemap at the conventional endpoint and raw article HTML lacks its H1. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes matching Open Graph metadata and NewsArticle JSON-LD with headline, author, dates and image. |
be-private-and-securesecure-transport-and-headers | issues | high | Cookie audit found STabid without Secure and all 10 observed cookies using SameSite=None; several identifiers last 390–400 days. F022 high: Cookie transport and same-site posture is too permissive. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence observed 8 third-party origins and DoubleClick on initial load; HAR attributes 69 requests and 667,124 transferred bytes to third parties. F023 high: Tracking and third-party activity start before a privacy choice. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt fired on load; sign-in is delegated to a distinct SSO endpoint rather than embedded in the reading flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence found no HSTS or Permissions-Policy; Referrer-Policy is the legacy no-referrer-when-downgrade value. CSP, nosniff and frame protection are present. F024 medium: Defensive response headers are incomplete. |
be-resilientprogressive-enhancement | pass | high | Raw HTML is not a JS shell and preserves 72% of home and 67% of article content words plus titles/descriptions. |
be-resilientresilient-runtime-behaviour | pass | high | The menu survived ten open/close cycles and returned to unchecked state; no cut-off overlay or runtime dead end appeared after consent. |
be-resilientoffline-and-installable | issues | high | A valid manifest and active /sw.js registration exist, but Cache Storage returned no cache names after the page loaded. F025 medium: The installable site does not expose an offline cache. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested 404 explains the failure, offers pause/navigation controls and supplies alternative content links. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=pl and the manifest declares pl-PL/ltr; reading order is correct on audited pages. |
be-internationalisedlocale-aware-data | pass | high | Article JSON-LD stores an ISO timestamp while visible publication text is localized in Polish. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public news surfaces display publication timestamps but expose no scheduling or cross-time-zone event flow requiring user-entered time-zone coordination. |
be-trustworthyno-dark-patterns | issues | high | The active consent walkthrough changed “Odrzucam” into two choices: “Nie chcę płacić, jednak akceptuję zgody” or “Nadal odrzucam, chcę zapłacić”. Core content remains gated. F002 critical: Rejecting tracking leads to a pay-or-consent choice rather than a straightforward refusal. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-editable form was present in the representative public news-reading paths. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in credential, or other editable input was present in the audited public reading paths; sign-in leaves for a separate SSO journey. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription completion, cancellation, and account management were not part of the public news-reading scope; the observed coercive consent choice is recorded under no-dark-patterns. |
be-sustainableoptimised-assets | issues | high | Of 100 images, 61 lacked srcset and 56 below-fold images lacked lazy loading; 40 lacked complete dimensions. F026 medium: Responsive image delivery is incomplete. |
be-sustainableno-wasteful-work | issues | high | HAR loaded ad/video SDKs and 69 third-party requests on initial load; Lighthouse found 226 KB unused JavaScript and forced reflow. F027 medium: Nonessential work competes with the initial news experience. |
be-sustainablethird-party-and-media-budget | issues | high | HAR measured 667,124 third-party bytes out of 1,320,746 total; IMA SDK alone transferred 154,248 bytes before a video was requested. F028 high: Third-party code consumes roughly half of transferred bytes. |
be-agent-readystructured-agent-capabilities | issues | medium | Robots explicitly blocks GPTBot and CCBot while allowing OAI-SearchBot and Perplexity; Lighthouse agentic browsing score is 0.5 and reports a malformed accessibility tree. No structured WebMCP capability was observed. F029 low: The public news corpus is only partly agent-ready. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing summarisation or language-model task was offered, so on-device inference is not applicable to the current interface. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten menu open/close cycles heap self-size rose only 301,751 bytes (0.80%) and heap node count 3,346 (0.48%) versus a same-content baseline, consistent with bounded warm-up rather than unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | After consent the page had 1,851 live DOM elements and about 38 MB heap self-size, proportionate to a media-rich news homepage. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated-interaction heap summaries showed closure count changing only 33,487 to 33,528 and no Detached* constructor among the dominant populations. |
Provenance
Canonical report: results/atomic/reports/0610-wiadomosci_wp_pl.json
Report SHA-256: dcc830e2fd057f051ca1b4f938a20f5eb69eebf362dd046a3aee8d7033f1e917
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/wiadomosci_wp_pl/2026-07-21T22-19-47-403Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/wiadomosci_wp_pl/2026-07-21T22-19-47-403Z
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.