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 76/95 pages over
Avg extra weight over 1.6 MB
0.42 MB 71/137 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
88/100
SEO
92/100
Agentic browsing
99/100
Largest Contentful Paint
7.3s
First Contentful Paint
3.8s
Speed Index
4.4s
Total Blocking Time
0.3s
Cumulative Layout Shift
0.062
Recommendations
Issues Lighthouse flagged across the 95 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
95/95
—
Minimize main-thread work
83/95
36.0s
Render-blocking requests
77/95
155.8s
Reduce unused CSS
77/95
4.8 MB · 25.8s
Time to Interactive
77/95
—
Reduce JavaScript execution time
76/95
30.8s
Font display
76/95
4.7s
Largest Contentful Paint
76/95
—
First Contentful Paint
75/95
—
Reduce unused JavaScript
74/95
11.2 MB · 36.8s
Max Potential First Input Delay
72/95
—
Total Blocking Time
60/95
—
Use efficient cache lifetimes
57/95
167.3s
Speed Index
56/95
—
Avoid multiple page redirects
54/95
56.5s
Document request latency
48/95
27.0s
Initial server response time was short
38/95
20.3s
Minify CSS
34/95
276 KB · 1.3s
Page prevented back/forward cache restoration
33/95
—
Minify JavaScript
32/95
102 KB · 0.8s
Forced reflow
32/95
—
LCP request discovery
31/95
—
Layout shift culprits
28/95
—
Improve image delivery
18/95
20.6s
Legacy JavaScript
13/95
2.0s
LCP breakdown
3/95
—
Best Practices
Best Practices recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Serves images with low resolution
51/95
—
Missing source maps for large first-party JavaScript
32/95
—
Does not use HTTPS
30/95
—
Uses third-party cookies
18/95
—
Issues were logged in the `Issues` panel in Chrome Devtools
18/95
—
Page lacks the HTML doctype, thus triggering quirks-mode
18/95
—
Charset declaration is missing or occurs too late in the HTML
18/95
—
Browser errors were logged to the console
1/95
—
SEO
SEO recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
Document does not have a meta description
41/95
—
Image elements do not have `[alt]` attributes
18/95
—
Page is blocked from indexing
7/95
—
Links do not have descriptive text
5/95
—
Links are not crawlable
1/95
—
Agentic (AI-readiness)
Agentic (AI-readiness) recommendations from Lighthouse, by sampled pages affected.
Recommendation
Pages
Est. saving
WebMCP tools registered
95/95
—
WebMCP form coverage
95/95
—
WebMCP schemas are valid
95/95
—
llms.txt follows recommendations
95/95
—
Cumulative Layout Shift
28/95
—
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 (95), WebMCP form coverage (95), WebMCP schemas are valid (95), llms.txt follows recommendations (95), Cumulative Layout Shift (28).
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