History & Trends → Severity, Lighthouse and other measures across 17 weeks.
Performance impact
How far pages fall short of Google's "good" benchmarks: Largest Contentful Paint ≤ 2.5s and page weight ≤ 1.6 MB. Lower is better.
Avg extra LCP over 2.5s
3.1s 194/294 pages over
Avg extra weight over 1.6 MB
3.50 MB 227/327 pages over
Set page_loads_per_week for this target to also estimate total wasted time and data (the way daily-dap uses traffic counts).
Medians across sampled pages
Performance
80/100
Accessibility
99/100
Best practices
100/100
SEO
100/100
Agentic browsing
93/100
Largest Contentful Paint
3.1s
First Contentful Paint
1.6s
Speed Index
4.4s
Total Blocking Time
0.2s
Cumulative Layout Shift
0
Recommendations
Issues Lighthouse flagged across the 294 sampled page(s), beyond the headline scores — grouped by category and ranked by how many pages they affect. Estimated savings (transfer bytes or load time) are Lighthouse's own estimates where available. Accessibility audits are intentionally omitted; they overlap with the axe-core findings on the Accessibility page.
Performance
Performance recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Reduce unused JavaScript
292/294
43.6 MB · 46.9s
JavaScript execution time
286/294
110.7s
Minimize main-thread work
282/294
142.1s
Network dependency tree
282/294
—
Use efficient cache lifetimes
257/294
751.6s
Time to Interactive
241/294
—
Render-blocking requests
229/294
129.2s
Reduce unused CSS
218/294
17.3 MB · 94.0s
Largest Contentful Paint
194/294
—
Minify JavaScript
180/294
7.1 MB · 22.0s
Font display
179/294
11.2s
Speed Index
177/294
—
Avoid multiple page redirects
169/294
145.4s
Improve image delivery
123/294
225.3s
LCP request discovery
98/294
—
Total Blocking Time
96/294
—
First Contentful Paint
94/294
—
Layout shift culprits
89/294
—
Max Potential First Input Delay
84/294
—
Document request latency
44/294
8.6s
Forced reflow
33/294
—
Initial server response time was short
31/294
10.7s
Legacy JavaScript
29/294
3.0s
Page prevented back/forward cache restoration
19/294
—
Minify CSS
5/294
75 KB · 0.3s
LCP breakdown
1/294
—
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Serves images with low resolution
83/294
—
Browser errors were logged to the console
82/294
—
Page lacks the HTML doctype, thus triggering quirks-mode
75/294
—
Issues were logged in the `Issues` panel in Chrome Devtools
64/294
—
Does not use HTTPS
58/294
—
Displays images with incorrect aspect ratio
38/294
—
Charset declaration is missing or occurs too late in the HTML
33/294
—
Missing source maps for large first-party JavaScript
7/294
—
Uses third-party cookies
4/294
—
Uses deprecated APIs
2/294
—
Requests the geolocation permission on page load
1/294
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
107/294
—
Image elements do not have `[alt]` attributes
55/294
—
Links do not have descriptive text
38/294
—
Links are not crawlable
4/294
—
Document does not have a valid `rel=canonical`
1/294
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
294/294
—
WebMCP form coverage
294/294
—
WebMCP schemas are valid
294/294
—
llms.txt follows recommendations
294/294
—
Cumulative Layout Shift
90/294
—
Accessibility tree is not well-formed
76/294
—
What the Agentic score means
The Agentic (AI-readiness) score is new in Google Lighthouse (13.4+). It measures how well a page works for AI agents and assistants — the tools that increasingly mediate how people find and use government services. It checks for things like an llms.txt file (a machine-readable guide for language models), valid structured data, a well-formed accessibility tree that agents can parse, and WebMCP tool/form descriptions. A higher score means an AI assistant is more likely to understand the page and complete tasks on a citizen's behalf correctly.
It is experimental and evolving; treat it as a forward-looking signal, not a compliance requirement. Median across sampled pages: 93/100.
Gaps found on the sampled pages: WebMCP tools registered (294), WebMCP form coverage (294), WebMCP schemas are valid (294), llms.txt follows recommendations (294), Cumulative Layout Shift (90), Accessibility tree is not well-formed (76).
Per-page results
Lighthouse scores and Core Web Vitals per sampled page (2026-W39). Agentic = experimental agentic-browsing score. PWA / offline readiness is tracked in the Standards tab (Lighthouse 12+ removed the PWA category). — click a column heading to sort