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.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.11 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
264 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.98 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.
5.85 s
Page Load Progression
DPage Weight BudgetAction2.3 MB transferred, 34 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
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DJS BundlesAction3 scripts, 444 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.uni-heidelberg.de/assets/index-C-OsSKiI.js | 822 KB | 289 KB (35%) | ✓ | 3rd |
| https://www.uni-heidelberg.de/assets/tex-mml-chtml-3GpWM_o-.js | 321 KB | 155 KB (48%) | ✓ | 3rd |
| https://cdn-eu.usefathom.com/script.js | 3 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
FPage Weight InventoryAction34 resources · 2.3 MB · 444 KB savings availableFIX
~443.8 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 34 resources | 2.3 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization16 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
CJS Execution CostAction1619ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.uni-heidelberg.de/assets/index-C-OsSKiI.js | 861ms | 704ms | 3ms | 3rd |
| https://www.uni-heidelberg.de/en | 374ms | 4ms | 11ms | 3rd |
| Unattributable | 233ms | 2ms | 0ms | 3rd |
| https://www.uni-heidelberg.de/assets/tex-mml-chtml-3GpWM_o-.js | 150ms | 113ms | 37ms | 3rd |
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 (44 KB)PASS
Web fonts
3
44 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
Network Waterfall34 requests over 6591msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.uni-heidelberg.de www.uni-heidelberg.de | Other | 861ms | 822 KB | 35% | €9/mo | Costly |
www.uni-heidelberg.de www.uni-heidelberg.de | Other | 374ms | 44 KB | — | €4/mo | Costly |
Unattributable Unattributable | Other | 233ms | 0 KB | — | €3/mo | Costly |
www.uni-heidelberg.de www.uni-heidelberg.de | Other | 150ms | 321 KB | 48% | €2/mo | Optional |
These scripts may cost more than they're worth
- www.uni-heidelberg.de adds 861ms and costs ~€9/month
- www.uni-heidelberg.de adds 374ms and costs ~€4/month
- Unattributable adds 233ms 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.uni-heidelberg.de takes 861ms 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.uni-heidelberg.de takes 374ms 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 233ms 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