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.4s 238/262 pages over
Avg extra weight over 1.6 MB
0.42 MB 188/414 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
55/100
Accessibility
100/100
Best practices
96/100
SEO
100/100
Agentic browsing
99/100
Largest Contentful Paint
7.9s
First Contentful Paint
3.2s
Speed Index
4.1s
Total Blocking Time
0.3s
Cumulative Layout Shift
0
Recommendations
Issues Lighthouse flagged across the 262 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
262/262
—
Render-blocking requests
243/262
418.1s
Minimize main-thread work
243/262
140.2s
Reduce unused CSS
238/262
14.0 MB · 82.5s
Largest Contentful Paint
238/262
—
Time to Interactive
238/262
—
JavaScript execution time
237/262
95.9s
Font display
237/262
14.2s
First Contentful Paint
236/262
—
Reduce unused JavaScript
229/262
35.4 MB · 104.0s
Max Potential First Input Delay
214/262
—
Use efficient cache lifetimes
196/262
620.4s
Total Blocking Time
176/262
—
Avoid multiple page redirects
163/262
159.6s
Speed Index
150/262
—
Document request latency
129/262
17.9s
Minify CSS
119/262
951 KB · 4.8s
Minify JavaScript
118/262
327 KB · 3.0s
Page prevented back/forward cache restoration
118/262
—
Initial server response time was short
105/262
16.6s
LCP request discovery
100/262
—
Forced reflow
99/262
—
Layout shift culprits
84/262
—
Improve image delivery
71/262
16.6s
Legacy JavaScript
53/262
8.2s
LCP breakdown
9/262
—
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Serves images with low resolution
144/262
—
Missing source maps for large first-party JavaScript
119/262
—
Does not use HTTPS
68/262
—
Issues were logged in the `Issues` panel in Chrome Devtools
45/262
—
Uses third-party cookies
43/262
—
Page lacks the HTML doctype, thus triggering quirks-mode
24/262
—
Charset declaration is missing or occurs too late in the HTML
24/262
—
Browser errors were logged to the console
11/262
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
98/262
—
Page is blocked from indexing
30/262
—
Image elements do not have `[alt]` attributes
24/262
—
Links do not have descriptive text
5/262
—
Links are not crawlable
4/262
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
262/262
—
WebMCP form coverage
262/262
—
WebMCP schemas are valid
262/262
—
llms.txt follows recommendations
262/262
—
Cumulative Layout Shift
84/262
—
Accessibility tree is not well-formed
1/262
—
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 (262), WebMCP form coverage (262), WebMCP schemas are valid (262), llms.txt follows recommendations (262), Cumulative Layout Shift (84), Accessibility tree is not well-formed (1).
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