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.
4.28 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
19.65 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4.71 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
1.143
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.73 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.
50.71 s
Page Load Progression
FPage Weight BudgetAction10.4 MB transferred, 186 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
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
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
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
FJS Execution CostAction14270ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/quiz.umd.js | 2369ms | 205ms | 1893ms | 3rd |
| Unattributable | 2345ms | 92ms | 0ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/react-components.umd.js | 1557ms | 1194ms | 281ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/viewer.umd.js | 1262ms | 1051ms | 204ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/vendors.js | 991ms | 652ms | 235ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/Core.js | 792ms | 490ms | 298ms | 3rd |
| https://www.uni-mainz.de/ | 747ms | 30ms | 25ms | 3rd |
| https://www.uni-mainz.de/wp-includes/js/dist/vendor/react.min.js?ver=18.3.1.1 | 721ms | 493ms | 1ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/commons.js | 682ms | 144ms | 534ms | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/EventOverlayFactory.js | 475ms | 437ms | 35ms | 3rd |
Showing top 10 of 24 scripts
FJS BundlesAction122 scripts, 4.7 MB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/commons.js | 0 KB | 343 KB (84%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/commons.js | 0 KB | 343 KB (84%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/commons.js | 0 KB | 343 KB (84%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/commons.js | 407 KB | 343 KB (84%) | ✓ | 3rd |
| https://www.uni-mainz.de/wp-includes/js/dist/components.min.js?ver=0d72a218dfea8f6f442f | 247 KB | 199 KB (80%) | ✓ | 3rd |
| https://www.uni-mainz.de/wp-content/plugins/jgu-base/dist/frontend.js?ver=2655bfff0bd6860a7baa | 280 KB | 167 KB (60%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/react-components.umd.js | 0 KB | 163 KB (59%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/react-components.umd.js | 0 KB | 163 KB (59%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/react-components.umd.js | 278 KB | 163 KB (59%) | ✓ | 3rd |
| https://video.uni-mainz.de/Panopto/Cache/13.20.3.01092/Scripts/Panopto/Bundles/react-components.umd.js | 0 KB | 163 KB (59%) | ✓ | 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
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 InventoryAction186 resources · 10.4 MB · 4.7 MB savings availableFIX
~4.7 MiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 186 resources | 10.4 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction14 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
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
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 (421 KB)PASS
Web fonts
3
421 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
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)
Fixing the unchecked items could save ~163 KB and ~326 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints2 hints, 0 missing preconnectsPASS
Current Resource Hints
2 resource hints configured
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall186 requests over 5262msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
video.uni-mainz.de video.uni-mainz.de | Other | 2369ms | 0 KB | 1% | €26/mo | Costly |
Unattributable Unattributable | Other | 2345ms | 0 KB | — | €25/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 1557ms | 0 KB | 59% | €17/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 1262ms | 0 KB | 20% | €14/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 991ms | 0 KB | 39% | €11/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 792ms | 0 KB | 69% | €9/mo | Costly |
www.uni-mainz.de www.uni-mainz.de | Other | 747ms | 39 KB | — | €8/mo | Costly |
www.uni-mainz.de www.uni-mainz.de | Other | 721ms | 4 KB | — | €8/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 682ms | 0 KB | 84% | €7/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 475ms | 0 KB | 55% | €5/mo | Costly |
www.uni-mainz.de www.uni-mainz.de | Other | 357ms | 280 KB | 60% | €4/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 231ms | 0 KB | 67% | €3/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 227ms | 0 KB | — | €2/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 226ms | 11 KB | — | €2/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 204ms | 0 KB | 88% | €2/mo | Costly |
video.uni-mainz.de video.uni-mainz.de | Other | 179ms | 11 KB | — | €2/mo | Optional |
video.uni-mainz.de video.uni-mainz.de | Other | 142ms | 0 KB | 88% | €2/mo | Optional |
video.uni-mainz.de video.uni-mainz.de | Other | 136ms | 0 KB | — | €1/mo | Optional |
www.uni-mainz.de www.uni-mainz.de | Other | 125ms | 153 KB | 56% | €1/mo | Optional |
www.uni-mainz.de www.uni-mainz.de | Other | 123ms | 247 KB | 80% | €1/mo | Optional |
www.uni-mainz.de www.uni-mainz.de | Other | 115ms | 43 KB | — | €1/mo | Optional |
video.uni-mainz.de video.uni-mainz.de | Other | 106ms | 0 KB | 65% | €1/mo | Optional |
video.uni-mainz.de video.uni-mainz.de | Other | 105ms | 0 KB | 52% | €1/mo | Optional |
www.uni-mainz.de www.uni-mainz.de | Other | 55ms | 41 KB | — | €1/mo | Optional |
These scripts may cost more than they're worth
- video.uni-mainz.de adds 2369ms and costs ~€26/month
- Unattributable adds 2345ms and costs ~€25/month
- video.uni-mainz.de adds 1557ms and costs ~€17/month
- video.uni-mainz.de adds 1262ms and costs ~€14/month
- video.uni-mainz.de adds 991ms and costs ~€11/month
- video.uni-mainz.de adds 792ms and costs ~€9/month
- www.uni-mainz.de adds 747ms and costs ~€8/month
- www.uni-mainz.de adds 721ms and costs ~€8/month
- video.uni-mainz.de adds 682ms and costs ~€7/month
- video.uni-mainz.de adds 475ms and costs ~€5/month
- www.uni-mainz.de adds 357ms and costs ~€4/month
- video.uni-mainz.de adds 231ms and costs ~€3/month
- video.uni-mainz.de adds 227ms and costs ~€2/month
- video.uni-mainz.de adds 226ms and costs ~€2/month
- video.uni-mainz.de adds 204ms and costs ~€2/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
video.uni-mainz.de takes 2369ms 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 2345ms 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
video.uni-mainz.de takes 1557ms 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
59% of video.uni-mainz.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
video.uni-mainz.de takes 1262ms 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
video.uni-mainz.de takes 991ms 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
video.uni-mainz.de takes 792ms 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
69% of video.uni-mainz.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.uni-mainz.de takes 747ms 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-mainz.de takes 721ms 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
video.uni-mainz.de takes 682ms 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
84% of video.uni-mainz.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
video.uni-mainz.de takes 475ms 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
55% of video.uni-mainz.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.uni-mainz.de takes 357ms 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
60% of www.uni-mainz.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
video.uni-mainz.de takes 231ms 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
67% of video.uni-mainz.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
video.uni-mainz.de takes 227ms 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
video.uni-mainz.de takes 226ms 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
video.uni-mainz.de takes 204ms 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
88% of video.uni-mainz.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
88% of video.uni-mainz.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
56% of www.uni-mainz.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
80% of www.uni-mainz.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
65% of video.uni-mainz.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
52% of video.uni-mainz.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