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
1.8s 97/174 pages over
Avg extra weight over 1.6 MB
4.22 MB 122/177 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
83/100
Accessibility
100/100
Best practices
96/100
SEO
100/100
Agentic browsing
94/100
Largest Contentful Paint
2.8s
First Contentful Paint
1.5s
Speed Index
4.0s
Total Blocking Time
0.1s
Cumulative Layout Shift
0
Recommendations
Issues Lighthouse flagged across the 174 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
JavaScript execution time
172/174
49.5s
Reduce unused JavaScript
172/174
26.4 MB · 19.9s
Minimizes main-thread work
168/174
43.8s
Network dependency tree
162/174
—
Use efficient cache lifetimes
140/174
297.4s
Time to Interactive
128/174
—
Reduce unused CSS
119/174
9.9 MB · 49.6s
Render-blocking requests
114/174
67.5s
Avoid multiple page redirects
99/174
69.7s
Largest Contentful Paint
97/174
—
Minify JavaScript
96/174
4.4 MB · 10.4s
Speed Index
91/174
—
Font display
70/174
4.0s
Improve image delivery
62/174
84.8s
Total Blocking Time
58/174
—
Max Potential First Input Delay
54/174
—
Layout shift culprits
51/174
—
LCP request discovery
45/174
—
First Contentful Paint
43/174
—
Document request latency
19/174
6.1s
Reduce initial server response time
16/174
8.2s
Forced reflow
16/174
—
Legacy JavaScript
9/174
0.7s
Minify CSS
6/174
106 KB · 0.3s
Page prevented back/forward cache restoration
6/174
—
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Serves images with low resolution
62/174
—
Browser errors were logged to the console
61/174
—
Page lacks the HTML doctype, thus triggering quirks-mode
55/174
—
Issues were logged in the `Issues` panel in Chrome Devtools
55/174
—
Does not use HTTPS
49/174
—
Displays images with incorrect aspect ratio
28/174
—
Charset declaration is missing or occurs too late in the HTML
14/174
—
Missing source maps for large first-party JavaScript
6/174
—
Uses third-party cookies
1/174
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
58/174
—
Image elements do not have `[alt]` attributes
49/174
—
Links do not have descriptive text
12/174
—
Links are not crawlable
1/174
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
174/174
—
WebMCP form coverage
174/174
—
WebMCP schemas are valid
174/174
—
llms.txt follows recommendations
174/174
—
Cumulative Layout Shift
55/174
—
Accessibility tree is not well-formed
44/174
—
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 (174), WebMCP form coverage (174), WebMCP schemas are valid (174), llms.txt follows recommendations (174), Cumulative Layout Shift (55), Accessibility tree is not well-formed (44).
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