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
9.4s 153/153 pages over
Avg extra weight over 1.6 MB
2.94 MB 159/199 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
49/100
Accessibility
98/100
Best practices
100/100
SEO
92/100
Agentic browsing
100/100
Largest Contentful Paint
10.2s
First Contentful Paint
3.3s
Speed Index
4.1s
Total Blocking Time
0.7s
Cumulative Layout Shift
0
Recommendations
Issues Lighthouse flagged across the 184 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
153/184
131.4 MB · 584.9s
Render-blocking requests
153/184
177.2s
Reduce unused CSS
153/184
15.0 MB · 78.5s
First Contentful Paint
153/184
—
Largest Contentful Paint
153/184
—
Time to Interactive
153/184
—
Page prevented back/forward cache restoration
153/184
—
Network dependency tree
153/184
—
Minimize main-thread work
149/184
116.2s
Reduce JavaScript execution time
149/184
109.8s
Max Potential First Input Delay
144/184
—
Use efficient cache lifetimes
141/184
43.2s
Total Blocking Time
140/184
—
Speed Index
133/184
—
Font display
95/184
8.8s
Legacy JavaScript
55/184
8.3s
Forced reflow
43/184
—
Layout shift culprits
33/184
—
LCP request discovery
25/184
—
Initial server response time was short
22/184
1.9s
Improve image delivery
8/184
1.2s
LCP breakdown
5/184
—
Duplicated JavaScript
2/184
0.5s
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Browser errors were logged to the console
53/184
—
Missing source maps for large first-party JavaScript
46/184
—
Uses third-party cookies
15/184
—
Issues were logged in the `Issues` panel in Chrome Devtools
15/184
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
109/184
—
Links are not crawlable
106/184
—
Page is blocked from indexing
56/184
—
Links do not have descriptive text
3/184
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
153/184
—
WebMCP form coverage
153/184
—
WebMCP schemas are valid
153/184
—
llms.txt follows recommendations
153/184
—
Accessibility tree is not well-formed
38/184
—
Cumulative Layout Shift
33/184
—
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: 100/100.
Gaps found on the sampled pages: WebMCP tools registered (153), WebMCP form coverage (153), WebMCP schemas are valid (153), llms.txt follows recommendations (153), Accessibility tree is not well-formed (38), Cumulative Layout Shift (33).
Per-page results
Lighthouse scores and Core Web Vitals per sampled page (2026-W40). 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