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.5s 105/165 pages over
Avg extra weight over 1.6 MB
3.94 MB 142/193 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
82/100
Accessibility
100/100
Best practices
100/100
SEO
100/100
Agentic browsing
94/100
Largest Contentful Paint
3.0s
First Contentful Paint
1.6s
Speed Index
4.3s
Total Blocking Time
0.2s
Cumulative Layout Shift
0.018
Recommendations
Issues Lighthouse flagged across the 166 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
164/166
24.9 MB · 28.9s
JavaScript execution time
163/166
42.8s
Minimize main-thread work
159/166
37.1s
Network dependency tree
158/166
—
Use efficient cache lifetimes
148/166
418.6s
Time to Interactive
140/166
—
Render-blocking requests
126/166
77.8s
Reduce unused CSS
125/166
9.8 MB · 54.5s
Minify JavaScript
107/166
4.4 MB · 10.9s
Largest Contentful Paint
105/166
—
Font display
99/166
5.5s
Speed Index
99/166
—
Avoid multiple page redirects
90/166
70.8s
Improve image delivery
61/166
120.7s
Total Blocking Time
56/166
—
LCP request discovery
52/166
—
Max Potential First Input Delay
51/166
—
Layout shift culprits
50/166
—
First Contentful Paint
49/166
—
Forced reflow
26/166
—
Document request latency
16/166
1.4s
Legacy JavaScript
13/166
1.9s
Page prevented back/forward cache restoration
8/166
—
Initial server response time was short
4/166
0.3s
Minify CSS
2/166
30 KB
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Browser errors were logged to the console
50/166
—
Serves images with low resolution
44/166
—
Page lacks the HTML doctype, thus triggering quirks-mode
40/166
—
Issues were logged in the `Issues` panel in Chrome Devtools
37/166
—
Does not use HTTPS
32/166
—
Displays images with incorrect aspect ratio
22/166
—
Charset declaration is missing or occurs too late in the HTML
19/166
—
Missing source maps for large first-party JavaScript
3/166
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
53/166
—
Image elements do not have `[alt]` attributes
32/166
—
Links do not have descriptive text
15/166
—
Links are not crawlable
2/166
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
165/166
—
WebMCP form coverage
165/166
—
WebMCP schemas are valid
165/166
—
llms.txt follows recommendations
165/166
—
Cumulative Layout Shift
52/166
—
Accessibility tree is not well-formed
39/166
—
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: 94/100.
Gaps found on the sampled pages: WebMCP tools registered (165), WebMCP form coverage (165), WebMCP schemas are valid (165), llms.txt follows recommendations (165), Cumulative Layout Shift (52), Accessibility tree is not well-formed (39).
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