Performance
· 25 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.
15.89 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
23.96 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
8.06 s
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.
15.89 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.
36.44 s
Page Load Progression
FPage Weight BudgetAction4.4 MB transferred, 134 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
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 BundlesAction66 scripts, 2.6 MB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://app.netlify.com/assets/js/app.a0f7af8e90e0c6ecd1cb.js | 778 KB | 644 KB (83%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/74899.c1fcfbc3efc89c6d34ce.js | 337 KB | 252 KB (75%) | ✓ | 3rd |
| https://js.stripe.com/v3 | 250 KB | 184 KB (74%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js | 347 KB | 180 KB (53%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js | 346 KB | 180 KB (53%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js | 0 KB | 180 KB (53%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js | 244 KB | 163 KB (67%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/highcharts.vendor.062d44badf31a5e6140f.js | 173 KB | 162 KB (94%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=AW-957669464&cx=c>m=4e69u2h1 | 165 KB | 115 KB (70%) | ✓ | 3rd |
| https://cdn.amplitude.com/engagement-browser/prod/split/27af780ed9b7852e0f27a662aeeea75cdcc108aa-chunk-GBGJOGSE.js | 170 KB | 85 KB (50%) | ✓ | 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 InventoryAction134 resources · 4.4 MB · 2.6 MB savings availableFIX
~2.6 MiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 134 resources | 4.4 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization6 images, 0 KB saveableREVIEW
BHTTP/3 (QUIC)HTTP/3 not advertisedREVIEW
CDocument CompressionActionDocument response served uncompressedREVIEW
BMain HTML Cache-ControlNo Cache-Control header on main HTML responseREVIEW
BServer-Timing ObservabilityNo Server-Timing header foundREVIEW
BJavaScript Blocking1 JS blocking issue(s) detectedREVIEW
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+JS Execution CostNo JS execution dataPASS
A+Font Loading1 fonts (34 KB)PASS
Web fonts
1
34 KB total
Render-blocking
0
of 1
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 Hints3 hints, 0 missing preconnectsPASS
Current Resource Hints
3 resource hints configured