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.
416 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
773 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
32 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
936 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.21 s
Page Load Progression
DThird-Party ImpactAction81% third-party, 0 ms blockingFIX
DJS BundlesAction17 scripts, 346 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=AW-1072310887&cx=c>m=4e64k0 | 144 KB | 106 KB (73%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-YT4L4GZFH2&cx=c>m=4e64k0 | 179 KB | 66 KB (37%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-WBCHSDC | 156 KB | 66 KB (42%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=AW-1072310887 | 144 KB | 63 KB (43%) | ✓ | 3rd |
| https://mxtoolbox.com/bundles/mx3rdPartyMinDefer.js?v=K7K8ANEVoVmCmGAsvK00mQBAbR0PJIINwyiaoZ3lkzM1 | 39 KB | 24 KB (63%) | ✓ | 1st |
| https://cl.qualaroo.com/ki.js/61819/e3J.js | 54 KB | 22 KB (40%) | ✓ | 3rd |
| https://dev.visualwebsiteoptimizer.com/j.php?a=24147&u=https%3A%2F%2Fmxtoolbox.com%2F&r=0.6735492181856009 | 3 KB | — | ✓ | 3rd |
| https://cdnjs.cloudflare.com/ajax/libs/jsrender/1.0.14/jsrender.min.js | 12 KB | — | ✓ | 3rd |
| https://mxtoolbox.com/bundles/mx3rdPartyMinSync.js?v=oUKfU03s4Z9Hw1nBwX_yKENkbOzkxmy7orj67VkgSNc1 | 3 KB | — | ✓ | 1st |
| https://js.hs-scripts.com/14537821.js | 1 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
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
BImage Optimization6 images, 0 KB saveableREVIEW
BPage Weight Inventory44 resources · 1.0 MB · 346 KB savings availableREVIEW
~346.5 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 44 resources | 1.0 MiB | ||||||
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
APage Weight Budget1.0 MB transferred, 44 requestsPASS
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
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost243ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://js.hs-analytics.net/analytics/1776893700000/14537821.js | 100ms | 78ms | 2ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-YT4L4GZFH2&cx=c>m=4e64k0 | 87ms | 70ms | 10ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-WBCHSDC | 56ms | 46ms | 10ms | 3rd |
A+Font Loading2 fonts (105 KB)PASS
Web fonts
2
105 KB total
Render-blocking
0
of 2
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
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 ~51 KB and ~102 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+HTTP Cachingmax-age=300 (5 minutes)PASS
public, max-age=300
| Directive | Value | Meaning |
|---|---|---|
| public | — | Any cache may store this response |
| max-age | 300 | Cache for 5 minutes |
Network Waterfall44 requests over 1323msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
HubSpot Analytics js.hs-analytics.net | Analytics | 100ms | 42 KB | — | €1/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 87ms | 179 KB | 37% | €1/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 56ms | 156 KB | 42% | €1/mo | Optional |
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