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
5.3s 274/297 pages over
Avg extra weight over 1.6 MB
0.43 MB 200/449 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
57/100
Accessibility
100/100
Best practices
96/100
SEO
100/100
Agentic browsing
99/100
Largest Contentful Paint
7.8s
First Contentful Paint
3.0s
Speed Index
3.5s
Total Blocking Time
0.3s
Cumulative Layout Shift
0.065
Recommendations
Issues Lighthouse flagged across the 297 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
Network dependency tree
297/297
—
Render-blocking requests
280/297
463.9s
Minimize main-thread work
277/297
139.7s
Reduce unused CSS
275/297
16.1 MB · 101.3s
Time to Interactive
275/297
—
Font display
274/297
16.4s
Largest Contentful Paint
274/297
—
JavaScript execution time
271/297
98.3s
First Contentful Paint
270/297
—
Use efficient cache lifetimes
263/297
749.3s
Reduce unused JavaScript
262/297
40.3 MB · 104.0s
Max Potential First Input Delay
224/297
—
Avoid multiple page redirects
190/297
184.3s
Total Blocking Time
178/297
—
Speed Index
155/297
—
Document request latency
143/297
16.8s
Minify CSS
142/297
1.1 MB · 8.5s
Minify JavaScript
141/297
402 KB · 6.1s
Page prevented back/forward cache restoration
141/297
—
Forced reflow
118/297
—
Initial server response time was short
114/297
14.2s
LCP request discovery
110/297
—
Layout shift culprits
89/297
—
Improve image delivery
88/297
14.5s
Legacy JavaScript
86/297
13.5s
LCP breakdown
9/297
—
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Serves images with low resolution
165/297
—
Missing source maps for large first-party JavaScript
140/297
—
Does not use HTTPS
97/297
—
Issues were logged in the `Issues` panel in Chrome Devtools
46/297
—
Uses third-party cookies
43/297
—
Page lacks the HTML doctype, thus triggering quirks-mode
22/297
—
Charset declaration is missing or occurs too late in the HTML
22/297
—
Displays images with incorrect aspect ratio
3/297
—
Browser errors were logged to the console
3/297
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
108/297
—
Page is blocked from indexing
37/297
—
Image elements do not have `[alt]` attributes
22/297
—
Links are not crawlable
2/297
—
Links do not have descriptive text
2/297
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
297/297
—
WebMCP form coverage
297/297
—
WebMCP schemas are valid
297/297
—
llms.txt follows recommendations
297/297
—
Cumulative Layout Shift
89/297
—
Accessibility tree is not well-formed
1/297
—
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: 99/100.
Gaps found on the sampled pages: WebMCP tools registered (297), WebMCP form coverage (297), WebMCP schemas are valid (297), llms.txt follows recommendations (297), Cumulative Layout Shift (89), Accessibility tree is not well-formed (1).
Per-page results
Lighthouse scores and Core Web Vitals per sampled page (2026-W38). 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