Manifest position 292 · CrUX rank bucket 1000

https://www.wp.pl

Coverage complete

Representative audit of homepage, news listing, article, login and unknown-route recovery.

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 emulation produced an identical light consent surface and no preference rule was found. F01 medium: The entry experience does not visibly adapt to dark preference.
respect-user-preferences `respects-reduced-motion`	issues	high	Two infinite 2 s animations remained running while reduce matched. F02 medium: Animations continue under reduced-motion preference.
respect-user-preferences `respects-contrast`	issues	high	Lighthouse directly identified insufficient color contrast. F13 medium: Some foreground/background combinations fail minimum contrast.
implement-natural-interactions `view-transitions`	issues	high	CSS snapshot contains no View Transition declarations across section/article navigation. F03 low: Major cross-document navigation has no View Transition treatment.
implement-natural-interactions `scroll-driven-animations`	pass	medium	CSS snapshot showed no scroll-event animation pattern and no scroll-driven visual effect requiring main-thread linkage; trace had only three bounded long tasks.
implement-natural-interactions `physical-gestures`	pass	medium	CSS probe found native scroll-snap usage and no evidence of custom pointer-driven gesture handling in the rendered entry DOM.
provide-guided-navigation `scroll-state-aware-chrome`	pass	medium	The portal uses conventional labelled section navigation; no shrinking/progress chrome is necessary to understand the covered pages.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, popover or edge-positioned menu was present in the covered initial states.
provide-guided-navigation `directs-attention`	pass	medium	Descriptive link labels and explicit page headings preserve orientation across homepage, section and article templates.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	A full-screen consent gate obscures each public content template. F04 high: A consent interstitial obscures all primary content on every public template.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	One full-viewport fixed overlay was present, with zero dialog/popover/details primitives. F05 medium: The blocking consent layer is not exposed as a native dialog.
maximize-content-reduce-noise `reduced-chrome`	issues	high	The first viewport allocates essentially all visible area to consent chrome instead of requested content. F04 high: A consent interstitial obscures all primary content on every public template.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	At 360 px, layout measured 972 px content width and 612 px overflow. F06 critical: The consent experience is unusable at a 360 px viewport.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	No @container rules were exposed and the consent component fails when reused at mobile width. F07 medium: The component-heavy portal exposes no container-query adaptation.
adapt-to-the-form-factor `input-modality-aware`	pass	medium	Programmatic focus on the first action produced a visible 1 px auto outline; primary login controls are large and labelled.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Titles and H1s clearly identify WP, News and the article; link text exposes primary content destinations.
support-core-task-success `primary-flow-completion`	issues	high	Every public content journey is stopped by the same asymmetric consent decision. F08 high: The primary content journey is gated by a coercive consent decision.
support-core-task-success `clear-system-state-and-recovery`	issues	high	Unknown-route state is hidden by the consent wall and shows no visible recovery. F09 medium: Unknown-route recovery is hidden behind the same consent wall.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse LCP was 5.2 s; trace LCP was 2.94 s with 78.61 ms TBT. F10 high: Cold-load LCP is slow.
be-fast-and-stable `visual-stability`	pass	high	Layout observer and Lighthouse both measured CLS 0.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace recorded three long tasks, 96.12 ms longest and 78.61 ms total blocking time, a bounded main-thread load.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR recorded 95 requests, 1.33 MB transfer, 673 KB scripts and 169 KB fonts. F11 medium: The entry load carries a large early network payload.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	medium	Script delivery dominates the pre-content load at 673 KB across 13 script requests. F11 medium: The entry load carries a large early network payload.
be-inclusive `names-roles-labels`	issues	high	Lighthouse failed button-name, link-name and image-alt; image audit found 33 missing alt values. F12 high: Controls and media lack accessible names.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse color-contrast audit failed. F13 medium: Some foreground/background combinations fail minimum contrast.
be-inclusive `structure-and-focus`	issues	high	Only one landmark was found and heading order jumps H1 to H3; Lighthouse found an ill-formed accessibility tree. F14 medium: The homepage structure is sparse and heading order skips levels.
be-inclusive `legible-text`	pass	medium	Desktop consent and login screenshots show readable sizing, line spacing and unclipped text; the failure is reflow, tracked separately.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Lighthouse failed user scaling and mobile layout has 612 px overflow. F15 high: The rendered experience fails Lighthouse user-scaling/reflow checks.
follow-best-practices `no-console-errors`	pass	medium	Lighthouse best-practices category scored 1.0 and did not report runtime console errors.
follow-best-practices `sound-document-and-assets`	issues	high	Doctype/UTF-8 are valid, but 11 images lack dimensions and 66 are oversized. F16 medium: Many images are unsized, oversized or eagerly loaded below the fold.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported three BFCache failure reasons. F17 low: The page is not eligible for back/forward cache restoration.
be-discoverable `title-and-description`	pass	high	Homepage and article expose descriptive title and meta description in raw and rendered HTML.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Real href links and indexable robots are present, but Lighthouse failed viewport user scaling and mobile reflow is broken. F15 high: The rendered experience fails Lighthouse user-scaling/reflow checks.
be-discoverable `canonical-and-indexing-signals`	pass	high	Homepage and article return 200, expose canonical links, and homepage robots is index,follow; content survives raw fetch.
be-discoverable `structured-and-shareable-metadata`	issues	high	Article has social metadata but no JSON-LD structured data block. F18 medium: Editorial pages omit machine-readable structured data.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS/CSP/nosniff exist, but HSTS is absent and three observed cookies are not Secure. F19 high: Transport and cookie defenses are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Seven third-party origins, DoubleClick and several 390 to 400 day identifiers were observed. F20 high: Tracking requests and long-lived identifiers are present on the pre-choice entry load.
be-private-and-secure `in-context-permissions-and-modern-auth`	issues	high	No permission prompt appeared, but the covered account flow offers password sign-in with no WebAuthn/passkey path. F21 medium: Sign-in offers passwords and social providers but no passkey path.
be-private-and-secure `defensive-browser-policies`	issues	high	HSTS and Permissions-Policy are absent; referrer policy is no-referrer-when-downgrade. F22 medium: Defensive response policy is incomplete.
be-resilient `progressive-enhancement`	issues	high	Article raw HTML retains 67% word coverage but omits its semantic H1. F23 medium: The raw article response omits its semantic H1 and a material share of rendered words.
be-resilient `resilient-runtime-behaviour`	issues	high	The fixed consent runtime layer overflows by 612 px on mobile. F24 medium: The consent runtime state is clipped rather than robust near narrow viewport edges.
be-resilient `offline-and-installable`	not-applicable	high	This public editorial MPA exposes a manifest/service-worker capability, but its core task is current online news rather than an installable offline app.
be-resilient `network-and-http-failure-states`	issues	high	The unknown route does not visibly communicate failure or recovery before consent. F25 medium: The tested unknown route does not expose actionable recovery in the initial state.
be-internationalised `lang-dir-and-logical-properties`	pass	high	HTML lang is pl and rendered CSS includes logical inline/block properties.
be-internationalised `locale-aware-data`	pass	medium	The Polish news listing renders localized relative timestamps such as “6 min” and “19:48” under lang=pl.
be-internationalised `time-zone-correctness`	not-applicable	medium	Covered portal pages display publication recency but do not expose a user flow coordinating scheduled events across time zones.
be-trustworthy `no-dark-patterns`	issues	high	Reject is visually secondary and labelled as a detour to learn more while accept is the direct primary action. F26 medium: Consent choices use asymmetric, nudging labels.
be-trustworthy `humane-error-handling`	issues	high	Login fields are not natively required and invalid submission produced no visible field-level recovery before the challenge. F27 medium: The login form does not expose native requirements and an attempted invalid submission gives no visible field-level recovery before the challenge.
be-trustworthy `trustworthy-input-assistance`	issues	high	Password has current-password but the login/email field has an empty autocomplete token. F28 low: The email/login field omits an autocomplete token.
be-trustworthy `safe-commercial-and-account-flows`	pass	medium	Covered account page clearly exposes password recovery, new-account action, social alternatives and security FAQ; no pricing/continuity commitment is present.
be-sustainable `optimised-assets`	issues	high	Image audit found 66 oversized images and 11 missing responsive srcset. F29 medium: Image delivery wastes bytes through oversized and non-responsive assets.
be-sustainable `no-wasteful-work`	pass	medium	Trace found three bounded long tasks and 78.61 ms total blocking time rather than continuous background main-thread work.
be-sustainable `third-party-and-media-budget`	issues	high	Scripts transfer 673 KB and seven third-party origins load before content access. F30 medium: Third-party and script cost is high before content access.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	No developer intent or public transaction/tool surface indicates WebMCP capability is expected for this editorial portal.
be-agent-ready `on-device-inference`	not-applicable	high	The covered editorial and account journeys do not require on-device summarization or generation to complete their core task.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	medium	Ten repeated scroll cycles increased summarized heap self-size only 29,464 bytes (0.09%) and node count by 690 across isolated equivalent loads.
be-memory-efficient `bounded-footprint`	pass	medium	Baseline summarized heap self-size was 32.0 MB for a media-rich portal entry state, proportionate to the page purpose.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	medium	Neither heap summary listed Detached constructors among top populations, and repeated-scroll growth was negligible.

Provenance

Canonical report: results/atomic/reports/0292-www_wp_pl.json
Report SHA-256: 5bd54c40f056533dc60db86be4414e540aab5dd147fca5883c32951d19695db8
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_wp_pl/2026-07-19T18-34-09-279Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_wp_pl/2026-07-19T18-34-09-279Z
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.