www.luton.gov.uk: Lighthouse — week 2026-W44
Trend
| Week | Performance | Accessibility | Best practices | SEO |
|---|---|---|---|---|
| 2026-W44 | 36 | 96 | 73 | 100 |
| 2026-W45 | 30 | 96 | 73 | 100 |
Performance impact
- Avg extra LCP over 2.5s
- 6.9s
- Avg extra weight over 1.6 MB
- 1.03 MB
Medians across sampled pages
- Performance
- 36/100
- Accessibility
- 96/100
- Best practices
- 73/100
- SEO
- 100/100
- Agentic browsing
- 38/100
- Largest Contentful Paint
- 9.6s
- First Contentful Paint
- 3.2s
- Speed Index
- 4.8s
- Total Blocking Time
- 1.0s
- Cumulative Layout Shift
- 0
Recommendations
Performance
| Recommendation | Pages | Est. saving |
|---|---|---|
| Reduce unused JavaScript | 192/218 | 82.3 MB · 238.9s |
| Render-blocking requests | 192/218 | 298.1s |
| Reduce JavaScript execution time | 192/218 | 235.6s |
| Minimize main-thread work | 192/218 | 227.1s |
| Minify JavaScript | 192/218 | 4.3 MB · 23.1s |
| Reduce unused CSS | 192/218 | 5.1 MB · 5.2s |
| First Contentful Paint | 192/218 | — |
| Time to Interactive | 192/218 | — |
| Page prevented back/forward cache restoration | 192/218 | — |
| Network dependency tree | 192/218 | — |
| Total Blocking Time | 191/218 | — |
| Largest Contentful Paint | 190/218 | — |
| Use efficient cache lifetimes | 188/218 | 128.0s |
| Max Potential First Input Delay | 188/218 | — |
| Speed Index | 172/218 | — |
| Initial server response time was short | 124/218 | 70.3s |
| Layout shift culprits | 112/218 | — |
| Forced reflow | 93/218 | — |
| Document request latency | 87/218 | 57.1s |
| Modern HTTP | 8/218 | 3.0s |
| Improve image delivery | 5/218 | 14.9s |
| Legacy JavaScript | 4/218 | 0.8s |
| LCP request discovery | 4/218 | — |
| LCP breakdown | 2/218 | — |
Best Practices
| Recommendation | Pages | Est. saving |
|---|---|---|
| Browser errors were logged to the console | 192/218 | — |
| Uses third-party cookies | 192/218 | — |
| Issues were logged in the `Issues` panel in Chrome Devtools | 192/218 | — |
| Serves images with low resolution | 1/218 | — |
Agentic (AI-readiness)
| Recommendation | Pages | Est. saving |
|---|---|---|
| WebMCP tools registered | 192/218 | — |
| WebMCP form coverage | 192/218 | — |
| WebMCP schemas are valid | 192/218 | — |
| llms.txt follows recommendations | 192/218 | — |
| `ai-catalog.json` schema is valid | 192/218 | — |
| Accessibility tree is not well-formed | 117/218 | — |
| Cumulative Layout Shift | 112/218 | — |
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.