Performance
· 17 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.
3.46 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.99 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.73 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.229
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.50 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.
13.50 s
Page Load Progression
375 ms 750 ms 1.1 s
1.5 s
1.9 s 2.2 s 2.6 s 3.0 sDPage Weight BudgetAction2.1 MB transferred, 33 requestsFIX
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.
CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FJS Execution CostAction6420ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.bundesregierung.de/resource/themes/relaunch/js/relaunch-1562518-106.js | 2477ms | 1647ms | 341ms | 3rd |
| https://www.bundesregierung.de/breg-de | 2406ms | 62ms | 13ms | 3rd |
| https://dashboard.stage.bio/static/bundle.js | 669ms | 202ms | 75ms | 3rd |
| Unattributable | 342ms | 9ms | 0ms | 3rd |
| https://www.bundesregierung.de/resource/themes/relaunch/css/relaunch-1562520-111.css | 320ms | 0ms | 0ms | 3rd |
| https://analytics.bundesregierung.de/piwik.js | 103ms | 83ms | 16ms | 3rd |
| https://www.bundesregierung.de/resource/themes/relaunch/js/commons-2243502-6.js | 103ms | 27ms | 15ms | 3rd |
FJS BundlesAction4 scripts, 582 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.bundesregierung.de/resource/themes/relaunch/js/relaunch-1562518-106.js | 580 KB | 419 KB (74%) | ✓ | 3rd |
| https://dashboard.stage.bio/static/bundle.js | 159 KB | 99 KB (62%) | ✓ | 3rd |
| https://analytics.bundesregierung.de/piwik.js | 103 KB | 64 KB (63%) | ✓ | 3rd |
| https://www.bundesregierung.de/resource/themes/relaunch/js/commons-2243502-6.js | 34 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
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
FPage Weight InventoryAction33 resources · 2.1 MB · 582 KB savings availableFIX
~582.2 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 33 resources | 2.1 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization20 images, 0 KB saveableREVIEW
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading3 fonts (120 KB)PASS
Web fonts
3
120 KB total
Render-blocking
0
of 3
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
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall33 requests over 1247msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.bundesregierung.de www.bundesregierung.de | Other | 2477ms | 580 KB | 74% | €27/mo | Costly |
www.bundesregierung.de www.bundesregierung.de | Other | 2406ms | 24 KB | — | €26/mo | Costly |
dashboard.stage.bio dashboard.stage.bio | Other | 669ms | 159 KB | 62% | €7/mo | Costly |
Unattributable Unattributable | Other | 342ms | 0 KB | — | €4/mo | Costly |
www.bundesregierung.de www.bundesregierung.de | Other | 320ms | 236 KB | — | €3/mo | Costly |
analytics.bundesregierung.de analytics.bundesregierung.de | Other | 103ms | 103 KB | 63% | €1/mo | Optional |
www.bundesregierung.de www.bundesregierung.de | Other | 103ms | 34 KB | — | €1/mo | Optional |
These scripts may cost more than they're worth
- www.bundesregierung.de adds 2477ms and costs ~€27/month
- www.bundesregierung.de adds 2406ms and costs ~€26/month
- dashboard.stage.bio adds 669ms and costs ~€7/month
- Unattributable adds 342ms and costs ~€4/month
- www.bundesregierung.de adds 320ms and costs ~€3/month
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
www.bundesregierung.de takes 2477ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
74% of www.bundesregierung.de'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
www.bundesregierung.de takes 2406ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
dashboard.stage.bio takes 669ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
62% of dashboard.stage.bio'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
Unattributable takes 342ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
www.bundesregierung.de takes 320ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
63% of analytics.bundesregierung.de'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