data.cms.gov: Lighthouse — week 2026-W39
Trend
| Week | Performance | Accessibility | Best practices | SEO |
|---|---|---|---|---|
| 2026-W24 | 46 | 96 | 100 | 92 |
| 2026-W25 | 49 | 95 | 100 | 92 |
| 2026-W26 | 47 | 95 | 100 | 92 |
| 2026-W27 | 47 | 95 | 100 | 92 |
| 2026-W28 | 47 | 95 | 100 | 92 |
| 2026-W29 | 47 | 95 | 100 | 92 |
| 2026-W30 | 45 | 95 | 100 | 92 |
| 2026-W31 | 45 | 95 | 100 | 92 |
| 2026-W32 | 47 | 95 | 100 | 92 |
| 2026-W33 | 45 | 95 | 100 | 92 |
| 2026-W34 | 49 | 95 | 100 | 92 |
| 2026-W35 | 48 | 95 | 100 | 92 |
| 2026-W36 | 48 | 95 | 100 | 92 |
| 2026-W37 | 49 | 95 | 100 | 92 |
| 2026-W38 | 49 | 95 | 100 | 92 |
| 2026-W39 | 48 | 95 | 100 | 92 |
| 2026-W40 | 49 | 98 | 100 | 92 |
Performance impact
- Avg extra LCP over 2.5s
- 9.5s
- Avg extra weight over 1.6 MB
- 3.49 MB
Medians across sampled pages
- Performance
- 48/100
- Accessibility
- 95/100
- Best practices
- 100/100
- SEO
- 92/100
- Agentic browsing
- 50/100
- Largest Contentful Paint
- 10.3s
- First Contentful Paint
- 3.4s
- Speed Index
- 4.2s
- Total Blocking Time
- 0.7s
- Cumulative Layout Shift
- 0
Recommendations
Performance
| Recommendation | Pages | Est. saving |
|---|---|---|
| Reduce unused JavaScript | 216/258 | 187.8 MB · 845.5s |
| Render-blocking requests | 216/258 | 227.7s |
| Reduce unused CSS | 216/258 | 21.3 MB · 114.0s |
| First Contentful Paint | 216/258 | — |
| Largest Contentful Paint | 216/258 | — |
| Time to Interactive | 216/258 | — |
| Page prevented back/forward cache restoration | 216/258 | — |
| Network dependency tree | 215/258 | — |
| Minimize main-thread work | 210/258 | 186.3s |
| Reduce JavaScript execution time | 210/258 | 174.2s |
| Max Potential First Input Delay | 203/258 | — |
| Total Blocking Time | 202/258 | — |
| Speed Index | 195/258 | — |
| Use efficient cache lifetimes | 180/258 | 46.9s |
| Font display | 149/258 | 15.6s |
| Legacy JavaScript | 87/258 | 12.9s |
| Forced reflow | 66/258 | — |
| Layout shift culprits | 48/258 | — |
| LCP request discovery | 39/258 | — |
| Initial server response time was short | 36/258 | 3.3s |
| Improve image delivery | 10/258 | 1.4s |
| LCP breakdown | 10/258 | — |
| Duplicated JavaScript | 3/258 | 0.6s |
| Avoid multiple page redirects | 1/258 | 1.1s |
| Document request latency | 1/258 | 0.1s |
Best Practices
| Recommendation | Pages | Est. saving |
|---|---|---|
| Browser errors were logged to the console | 72/258 | — |
| Missing source maps for large first-party JavaScript | 68/258 | — |
| Uses third-party cookies | 20/258 | — |
| Issues were logged in the `Issues` panel in Chrome Devtools | 20/258 | — |
SEO
| Recommendation | Pages | Est. saving |
|---|---|---|
| Document does not have a meta description | 156/258 | — |
| Links are not crawlable | 146/258 | — |
| Page is blocked from indexing | 82/258 | — |
| Links do not have descriptive text | 4/258 | — |
Agentic (AI-readiness)
| Recommendation | Pages | Est. saving |
|---|---|---|
| WebMCP tools registered | 216/258 | — |
| WebMCP form coverage | 216/258 | — |
| WebMCP schemas are valid | 216/258 | — |
| llms.txt follows recommendations | 216/258 | — |
| Accessibility tree is not well-formed | 132/258 | — |
| Cumulative Layout Shift | 48/258 | — |
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.