Manifest position 501 · CrUX rank bucket 1000
https://www.onet.pl
Coverage complete
Coverage-complete audit of homepage, news listing and representative article.
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 dark-scheme screenshot remains the same white and grey light palette as the default capture; the CSS probe found no prefers-color-scheme rule and computed color-scheme was normal. F01 medium: The site does not adapt to the system color scheme. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion emulation matched and document.getAnimations() returned no active animations. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found no preference treatment, while Lighthouse found a 3.91:1 text contrast failure in the install banner under the default palette. F02 medium: Contrast preferences are not explicitly supported. |
implement-natural-interactionsview-transitions | issues | high | The rendered CSS probe found no view-transition rules or API styling across the link-heavy news experience. F03 low: Route changes do not use declarative View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | The CSS probe found no scroll timelines and the layout capture found no long tasks, so no main-thread scroll-linked animation was active. |
implement-natural-interactionsphysical-gestures | pass | high | The representative reading surfaces used native scrolling and links; no custom pointer-driven gesture surface was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The CSS probe found no scroll timeline or scroll-state treatment on a long 12,574 px homepage. F04 low: Navigation chrome does not expose scroll-aware state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned popover was part of the representative editorial paths. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show clear card headlines, section labels and conventional link navigation across homepage, listing and article. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, mobile, listing and article screenshots all show a large consent modal covering the content before any interaction. F05 high: A consent interstitial obscures the entire primary experience on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found a DIV with role=dialog rather than dialog/popover; the visible surface only offers advanced settings and proceed. F06 medium: The consent modal is an ad hoc dialog and has no light-dismiss path. |
maximize-content-reduce-noisereduced-chrome | issues | high | The consent panel occupies most of the desktop viewport, while the crawler screenshot is largely header and a large ad slot rather than editorial content. F07 high: Consent and advertising chrome dominate the initial viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The viewport meta is width=1280; a 360x800 capture is a tiny scaled desktop layout and layout metrics report innerWidth 1280 at the mobile condition. F08 high: The homepage forces a 1280 CSS-pixel viewport on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no @container rules, while the homepage reuses cards across 620, 300 and 290 px columns and then scales the whole desktop canvas on mobile. F09 medium: Repeated card components are not container-responsive. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe measured 11.6x18 and 12 px-high buttons, 36 px icon links, and no outline on the search input and login button. F10 high: Several controls are too small or have no visible custom focus. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The DOM probe found an empty H1 and the first-view screenshot hides the editorial hierarchy behind consent text. F11 medium: The homepage purpose is weakened by an empty primary heading and blocking consent wall. |
support-core-task-successprimary-flow-completion | issues | high | The representative article screenshot shows its headline and body disabled beneath the full consent dialog. F12 high: Reading the selected article requires clearing the same blocking consent wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | The modal presents advanced settings and a high-emphasis proceed action, but no equivalent reject-all, close or back-to-content action. F13 medium: The initial consent state lacks a clear immediate decline or return path. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.2 s and Speed Index 6.4 s; the independent trace measured LCP 2.37 s, showing a condition-sensitive performance risk. F14 medium: Lab LCP is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer measured CLS 0.041, within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 200 ms TBT and 23.4 s Time to Interactive, despite the separate trace recording no long tasks in its capture window. F15 medium: Third-party startup work delays interactivity. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 262 requests and 3.81 MB transferred, including 28 stylesheets and parser-inserted high-priority Google Fonts and livebar CSS candidates. F16 high: The homepage has a large and fragmented critical load. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 603 KiB unused JavaScript and 40 KiB unused CSS; major waste comes from ads, Piano, tag managers and app bundles. F17 high: The page ships substantial unused JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two unnamed navigation links, an untitled livebar iframe and a visible-label/accessibility-name mismatch; the search input probe also found no label. F18 high: Important controls and embedded content lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured the install banner at 3.91:1 against a required 4.5:1. F19 medium: Some small text fails minimum contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage H1 is empty, the probe found only header and footer landmarks in its DOM slice, and search/login controls showed no visible outline when focused. F20 high: Heading, landmark and focus structure is incomplete. |
be-inclusivelegible-text | issues | high | The 360 px screenshot shows the fixed 1280 px page and consent copy reduced to tiny text that is impractical to read. F21 high: Mobile text is rendered as a scaled desktop page. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport meta is width=1280 and the focus probe found multiple targets below 44x44 CSS pixels. F22 high: The mobile experience does not reflow and has undersized targets. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a 401 response from /api/okonto/me in the browser console. F23 low: The page logs a network error during normal load. |
follow-best-practicessound-document-and-assets | pass | high | DOM evidence confirms HTML doctype, UTF-8 charset and explicit dimensions passed Lighthouse on rendered images. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found an unload listener and reported BFCache restoration blocked in the main frame. F24 medium: Deprecated unload handling blocks the back-forward cache. |
be-discoverabletitle-and-description | pass | high | Homepage, listing and article all exposed descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage declares width=1280 rather than device-width, and the 360 px capture is a scaled desktop layout. All sampled links did have href values. F25 high: The fixed viewport signal undermines mobile friendliness. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt returned successfully but /sitemap.xml returned HTTP 404; canonical URLs were present on sampled pages. F26 medium: No sitemap was available at the conventional root URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The probe found one JSON-LD block but no og:* meta properties on the homepage; the article did expose JSON-LD. F27 medium: The homepage lacks Open Graph share metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers probe found no CSP or HSTS; the cookies probe found 18 cookies flagged insecure by the primitive, including multiple 400-day values. F28 high: Transport is HTTPS but key security headers and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe observed 44 third-party origins and five known tracker domains; HAR attributed 256 of 262 requests and 3.69 MB to non-main origins. F29 high: The initial page load has an excessive tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | low | The homepage exposes a login button, but the rendered DOM and scripts inspected in the audit showed no user-facing passkey or WebAuthn path. No permission prompt appeared on load. F30 medium: The visible login entry provides no passkey or WebAuthn affordance. |
be-private-and-securedefensive-browser-policies | issues | high | The headers probe found no frame protection, Referrer-Policy or Permissions-Policy in addition to missing CSP and HSTS. F31 high: Browser-enforced defensive policies are largely absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 10% raw-to-rendered content coverage on the homepage, while the article template reached 79%. F32 high: Most homepage editorial content is unavailable to non-JavaScript clients. |
be-resilientresilient-runtime-behaviour | pass | high | The sampled pages rendered stable content and the consent overlay remained within the viewport on desktop. |
be-resilientoffline-and-installable | not-applicable | high | Onet is a continuously updated public news service rather than an offline-first application; installability is not required for the core reading task. |
be-resilientnetwork-and-http-failure-states | pass | high | The observed anonymous account 401 did not blank the page; editorial content and navigation still rendered beneath the consent state. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All sampled documents declared lang=pl, matching their Polish content. |
be-internationalisedlocale-aware-data | pass | high | The article rendered its date in Polish day-month-year form consistent with the declared pl locale. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled public news pages did not provide scheduling or cross-zone event coordination controls. |
be-trustworthyno-dark-patterns | issues | high | The bright yellow proceed button is paired with advanced settings, but no equally immediate reject-all action is visible. F33 high: Consent choices are visually and structurally imbalanced. |
be-trustworthyhumane-error-handling | not-applicable | high | No validation form was present in the sampled homepage, listing or article core paths. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found one input with no label, aria-label or aria-labelledby; its visible focus outline was none. F34 medium: The search field lacks basic programmatic input assistance. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The first-view header shows only SUBSKRYBUJ, with no adjacent price, renewal or cancellation context. F35 medium: The subscription CTA does not disclose price or commitment before navigation. |
be-sustainableoptimised-assets | issues | high | The image probe found 61 of 100 images without srcset and four below-fold images not lazy-loaded; HAR also loaded a 203 KB decorative MP4. F36 high: Image and media delivery is not sufficiently responsive. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 118 scripts and 40 fetch/XHR requests; Lighthouse identified 603 KiB unused JavaScript and 200 ms blocking time. F37 high: Large optional tracking and marketing workloads start on initial load. |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributed 3.69 MB of 3.81 MB to non-main origins and the tracker probe observed 44 external origins. F38 high: Third-party resources dominate the transfer budget. |
be-agent-readystructured-agent-capabilities | issues | high | Homepage non-JS content coverage was 10%; the probe found no WebMCP registration while the article template retained 79% content coverage. F39 medium: The homepage is weakly agent-readable and exposes no structured browser tools. |
be-agent-readyon-device-inference | not-applicable | high | The sampled news reading and discovery tasks do not require client-side language-model or summarisation inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten repeated feed scroll cycles the post snapshot was 48.12 MB versus 48.37 MB baseline, with only a 0.17% node-count increase. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap contained 892,248 nodes and 48.37 MB self size for a news landing page; the DOM itself had about 1,504 elements. F40 medium: The homepage has a disproportionately large in-memory footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated-scroll comparison showed bounded aggregate growth: 1,525 additional nodes and a lower total self size; no runaway pattern was evident at this confidence. |
Provenance
Canonical report: results/atomic/reports/0501-www_onet_pl.json
Report SHA-256: 095220924d506b9ec1c45ef34fb61b38f3aedd9fdae304745f204aa4fda10e93
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_onet_pl/2026-07-21T05-32-55-729Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_onet_pl/2026-07-21T05-32-55-729Z
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.