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.
924 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.650
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
924 ms
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.49 s
Page Load Progression
423 ms
847 ms
1.3 s 1.7 s
2.1 s 2.5 s 3.0 s
3.4 sFPage Weight BudgetAction5.4 MB transferred, 113 requestsFIX
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
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
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DPage Weight InventoryAction113 resources · 5.4 MB · 151 KB savings availableFIX
~151.1 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 113 resources | 5.4 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BJS Execution Cost773ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.muenchen.de/ | 262ms | 22ms | 0ms | 3rd |
| Unattributable | 257ms | 31ms | 0ms | 3rd |
| https://www.muenchen.de/themes/custom/muenchen/js/bundle.js?t9bgn6 | 253ms | 91ms | 0ms | 3rd |
CJS BundlesAction14 scripts, 151 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.muenchen.de/themes/custom/muenchen/js/bundle.js?t9bgn6 | 89 KB | 64 KB (72%) | ✓ | 3rd |
| https://app.usercentrics.eu/browser-ui/3.99.0/index.module.js | 121 KB | 57 KB (48%) | ✓ | 3rd |
| https://muenchenapis.de/proxies/dbs-login/proxy.php | 147 KB | 30 KB (21%) | ✓ | 3rd |
| https://static.etracker.com/code/e.js | 31 KB | — | ✓ | 3rd |
| https://app.usercentrics.eu/browser-ui/latest/loader.js | 11 KB | — | ✓ | 3rd |
| https://code.etracker.com/code/e.js | 31 KB | — | ✓ | 3rd |
| https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js | 30 KB | — | ✓ | 3rd |
| https://code.etracker.com/t.js?v=ee485f6&et=Shbe3K | 10 KB | — | ✓ | 3rd |
| https://www.etracker.de/cntcc?&&et=Shbe3K&v=6.0&tc=17768961376545&pagename=muenchen.de%20-%20Das%20offizielle%20Stadtportal%20f%C3%BCr%20M%C3%BCnchen&ilevel=1&areas=Drupal%2FMDE%2Faktuell%2Cteaser_overview%2CDesktop&et_source_url=https%3A%2F%2Fwww.muenchen.de%2F&cc_ordercurr=EUR&cc_ordertype=lead&cc_baskettype=basket&block_cookies=true&respect_dnt=true&et_bs=1&code_source=%2F%2Fcode.etracker.com%2Fcode%2Fe.js&code_async=true&page_id=896137433&et_sbscr=0&coid=582b7f1dce00345cf3f41c4d1d960cee&et_cblk=1&et_cd=www.muenchen.de&dh=boqjtgjsL%2FiBQ4n4Cxa%2FdOxRsyx4G5aw&clt=24 | 0 KB | — | ✓ | 3rd |
| https://app.usercentrics.eu/browser-ui/3.99.0/DefaultData-3e2b2c3c-a6380bf2.js | 1 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
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
AImage Optimization51 images, 0 KB saveablePASS
A+Font Loading5 fonts (82 KB)PASS
Web fonts
5
82 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
Network Waterfall113 requests over 1078msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.muenchen.de www.muenchen.de | Other | 262ms | 45 KB | — | €3/mo | Costly |
Unattributable Unattributable | Other | 257ms | 0 KB | — | €3/mo | Costly |
www.muenchen.de www.muenchen.de | Other | 253ms | 89 KB | 72% | €3/mo | Costly |
These scripts may cost more than they're worth
- www.muenchen.de adds 262ms and costs ~€3/month
- Unattributable adds 257ms and costs ~€3/month
- www.muenchen.de adds 253ms 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.muenchen.de takes 262ms 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
Unattributable takes 257ms 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.muenchen.de takes 253ms 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
72% of www.muenchen.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