Manifest position 50 · CrUX rank bucket 1000
https://www.ilfattoquotidiano.it
Coverage complete
Coverage-complete multi-template audit. Search, 404 and public reading paths were included; authenticated shop checkout/account flows and exhaustive topic/article permutations were not covered because they are separate-origin or duplicate templates.
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 normal and prefers-color-scheme: dark captures are pixel-identical (both 68,485 bytes), and the live CSS probe found zero color-scheme, prefers-color-scheme, or light-dark() rules. F01 medium: The site ignores the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, two 1,200 ms ifq-on-air animations remained running and the CSS probe found no prefers-reduced-motion rule. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colours capture kept text and all three consent actions clearly visible with system colours. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found zero view-transition declarations across the loaded styles, while recon identified many section and article routes. F06 low: Route changes are abrupt despite a navigation-heavy multi-page experience. |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | CSS probe found no scroll timeline; screenshots show a conventional static news feed. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | Recon and DOM inspection found conventional links and buttons only. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The CSS probe found no container scroll-state or scroll-timeline rules; mobile captures show two persistent header rows consuming vertical space. F07 low: The multi-row sticky chrome does not use scroll-state-aware adaptation. |
provide-guided-navigationanchored-positioning | not-applicable | medium | DOM probe found no popover primitive or visible tooltip flow. |
provide-guided-navigationdirects-attention | pass | high | Section labels, article headlines, topic rails, and the 404 return action clearly indicate destination and next step. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots of the homepage, article, section and blog all show the privacy wall covering the primary content before interaction. F03 high: A full-screen consent interstitial obscures every audited content template on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | While the visual overlay was present, the DOM probe found no dialog, role=dialog, role=alertdialog, or popover element. F04 medium: The consent modal is not exposed as a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | At 360x800, two header rows plus the full-height consent panel leave the lead story only partly visible beneath the overlay. F05 medium: Navigation and consent chrome dominate the initial viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, home, section, and blog had 0 px overflow; the article had only a 1 px rounding difference and remained visually usable. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The rendered homepage contains many reused story cards, but the accessible stylesheet probe found zero @container rules. F08 low: Repeated cards rely on page-level layout rather than component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found 10 target-size failures on the homepage and 2 on the article; the focus probe found MENU, ABBONATI and ACCEDI with outline: none while :focus-visible matched. F09 medium: Several controls are too small or lack a visible focus indicator. |
support-core-task-successclear-purpose-and-primary-action | pass | high | After the consent decision, homepage headlines, section identity, article H1/byline and search results communicate each page purpose and next reading action. |
support-core-task-successprimary-flow-completion | issues | high | Reading is initially interrupted on all four templates, but both Accept and Reject routes are offered and the article content is present after dismissal. F03 high: A full-screen consent interstitial obscures every audited content template on first load. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberate missing URL renders a clear “Pagina non trovata” H1, explanation, homepage recovery link, and suggested articles. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured article LCP 3.1 s and TTI 14.3 s; homepage TTI was 22.1 s. The separate desktop trace measured LCP 1.79 s and TBT 19.5 ms, so the problem is condition-sensitive. F10 medium: The article misses the good LCP threshold and both pages become interactive late. |
be-fast-and-stablevisual-stability | issues | high | The 360x800 layout observer recorded CLS 0.223, including a 0.214 shift at about 1.54 s; the image audit found 45 of 100 images without dimensions. F11 high: The mobile homepage shifts substantially during load. |
be-fast-and-stableefficient-main-thread | pass | high | The trace found one 69.5 ms long task and only 19.5 ms total blocking time; mobile Lighthouse TBT remained 130–152 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR confirmed two VeryHigh-priority parser-inserted stylesheets; Lighthouse estimated 300 ms render-blocking savings, and two EB Garamond fonts transferred 296 KB and 282 KB. The main script was confirmed type=module and is not treated as blocking. F12 medium: Render-blocking CSS and heavy fonts delay content delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 342 KiB unused JavaScript on the homepage and 543 KiB on the article, plus 24 KiB and 16 KiB unused CSS respectively. F13 medium: The page ships substantial unused JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an untitled iframe and six label/name mismatches on the homepage; the article had two images without alt and one unnamed link. F14 high: Accessible names and alternatives are incomplete. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported seven failing contrast nodes on both the homepage and article. Forced-colours remained readable, but normal-theme WCAG contrast still fails. F15 high: Text colour contrast fails on both key templates. |
be-inclusivestructure-and-focus | issues | high | The homepage has an empty H1 followed by H3 topics, the article failed heading-order, and several focused top controls suppress their outline. F16 medium: Heading and keyboard structure is inconsistent. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable serif headlines and body copy with responsive wrapping; no horizontal clipping was observed on home, section, or blog. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse reported 10 target-size failures on the homepage and 2 on the article. Reflow itself passed with 0 px overflow on three templates and only 1 px on the article. F17 medium: Touch target spacing does not hold at mobile size. |
follow-best-practicesno-console-errors | issues | high | Lighthouse’s errors-in-console audit found one browser error on the homepage. F18 medium: The homepage logs a browser error. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 45 of 100 homepage images without width/height; Lighthouse independently found 29 unsized images on home and 11 on the article. F19 medium: Many images omit intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse logged two DevTools Issues on home and one on article, plus about 17 KiB of legacy JavaScript on each. F20 low: Chrome reports inspector issues and avoidable legacy delivery. |
be-discoverabletitle-and-description | pass | high | Home and article expose unique descriptive titles and meta descriptions in both rendered DOM and raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, a width=device-width viewport, and permissive public robots rules were observed; the page achieved 95% no-JS content coverage. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and redirected article expose canonical URLs and indexable robots metadata; both returned successful raw HTTP responses. |
be-discoverablestructured-and-shareable-metadata | pass | high | The homepage exposes WebSite/WebPage/Breadcrumb JSON-LD and Open Graph; the article exposes NewsArticle, Breadcrumb, OG image dimensions and matching visible title/body. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy. Two first-party cookies lacked Secure, including a 400-day SameSite=None cookie. F21 high: The document lacks baseline security headers and sets insecure cookies. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The no-interaction load contacted 18 third-party origins and known Google Tag Manager, Ads and Analytics trackers. HAR recorded 70 of 72 requests and 2.06 MB of 2.15 MB as cross-origin, including three Google scripts totalling about 520 KB. F22 high: A large tracking footprint loads before a consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | medium | DOM probe found only a search form and no permission prompt appeared on load. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, clickjacking defense, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors policy was present on the main response. F23 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Raw HTML contains 95% of homepage and 92% of article rendered content; neither is a JavaScript shell. |
be-resilientresilient-runtime-behaviour | pass | high | Repeated menu toggling left DOM node count unchanged at 5,245, and representative section/article routes remained usable at narrow width. |
be-resilientoffline-and-installable | not-applicable | medium | Probe found no manifest and no controlling service worker. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested 404 provides an explanation, prominent homepage recovery, and relevant alternative articles instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=it-IT, UTF-8 and uses some logical inline properties; Italian reading order renders correctly. |
be-internationalisedlocale-aware-data | pass | high | Visible publication dates are consistently formatted in Italian, while machine-readable article datetime includes an explicit +02:00 offset. |
be-internationalisedtime-zone-correctness | not-applicable | medium | Article probe found editorial publication times only. |
be-trustworthyno-dark-patterns | issues | high | On desktop, Accept is the only filled red button while Reject and Manage are outlined; on mobile Accept is placed first. Reject remains available, so this is a salience nudge rather than forced consent. F24 medium: Consent presentation visually favours acceptance. |
be-trustworthyhumane-error-handling | not-applicable | medium | DOM probe found one text search input and submit control with no required fields. |
be-trustworthytrustworthy-input-assistance | pass | high | The only same-origin input is a simple search box; it does not request address, payment, sign-in or other autofill-sensitive data. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | Recon shows account and shop links target shop.ilfattoquotidiano.it. |
be-sustainableoptimised-assets | issues | high | Lighthouse estimated 255 KiB image savings on home and 164 KiB on article; the image audit found 43 below-fold images not lazy-loaded and 16 legacy-format images. F25 medium: Image delivery leaves avoidable bytes and loading work. |
be-sustainableno-wasteful-work | issues | high | Before any consent interaction, the HAR loaded 23 scripts (894 KB) and 6 XHR/fetch requests; known analytics and advertising endpoints were already active. F26 medium: Analytics and advertising work runs during the blocked first view. |
be-sustainablethird-party-and-media-budget | issues | high | The initial HAR transferred 2.15 MB, including 639 KB fonts and 894 KB scripts; Lighthouse’s fuller run reported 5,284 KiB total payload. F27 medium: Third-party code and fonts are disproportionate for a text-news first view. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | JSON-LD and high no-JS coverage were observed, but no agent action surface exists. |
be-agent-readyon-device-inference | not-applicable | medium | No summarisation or language-model feature is offered or required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 20 menu toggles, DOM count stayed 5,245; heap snapshot self-size rose only 0.52 MB (1.8%) and graph nodes 0.6% across fresh comparable loads. |
be-memory-efficientbounded-footprint | pass | high | The content-heavy homepage used about 29 MB heap self-size with 5,245 DOM elements, proportionate to a long multi-section news page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Twenty menu toggles produced no DOM growth, and the post snapshot increased graph nodes by only 0.6%; no accumulating overlay nodes were observed. |
Provenance
Canonical report: results/atomic/reports/0050-www_ilfattoquotidiano_it.json
Report SHA-256: 29dc25439f23a737d6301d063e7b4c9d714fa04b1bb099db0c3ab2445a7df9cd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilfattoquotidiano_it/2026-07-18T02-04-09-332Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilfattoquotidiano_it/2026-07-18T02-04-09-332Z
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.