Performance
· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.87 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.87 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.034
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.27 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.89 s
Page Load Progression
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction5 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
BJS Bundles6 scripts, 61 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://statistiek.rijksoverheid.nl/containers/bf9c05f0-c13f-4e22-80c7-e603d39fc616.js | 79 KB | 36 KB (46%) | ✓ | 3rd |
| https://www.rijksoverheid.nl/webfiles/1750011834072/behaviour/core.js | 44 KB | 24 KB (55%) | ✓ | 3rd |
| https://www.rijksoverheid.nl/binaries/content/assets/rijksoverheid/behaviour/rop-page-feedback.min-20230526.js | 3 KB | — | ✓ | 3rd |
| https://statistiek.rijksoverheid.nl/ppms.js | 26 KB | — | ✓ | 3rd |
| https://survey-deploy.platformrijksoverheid.nl/js/pastease.js | 13 KB | — | ✓ | 3rd |
| https://www.rijksoverheid.nl/webfiles/1750011834072/behaviour/shared-ro/jquery-ui.js | 11 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
APage Weight Budget987 KB transferred, 26 requestsPASS
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost407ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.rijksoverheid.nl/ | 168ms | 3ms | 1ms | 3rd |
| Unattributable | 101ms | 2ms | 0ms | 3rd |
| https://statistiek.rijksoverheid.nl/containers/bf9c05f0-c13f-4e22-80c7-e603d39fc616.js | 73ms | 55ms | 14ms | 3rd |
| https://www.rijksoverheid.nl/webfiles/1750011834072/behaviour/core.js | 66ms | 53ms | 4ms | 3rd |
A+Font Loading5 fonts (260 KB)PASS
Web fonts
5
260 KB total
Render-blocking
0
of 5
Dominant font-display
swap
Most common across fonts
Font loading timeline
Optimization checklist
- Preload critical fonts (priority=high)
- Use woff2 format for all fonts
- Set font-display to swap, optional, or fallback
- Subset large fonts (≤100 KB each)
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
APage Weight Inventory26 resources · 987 KB · 61 KB savings availablePASS
~60.5 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 26 resources | 987.4 KiB | ||||||
Network Waterfall26 requests over 13565msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.rijksoverheid.nl www.rijksoverheid.nl | Other | 168ms | 8 KB | — | €2/mo | Optional |
Unattributable Unattributable | Other | 101ms | 0 KB | — | €1/mo | Optional |
statistiek.rijksoverheid.nl statistiek.rijksoverheid.nl | Other | 73ms | 79 KB | 46% | €1/mo | Optional |
www.rijksoverheid.nl www.rijksoverheid.nl | Other | 66ms | 44 KB | 55% | €1/mo | Optional |
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev
55% of www.rijksoverheid.nl's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev