Manifest position 799 · CrUX rank bucket 1000
https://www.corriere.it
Coverage complete
Complete atomic audit of 58/58 checks across four representative templates plus a 404 recovery state.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-emulated screenshot is pixel-equivalent in appearance to the light capture, and computed styles report color-scheme: normal. F03 medium: The site does not adapt to the user’s dark color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found no prefers-reduced-motion CSS rules and five running 2s animations plus running 1.5s animations. F04 medium: Non-essential animations continue under reduced-motion. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color-contrast audit passed and high-contrast capture retained visible consent text and controls. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found only the browser default view-transition name and no authored transition elements across an MPA with many route changes. F05 low: Navigation changes do not use authored View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | Platform probe found no scroll-timeline rules, but recon found no authored parallax/scrollytelling motion requiring them and no scroll-jank finding was observed. |
implement-natural-interactionsphysical-gestures | pass | high | Primary navigation and reading use native links and scrolling; no custom pointer-driven gesture surface that fights platform behavior was observed. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | DOM/screenshots show persistent section/header navigation and the content hierarchy remains oriented across sampled homepage, section and article templates. |
provide-guided-navigationanchored-positioning | pass | high | No tooltip/popover requiring manual edge positioning was present in the audited primary paths; existing menus remained attached in sampled states. |
provide-guided-navigationdirects-attention | pass | high | Section labels, article headings, breadcrumbs/navigation and descriptive links provide clear location and reading progression across sampled templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360px screenshots show the entire first viewport obscured by a mandatory consent/subscription wall before any article can be read. F01 high: A full-viewport consent wall blocks all news on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM evidence shows zero <dialog> and popover elements while Lighthouse identifies a full-screen div with role=dialog and a broken accessible name. F27 medium: The blocking consent experience is an ad-hoc div dialog rather than a native dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | Both desktop and mobile screenshots show no readable news content in the unobscured foreground on first load. F28 medium: Consent chrome occupies 100% of the initial viewport and displaces editorial content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport the layout primitive measured innerWidth 1230, visualViewport 1200, clientWidth 1214, and 30px overflow; screenshots show a tiny scaled consent panel. F06 high: The mobile page is a scaled desktop-width layout rather than a true 360px reflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero CSSContainerRule entries; mobile DOM captures retain 780px main widths and the newsletter form is positioned at x=-352. F07 medium: Components rely on global fixed widths and expose no container-query adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe reported outline-style none and no box-shadow for the first search input and multiple header buttons. F08 high: Keyboard focus is absent on prominent controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage title, section headings and article headline make the news-reading purpose explicit; prominent headline links expose the next action. |
support-core-task-successprimary-flow-completion | pass | high | Homepage links led directly to a section and a current article; article title/content metadata loaded without an account wall in DOM evidence. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid URL produced a clear “page not found” message, home link and current-story recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.4s, TBT 560ms and performance 45; the raw-CDP trace measured LCP 3.21s and TBT 311ms, both indicating meaningful delay under their respective conditions. F09 high: Cold-load performance misses the Core Web Vitals loading bar. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.052 and Lighthouse measured 0.015, both in the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Trace found 8 long tasks and 311ms TBT; Lighthouse found 11.2s main-thread work, including 3.0s script evaluation and 2.5s style/layout. F10 high: Heavy script and layout work blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 254 requests and 6.80MB transferred; Lighthouse reported 6.69MiB, 1.2s render-blocking savings and 2.0MiB cache-lifetime savings. F11 high: The homepage ships a very large and dependency-heavy cold load. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 891KiB unused JS, 68KiB unused CSS, 53KiB legacy JS and duplicate module code; HAR records 96 script requests totaling 2.38MB. F12 high: Large amounts of unused and legacy JavaScript/CSS ship on initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 79 and identified unnamed menu/search buttons, unnamed links, an unnamed consent dialog and untitled iframes. F13 high: Important controls, links, dialogs, and frames lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed for the rendered state. |
be-inclusivestructure-and-focus | pass | high | Landmark/heading probes found one main and logical H2 news sections; focus visibility is separately failed under input modality. |
be-inclusivelegible-text | pass | high | Article and homepage DOM use readable serif/sans text sizing and screenshots show clear typographic hierarchy despite the blocking modal. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found duplicate viewport declarations containing maximum-scale=1/user-scalable=no; independent mobile layout evidence shows a 1214px content viewport under 360px emulation. F14 high: Viewport declarations can prevent user zoom and the layout does not reflow cleanly. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured missing $/jQuery errors, newsletter null.split failures, and an uncaught classList exception. F15 medium: The homepage logs uncaught and application errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 16 images without dimensions, 79 without srcset, 94 legacy-format images and 6 missing alt values; Lighthouse also flagged unsized images. F16 medium: Image markup and delivery are structurally inefficient. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices scored 73 and the inspector-issues audit failed with extensive cookie issues; legacy JavaScript was also detected. F17 medium: Chrome reports browser-platform and cookie inspector issues. |
be-discoverabletitle-and-description | pass | high | Homepage and article probes found descriptive unique titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO scored 100, crawlable anchors passed, robots allows indexing, and a viewport meta is present (zoom quality is separately failed under inclusion). |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage/article expose correct canonicals, HTTP 200, robots index/follow, and discoverability raw fetch succeeded. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article probe found article Open Graph title, description, URL, image, author and UTC publication metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers found no CSP, HSTS, nosniff, or clickjacking header; cookie audit found 42 cookies flagged insecure, many SameSite=None and several long-lived identifiers. F18 critical: Core browser security headers are absent and cookies are broadly insecure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 53 third-party origins and known DoubleClick, Rubicon and GTM trackers; HAR attributes 247/254 requests and 6.53MB to origins classified as third-party. F19 high: The initial page has an exceptionally broad third-party and tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Rendered DOM/platform probes found no navigator.credentials/WebAuthn-facing affordance or passkey messaging around the account entry point. F29 medium: The visible account entry point provides no evidence of phishing-resistant authentication support. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, CSP/frame-ancestors, X-Frame-Options or X-Content-Type-Options was present; Referrer-Policy remains no-referrer-when-downgrade. F20 high: Defensive browser policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 89% rendered-word coverage in raw HTML, no JS shell, and raw title/H1/description present. |
be-resilientresilient-runtime-behaviour | pass | high | Homepage, section, article and newsletter DOMs rendered full content structures; sampled primary links and header surfaces did not blank or lose state. |
be-resilientoffline-and-installable | not-applicable | high | Corriere is a public content MPA rather than an installed app; offline installability is contextual and not required for the audited reading journey. |
be-resilientnetwork-and-http-failure-states | pass | high | The 404 probe returned an explicit recovery state with a home link and useful current stories instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Document declares lang="it-IT" and Italian content reads in the expected LTR direction across sampled templates. |
be-internationalisedlocale-aware-data | pass | high | Rendered article dates use Italian month/day formatting and metadata preserves ISO publication times. |
be-internationalisedtime-zone-correctness | issues | high | The article probe found many <time> elements with Italian display text but empty dateTime values, while social metadata uses UTC timestamps. F26 medium: Rendered article times omit machine-readable, unambiguous datetime values. |
be-trustworthyno-dark-patterns | issues | high | The modal gives a dominant filled “ACCETTA E CONTINUA” action while the alternative is “Rifiuta e abbonati”; the free rejection path is not presented as an equal first-level choice. F02 high: Consent choices are visually asymmetric and rejection is coupled to subscription. |
be-trustworthyhumane-error-handling | pass | high | No required data-entry transaction was exposed before user action in sampled public reading paths; the search/newsletter controls did not show premature blame-style validation. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found visible text inputs with empty autocomplete values and no associated label or aria-label. F21 medium: Search and text inputs do not expose labels or autocomplete intent. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The only first-level refusal wording is “Rifiuta e abbonati”, while acceptance is free and visually dominant. F30 medium: The consent/subscription flow conflates privacy rejection with a commercial commitment. |
be-sustainableoptimised-assets | issues | high | Images account for 3.77MB; 94/100 use legacy formats, 79 lack srcset, and Lighthouse estimates 1.79MiB image-delivery savings. F22 medium: Image assets consume avoidable bandwidth. |
be-sustainableno-wasteful-work | issues | high | HAR records 247 third-party requests while Lighthouse reports 891KiB unused JS and 11.2s main-thread work, much of it from tracking/ad vendors. F23 high: Startup performs substantial non-critical advertising and analytics work. |
be-sustainablethird-party-and-media-budget | issues | high | The page transfers 6.80MB over 254 requests, including 2.38MB scripts and 3.77MB images, with 53 third-party origins. F24 high: Third-party code and media exceed a proportionate news-homepage budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing transaction or tool surface was found; this emerging capability is optional for this news site. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited scope requires on-device inference; absence is an opportunity, not a failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 menu open/close cycles, heap self size rose only 0.61MB (1.0%); Object, Array, Promise and closure populations were flat or lower. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap summary contained 826,807 nodes, 3.17M edges and 58.99MB self size for a document-centric page. F25 medium: The homepage has a disproportionately large in-memory object graph. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after summaries show closures 39,583→39,569, Promise 513→486, Object 33,001→32,843 and no Detached constructor among top populations. |
Provenance
Canonical report: results/atomic/reports/0799-www_corriere_it.json
Report SHA-256: 28b4739408ece691a358a12230d9ba378cae3eeb199cc5b3e6961abd46a39502
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_corriere_it/2026-07-23T02-41-13-336Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_corriere_it/2026-07-23T02-41-13-336Z
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.