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.
2.35 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.33 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
350 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.
2.35 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.
6.99 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 OptimizationAction6 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
CJS Execution CostAction1854ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.postgresql.org/ | 676ms | 5ms | 1ms | 3rd |
| Unattributable | 464ms | 144ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-FGJ68XB9NC&cx=c&_slc=1 | 368ms | 270ms | 77ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-WC97NKC | 241ms | 180ms | 57ms | 3rd |
| https://www.google-analytics.com/analytics.js | 105ms | 88ms | 10ms | 3rd |
BJS Bundles5 scripts, 128 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtm.js?id=GTM-WC97NKC | 120 KB | 65 KB (54%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-FGJ68XB9NC&cx=c&_slc=1 | 153 KB | 63 KB (41%) | ✓ | 3rd |
| https://www.postgresql.org/media/js/theme.js?54a05eb2 | 0 KB | — | ✓ | 3rd |
| https://www.postgresql.org/media/js/main.js?54a05eb2 | 2 KB | — | ✓ | 3rd |
| https://www.google-analytics.com/analytics.js | 21 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 Budget738 KB transferred, 24 requestsPASS
A+Text CompressionAll text resources are compressedPASS
A+Font Loading3 fonts (89 KB)PASS
Web fonts
3
89 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
APage Weight Inventory24 resources · 738 KB · 128 KB savings availablePASS
~127.8 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 24 resources | 738.1 KiB | ||||||
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall24 requests over 856msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.postgresql.org www.postgresql.org | Other | 676ms | 6 KB | — | €7/mo | Costly |
Unattributable Unattributable | Other | 464ms | 0 KB | — | €5/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 368ms | 153 KB | 41% | €4/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 241ms | 120 KB | 54% | €3/mo | Costly |
Google Analytics www.google-analytics.com | Analytics | 105ms | 21 KB | — | €1/mo | Optional |
These scripts may cost more than they're worth
- www.postgresql.org adds 676ms and costs ~€7/month
- Unattributable adds 464ms and costs ~€5/month
- Google Tag Manager adds 368ms and costs ~€4/month
- Google Tag Manager adds 241ms 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.postgresql.org takes 676ms 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 464ms 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
Google Tag Manager takes 368ms 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
Google Tag Manager takes 241ms 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
54% of Google Tag Manager'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