Manifest position 502 · CrUX rank bucket 1000
https://www.repubblica.it
Coverage complete
Atomic coverage complete across 58 checks and five representative public templates/flows.
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 | With prefers-color-scheme: dark active, the body remains rgb(252,253,253) with black text and color-scheme remains normal; the dark screenshot is visually unchanged. F01 medium: The site does not adapt to dark color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | No active animations were returned under prefers-reduced-motion: reduce, while the default probe observed three running 200 ms animations. |
respect-user-preferencesrespects-contrast | issues | high | CSS inspection found no prefers-contrast or forced-colors handling, and Lighthouse found 121 contrast failures on the homepage. F02 high: High-contrast support and baseline contrast are insufficient. |
implement-natural-interactionsview-transitions | issues | medium | CSS inspection found no view-transition usage across the representative news templates. F03 low: Page and state changes use abrupt legacy swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked reveal surface was observed on the representative news routes, so there is no scroll-linked implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited news, search, and article templates expose no gesture-driven carousel, swipe, pull-to-refresh, or reorder interaction. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The homepage is about 53,519 CSS px tall, but CSS inspection found no scroll-state query, scroll timeline, or progress treatment. F04 low: Long news pages lack scroll-state guidance. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or viewport-edge popover requiring anchored positioning appeared in the representative public routes. |
provide-guided-navigationdirects-attention | pass | medium | A skip link targets #main-content, labeled menu/search controls expose the navigation path, and the 404 offers a clear homepage recovery link. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a large modal/overlay covering the news page before interaction; on mobile its controls extend below the first viewport. F05 critical: The consent wall obscures the primary content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM reports zero dialog and zero popover elements while the screenshots show a modal consent experience. F06 medium: The blocking overlay is not built with a semantic dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | The article screenshot gives a large bordered ad slot most of the pre-headline viewport, and the consent layer occupies the lower portion. F07 high: Advertising, subscription chrome, and consent UI dominate the first viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive measured scrollWidth 986 versus visual viewport 390, with 596 px horizontal overflow; the article template had no overflow. F08 critical: The homepage forces a 986 px layout into a 390 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules, while the homepage fails at 390 px and the article template adapts correctly. F09 medium: Reused news components do not use container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found many visible links/inputs with outline:none, and Lighthouse reported 10 target-size failures. F10 high: Keyboard focus and touch-target support are inconsistent. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The homepage and section are identifiable, but the load screenshots cover the story grid with consent; the article places a large ad before the headline. F11 high: The primary news task is hidden behind consent and ad chrome. |
support-core-task-successprimary-flow-completion | issues | high | On the homepage the CSS makes .iubenda-cs-close-btn visibility:hidden, leaving Accept or “Reject and subscribe”; the article uses another full-width cookie notice before reading. F12 high: Reading a public route is needlessly detoured through a coercive consent/subscription choice. |
support-core-task-successclear-system-state-and-recovery | pass | high | The deliberate missing URL returns a bilingual “Pagina non trovata / Page not found” state explaining the problem and linking back to the homepage. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 11.8 s and article LCP 15.5 s; the trace independently measured homepage LCP 5.4 s. CLS remained low. F13 critical: Loading is far outside the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Homepage observed CLS was 0 in the layout run and 0.003 in Lighthouse; article CLS was 0.0069, all within the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 3.0 s of main-thread work and 280 ms TBT; the trace found one 65 ms long task. F14 medium: Main-thread work remains heavy during load. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse found 890 ms root-document latency, an estimated 1,340 ms render-blocking saving, and 710 KiB cache-lifetime saving; HAR confirmed two very-high-priority parser stylesheets. F15 high: Critical delivery has slow document and render-blocking paths. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 729 KiB unused JavaScript and 13 KiB unused CSS; HAR transferred 1.51 MB across 30 scripts. F16 high: The page ships substantial unused JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name and image-alt; the DOM probe counted 57 anchors with no text, aria-label, or image alt, and the image primitive found two missing alts. F17 high: Some links and images lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse identified 121 homepage contrast failures and 3 article failures. F18 high: Text contrast fails at scale. |
be-inclusivestructure-and-focus | issues | high | The Politica section has no h1 and begins with repeated h2 headings; many focused visible links show outline:none in the probe. F19 high: Heading structure and focus visibility are inconsistent. |
be-inclusivelegible-text | pass | medium | Article headline/body typography is large and readable in desktop/mobile captures, with no article horizontal overflow or clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 390 px the homepage overflows by 596 px and Lighthouse reports 10 undersized/closely spaced targets; viewport scaling itself is allowed. F20 high: Homepage reflow and target sizing fail on mobile. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console reported zero items and no uncaught exception prevented the audited templates from loading. |
follow-best-practicessound-document-and-assets | issues | high | Doctype, UTF-8 and viewport are valid, but the image primitive found two missing dimensions on both homepage and article, 79/100 homepage images without srcset, and 94 legacy-format images. F21 medium: Document basics are sound, but image delivery has sizing defects. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse found one Inspector Issues entry, although it found no deprecated APIs or console errors. F22 low: DevTools reports an inspector issue. |
be-discoverabletitle-and-description | pass | high | Homepage, section, article, search, and 404 paths have descriptive titles; public content templates expose meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage has 581 real href anchors but 57 have no discernible text; Lighthouse fails link-name. Viewport and robots allow normal search crawling. F23 medium: Links are crawlable but some lack descriptive text and one section lacks an h1. |
be-discoverablecanonical-and-indexing-signals | pass | high | Public routes return 200, expose canonical URLs, are not noindex, and robots.txt points to a working sitemap index. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes NewsArticle, AudioObject and BreadcrumbList JSON-LD plus matching Open Graph title, description, image and URL; homepage has JSON-LD and OG metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | CSP allows unsafe-inline and unsafe-eval; HSTS and nosniff are missing. Six of seven observed cookies lack Secure and all use SameSite=None. F24 critical: Transport is HTTPS, but CSP and cookie protections are weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 22 third-party origins and four known tracker domains; HAR transferred 2.16 MB, including 1.51 MB of scripts. F25 high: The pre-consent third-party footprint is extensive. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No browser permission prompt appeared on any audited public route. Authentication was not required for the representative public-news/search tasks, so its credential method did not apply to these paths. |
be-private-and-securedefensive-browser-policies | issues | high | Headers show no HSTS, X-Content-Type-Options, clickjacking policy, or Permissions-Policy; Referrer-Policy is unsafe-url and CSP has no frame-ancestors while allowing unsafe code. F26 critical: Key browser-enforced defensive policies are absent or unsafe. |
be-resilientprogressive-enhancement | pass | high | Raw HTML retains 94% of homepage and 76% of article content words, with title, h1, and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Homepage/section show a centered blocking wall, mobile places actions below the first viewport, and the article uses a different bottom notice; no semantic dialog is present. F27 medium: Runtime overlay behavior is inconsistent across templates and viewports. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered, frequently changing news service rather than an installable app in the audited scope; no offline reading/installability intent was declared. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing route produces a useful bilingual 404 with explanation and homepage recovery instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang is it, but CSS inspection found no logical properties and did find physical left/padding-left rules. F28 medium: Language is declared, but layout CSS is not writing-mode resilient. |
be-internationalisedlocale-aware-data | pass | medium | Rendered dates and subscription prices use Italian language and formatting consistently on article, search, and 404 paths. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative news, section, search, and article templates show publication dates but no event scheduling, recurring intervals, or user-entered time-zone-sensitive data. |
be-trustworthyno-dark-patterns | issues | high | The primary choices are “ACCETTA” and “RIFIUTA E ABBONATI”; the homepage CSS hides the continue-without-accepting control, making the privacy-preserving path materially less available. F29 critical: Consent refusal is tied to purchasing a subscription. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited search uses an optional GET query and exposes no required or destructive form submission for which validation/error timing applies. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The representative public routes only expose search/filter inputs; address, payment, sign-in, and sign-up fields were outside the audited public-news scope. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The consent wall presents subscription as the rejection action, while pricing appears elsewhere; this makes a privacy choice look like a purchase commitment. F30 high: The commercial choice is entangled with consent refusal. |
be-sustainableoptimised-assets | issues | high | The homepage image audit found 94 legacy-format images, 79 without srcset, and eight oversized images; Lighthouse estimated 76 KiB immediate image savings. F31 high: Image assets are not efficiently responsive. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 83 requests and 2.16 MB transferred; 30 scripts account for 1.51 MB, while Lighthouse estimates 729 KiB unused JavaScript. F32 high: Large script and third-party loads create avoidable work. |
be-sustainablethird-party-and-media-budget | issues | high | Twenty-two third-party origins load on the homepage, including four known trackers, before the user can access content. F33 high: Third-party code is disproportionate to the initial news task. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing transaction or tool surface is declared, and robots.txt explicitly opts major AI crawlers out; absence of WebMCP capabilities is therefore treated as an intentional contextual choice, not a defect. |
be-agent-readyon-device-inference | not-applicable | high | The audited publisher experience exposes no summarization/composition feature requiring inference; adding built-in AI is an optional product decision rather than a quality requirement. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After equivalent consent dismissal and settling, 10 menu open/close cycles increased snapshot self size from 75.1 MB to 81.9 MB (+9%) and snapshot nodes from 1.35M to 1.52M (+13%). F34 medium: Repeated menu use retains substantial additional heap. |
be-memory-efficientbounded-footprint | issues | high | The settled baseline heap summary contains 1,348,055 snapshot nodes and 75.1 MB self size before repeated interaction. F35 high: The homepage has an unusually large memory footprint for a news document. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | issues | medium | The settled repeated-interaction snapshot retained 176,820 more snapshot nodes and 6.8 MB more self size; the in-page sample also grew from 3,441 to 3,478 DOM elements. Constructor-level detached-node attribution was unavailable, so confidence is medium. F36 medium: Interaction-associated heap/node growth needs leak investigation. |
Provenance
Canonical report: results/atomic/reports/0502-www_repubblica_it.json
Report SHA-256: ad084c131beadc48a0e6d3597454b8d9501142f8e8617ba1493ec3c28301c632
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_repubblica_it/2026-07-21T05-42-10-953Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_repubblica_it/2026-07-21T05-42-10-953Z
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.