Manifest position 764 · CrUX rank bucket 1000
https://www.ilmeteo.it
Coverage complete
Coverage-complete audit of six representative paths/templates. Excluded: authenticated account internals, destructive/commercial flows not part of the public core journey, and every city/article URL sharing the audited templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode evaluate probe reports matchMedia=true, html color-scheme “normal”, body background rgb(255,255,255), and no dark-theme CSS; the dark screenshot remains light. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe matched the emulated preference and found zero active animations; scroll behavior remained auto. |
respect-user-preferencesrespects-contrast | issues | high | CSS inspection found no prefers-contrast or forced-colors rules; Lighthouse also identified multiple contrast failures, including the search placeholder at 2.32:1. F02 medium: High-contrast preferences have no authored adaptation. |
implement-natural-interactionsview-transitions | issues | high | Rendered CSS inspection found no view-transition rules or names across the multi-page navigation surface. F03 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was observed on the representative templates, so there is no implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-reveal or other gesture-driven primary interaction was present on the exercised paths. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots and CSS inspection show no sticky/affixed chrome that must react to scroll; primary navigation remains at the document top. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-sensitive anchored popover was present; the navigation is a drawer rather than an anchored overlay. |
provide-guided-navigationdirects-attention | pass | high | Article breadcrumb, labelled navigation, selected forecast tabs and descriptive links preserve orientation across the exercised templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show the modal covering the forecast/article before any interaction; on mobile it consumes virtually the full viewport. F04 high: A full-screen consent wall obscures every representative page on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found 0 <dialog> and 4 role=dialog elements, with no popover or details primitives. F05 medium: Modal UI is implemented as custom role=dialog markup instead of the platform dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop listing screenshot and homepage DOM show extensive navigation, news carousels, social controls and repeated modules before/around the primary forecast. F06 medium: Dense chrome, carousels and secondary modules compete with the forecast. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The layout primitive measured scrollWidth 435 versus visual viewport 360, a 75px horizontal overflow, despite a viewport meta tag. F07 high: The homepage overflows horizontally on a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Live CSS inspection found no @container or container-type declarations; the homepage is the only audited template that overflowed at narrow width. F08 low: Reusable forecast/news components rely on viewport layout rather than container responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The control probe found many visible controls below 24px high (date tabs, links, selects); focused controls reported outline-style none. F09 high: Touch targets and keyboard focus are insufficient on key controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and Rome page headings clearly identify national/local weather, and the labelled “Cerca località” field is prominent. |
support-core-task-successprimary-flow-completion | pass | high | Submitting Roma leads to the Rome forecast detail with current conditions and forecast table; direct and search URLs converge. |
support-core-task-successclear-system-state-and-recovery | issues | high | Searching for zzzzzzzzzzzzzz redirected to /Italia with no “not found” message, correction, retry, or preserved query. F10 medium: An unknown location search silently falls back to the Italy page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 4.3s and Rome forecast LCP 10.3s; the city performance score was 0.69. F11 high: Primary forecast pages miss the good LCP threshold. |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0 on home and 0.009 on city/article; Lighthouse CLS was 0.003 on all three paths. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found no long tasks and 0ms TBT; Lighthouse TBT was 160–230ms, below the poor threshold. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 135 requests and 1,864,269 transferred bytes, including 40 scripts/1,134,034 bytes; Lighthouse interactive was 10.5s and flagged dependency-tree issues. F12 high: The load is dominated by scripts and a large third-party dependency graph. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 135 requests and 1,864,269 transferred bytes, including 40 scripts/1,134,034 bytes; Lighthouse interactive was 10.5s and flagged dependency-tree issues. F12 high: The load is dominated by scripts and a large third-party dependency graph. |
be-inclusivenames-roles-labels | issues | high | Image probes found 3 missing alts on the homepage and 2 on the article, including the article hero; the DOM has no main landmark. F13 medium: Meaningful images lack alternatives and the page landmark model is incomplete. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color-contrast on all three Lighthouse paths; examples include the search placeholder at 2.32:1, white/orange text at 2.54:1 and date labels at 2.32:1. F14 high: Text and essential controls fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The active control probe reported outline “none” and many controls have no visible focus styling; there is also no <main> landmark. F15 high: Keyboard focus is not visibly distinguishable. |
be-inclusivelegible-text | pass | high | Article body is real text, uses a readable single-column mobile layout, and Lighthouse found no text-size/legibility audit failure. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The layout primitive measured scrollWidth 435 versus visual viewport 360, a 75px horizontal overflow, despite a viewport meta tag. The control probe found many visible controls below 24px high (date tabs, links, selects); focused controls reported outline-style none. F07 high: The homepage overflows horizontally on a 360px viewport. F09 high: Touch targets and keyboard focus are insufficient on key controls. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured TypeError: Cannot read properties of undefined at the homepage inline document handler (line 3699), via jquery 3.6.3. F16 medium: The homepage throws an uncaught JavaScript exception. |
follow-best-practicessound-document-and-assets | issues | high | The image probe found 50/52 homepage images missing dimensions; Lighthouse failed aspect-ratio and responsive-image audits. F17 medium: Images are frequently unsized, distorted or served at unsuitable resolution. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed geolocation-on-start at ilmeteo-geolocation.js line 64 and inspector-issues for analytics endpoints. F18 high: The homepage requests geolocation on load and records DevTools inspector issues. |
be-discoverabletitle-and-description | pass | high | Homepage, city and article each expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Viewport meta is present, navigation uses real hrefs, robots allows ordinary public pages and raw HTML carries most content. |
be-discoverablecanonical-and-indexing-signals | pass | high | All representative pages returned 200 with canonical URLs; robots.txt and sitemap.xml are present and the article is not noindex. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage WebSite/VideoObject, city Place/WeatherObservation and article NewsArticle JSON-LD align with visible content; Open Graph metadata is present. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, X-Content-Type-Options, clickjacking protection, Referrer-Policy or Permissions-Policy. F19 high: Core transport and browser security headers are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 22 third-party origins and known DoubleClick, Facebook, GTM, Outbrain and Rubicon trackers; 10 cookies were present, 5 lacked Secure and several lasted 390–400 days. F20 high: The pre-consent privacy and tracking footprint is disproportionate. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse directly traced a load-time geolocation request to ilmeteo-geolocation.js line 64. F21 high: Geolocation is requested outside user context. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no HSTS, frame-ancestors/X-Frame-Options, Referrer-Policy, Permissions-Policy or CSP; cookie evidence also shows SameSite=None throughout. F22 high: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 72–79% raw/rendered content coverage with H1 and descriptions in raw HTML; no JS shell was shipped. |
be-resilientresilient-runtime-behaviour | pass | high | Representative pages rendered usable content and responsive city/article layouts; the drawer/consent surfaces remained within mobile viewport bounds. |
be-resilientoffline-and-installable | issues | high | The PWA probe found a standalone manifest with weather/news shortcuts and screenshots, but navigator.serviceWorker.getRegistrations() returned an empty array. F23 medium: The app manifest advertises standalone installation but no service worker is registered. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown URL returned a real HTTP 404 with an iLMeteo 404 document and links back into the site. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=it and visible copy/reading order is consistently Italian LTR on all paths. |
be-internationalisedlocale-aware-data | pass | high | Forecast labels, dates, decimal values and units are rendered in the Italian locale; city structured dates include +02:00 where published/modified. |
be-internationalisedtime-zone-correctness | issues | high | Rome JSON-LD uses offsets for datePublished/dateModified but WeatherObservation.observationDate is “2026-07-27T01:10:00” with no offset or zone. F24 medium: Machine-readable observation time is ambiguous about time zone. |
be-trustworthyno-dark-patterns | issues | high | The blocking modal headlines “NON raccogliamo dati privati” while stating data may be shared with 275 partners; the green Accept action dominates the muted reject option. F25 critical: Consent copy and visual hierarchy are misleading. |
be-trustworthyhumane-error-handling | issues | high | An impossible city query silently redirects to the generic Italy forecast instead of announcing an error or offering corrected suggestions. F26 medium: Search failure is neither explained nor recoverable in context. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The audited public journey has location search only, not address, payment, sign-in or sign-up fields where autofill tokens apply. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or account-management flow is part of the public weather/news core journey. |
be-sustainableoptimised-assets | issues | high | Homepage image audit found 49 legacy-format images, 22 without srcset, 17 oversized and 29 below-fold images not lazy-loaded. F27 medium: Image delivery is wasteful for the content shown. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 135 requests, 40 scripts and 22 third-party origins during the short load window, while Lighthouse interactive reached 10.5s. F28 high: Background and third-party work is excessive for a forecast page. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party evidence found 22 origins; scripts alone transferred 1.13MB and known ad/tracking vendors were active on load. F29 high: Third-party scripts consume an outsized share of the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was found; public SSR and structured metadata support machine reading, but exposing transactional WebMCP tools is not required for this weather/news surface. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the representative weather/news pages requires on-device generative inference; absence is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 real consent-detail open/close cycles, heap grew only 1.16% (26,550,257 to 26,859,227 bytes) and node count 0.23%, not an unbounded pattern. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 26.6MB for the ad/news/weather page; trace had no long tasks and the footprint remained stable under repeated interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary exposed Detached* constructors among top populations, and repeated interaction added only 1,077 nodes (0.23%). |
Provenance
Canonical report: results/atomic/reports/0764-www_ilmeteo_it.json
Report SHA-256: a88562d313289f1cc83a6fd25439d71042fb12105c093a9b63bce7a6ac0b9967
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilmeteo_it/2026-07-26T23-13-35-859Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilmeteo_it/2026-07-26T23-13-35-859Z
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.