Performance
· 24 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.
14.86 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
32.44 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.78 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.
14.86 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.
32.47 s
Page Load Progression
FPage Weight BudgetAction4.1 MB transferred, 121 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 BundlesAction61 scripts, 2.5 MB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://app.netlify.com/assets/js/app.6fb2402b07138c6089aa.js | 851 KB | 741 KB (87%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/7884.0d6c4c920b73c92ce6c3.js | 344 KB | 259 KB (75%) | ✓ | 3rd |
| https://js.stripe.com/v3 | 248 KB | 182 KB (73%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js | 0 KB | 181 KB (54%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js | 336 KB | 181 KB (54%) | ✓ | 3rd |
| https://www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js | 336 KB | 181 KB (54%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/monitoring.vendor.11a3f8fda6fd77bc1b6d.js | 246 KB | 162 KB (66%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/highcharts.vendor.b2d7d17555326503a0ec.js | 172 KB | 161 KB (94%) | ✓ | 3rd |
| https://cdn.amplitude.com/engagement-browser/prod/split/2d478da3f712989100ed9c93f917366917176f65-chunk-QDOMPRCS.js | 168 KB | 83 KB (50%) | ✓ | 3rd |
| https://app.netlify.com/assets/js/ui.37f47c5245a2e38bf4d8.js | 87 KB | 71 KB (82%) | ✓ | 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 InventoryAction121 resources · 4.1 MB · 2.5 MB savings availableFIX
~2.5 MiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 121 resources | 4.1 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization4 images, 0 KB saveableREVIEW
BHTTP/3 (QUIC)HTTP/3 not advertisedREVIEW
CCompression AlgorithmActionMain response served uncompressedREVIEW
BMain HTML Cache-ControlNo Cache-Control header on main HTML responseREVIEW
BServer-Timing ObservabilityNo Server-Timing header foundREVIEW
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 Hints2 hints, 0 missing preconnectsPASS
Current Resource Hints
2 resource hints configured