JavaScript is 1.3 MB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 1.3 MB
Warning::
!
113 HTTP requests — consider bundling or reducing
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
Info::
i
Estimated 0.33 g CO2 per page load
1.6 MBtransferred
113 requests
0.33 g CO2 per page load
JavaScript1.3 MiB83%
Fonts96.9 KiB6%
Images66.4 KiB4%
CSS52.5 KiB3%
Other52.2 KiB3%
Other3.8 KiB0%
Other2.1 KiB0%
HTML1.8 KiB0%
Other705 B0%
Other0 B0%
Other0 B0%
02.4 MB4.9 MB
Approaching limit
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Why this matters
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.
Why this matters
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
B
Third-Party Impact
44% third-party, 0 ms blocking
REVIEW
44% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 44% of page weight (711.9 KiB of 1.6 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
56%
44%
First-party Third-party
B
Image Optimization
17 images, 0 KB saveable
REVIEW
17 images, 0 KB saveable
Warning::
!
https://5a3606d6-a55c-4624-a79e-1a13dc413b14.seals... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
17images66 KB
0oversized-0 KB
5legacy format
1missing dimensionsCLS risk
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
i
HTTP/3 (QUIC) is not advertised
HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.
B
Compression Algorithm
Main response uses gzip; brotli would be ~20% smaller
REVIEW
Main response uses gzip; brotli would be ~20% smaller
Info::
i
Main HTML response uses gzip (brotli would be ~20% smaller)
All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.
C
Main HTML Cache-Control
Action
Main HTML max-age=14400 (~240min) is aggressive
REVIEW
Main HTML max-age=14400 (~240min) is aggressive
Warning::
!
Main HTML cached for 240 minutes -- risks stale auth / SPA state
Long max-age on the main HTML document means users may see outdated auth state, SPA shells, or A/B variants until the cache expires. Consider Cache-Control: no-cache (or max-age=300) for HTML and let your hashed assets (JS/CSS/images) carry the long cache instead.
Got: public, max-age=14400
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
No Server-Timing header found
Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 JS blocking issue(s) detected
Warning::
!
2 render-blocking <script src> tag(s) without async/defer
Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
Warning::
!
Total JS execution time is 8.3 s -- over the 3.5s budget
Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
✓
All text resources are compressed
All text resources are properly compressed.
A+
Font Loading
4 fonts (97 KB)
PASS
4 fonts (97 KB)
Info::
i
4 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
4
97 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
b7f9c63797376039085e.ttfttfswap
Size36 KB
Load time47 ms
Start459 ms
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
XRXV3I6Li01BKofINeaBTMn...woff2swap
Size38 KB
Load time27 ms
Start490 ms
RiskFOUT — text flashes from fallback to web font
pe0uMIWbN4JFplR2HDVyB_2...woff2swap
Size11 KB
Load time25 ms
Start712 ms
RiskFOUT — text flashes from fallback to web font
pe0rMIWbN4JFplR2FI5XEtC...woff2swap
Size11 KB
Load time25 ms
Start713 ms
RiskFOUT — text flashes from fallback to web font
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 ~11 KB and ~22 ms
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
✓
No render-blocking resources detected
A
Resource Hints
7 hints, 0 missing preconnects
PASS
7 hints, 0 missing preconnects
Info::
i
2 dns-prefetch redundant with preconnect on same origin
preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://cms-wildtornado-cdn.s3.eu-central-1.amazonaws.com, https://cms-wildreel-cdn.s3.eu-central-1.amazonaws.com. Remove the redundant dns-prefetch entries.
Info::
i
2 URL(s) appear in multiple hints
The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: https://cms-wildtornado-cdn.s3.eu-central-1.amazonaws.com (preconnect+dns-prefetch), https://cms-wildreel-cdn.s3.eu-central-1.amazonaws.com (preconnect+dns-prefetch).
Info::
✓
Page uses 7 resource hint(s)
Current Resource Hints
preconnect
4
preload
1
dns-prefetch
2
prefetch—
7 resource hints configured
preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://cms-wildtornado-cdn.s3.eu-central-1.amazonaws.com, https://cms-wildreel-cdn.s3.eu-central-1.amazonaws.com. Remove the redundant dns-prefetch entries.
Why this matters
Performance issues directly impact user engagement and conversion rates.
The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: https://cms-wildtornado-cdn.s3.eu-central-1.amazonaws.com (preconnect+dns-prefetch), https://cms-wildreel-cdn.s3.eu-central-1.amazonaws.com (preconnect+dns-prefetch).
Why this matters
Performance issues directly impact user engagement and conversion rates.
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
✓
LCP image preload audit not available for this scan
A+
Server Response Intelligence
2 server-response signal(s) detected
PASS
2 server-response signal(s) detected
Info::
✓
`Vary` header declared: Accept-Encoding
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
Info::
✓
`Last-Modified` present -- timestamp-based conditional GET supported
Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.
Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.
A+
HTTP Caching
max-age=14400 (4 hours)
PASS
max-age=14400 (4 hours)
Info::
✓
Cache-Control header is set
Got: public, max-age=14400
Info::
✓
Effective TTL: 4 hours (max-age=14400)
Info::
✓
Last-Modified header present
Cache-Control
public, max-age=14400
Directive
Value
Meaning
public
—
Any cache may store this response
max-age
14400
Cache for 4 hours
Effective TTL: 14400 seconds
Network Waterfall
113 requests over 5786ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
21%of JavaScript execution is third-party
First-party Third-party1766ms · 540KB · €19/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Google Tag Manager
www.googletagmanager.com
Tag Manager
467ms
0 KB
—
€5/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
341ms
142 KB
44%
€4/mo
Costly
cdn.onesignal.com
cdn.onesignal.com
Other
243ms
69 KB
64%
€3/mo
Costly
Microsoft Clarity
scripts.clarity.ms
Session Replay
217ms
0 KB
—
€2/mo
Costly
Zendesk Widget
static.zdassets.com
Customer Support
208ms
184 KB
63%
€2/mo
Costly
Hotjar
script.hotjar.com
Session Replay
152ms
0 KB
—
€2/mo
Optional
Zendesk Widget
static.zdassets.com
Customer Support
87ms
139 KB
91%
€1/mo
Optional
Zendesk Widget
static.zdassets.com
Customer Support
51ms
6 KB
—
€1/mo
Optional
Google Tag Manager
Tag Manager
Costly
Execution467ms
Transfer0 KB
Monthly Cost€5/mo
Google Tag Manager
Tag Manager
Costly
Execution341ms
Transfer142 KB
Unused44%
Monthly Cost€4/mo
cdn.onesignal.com
Other
Costly
Execution243ms
Transfer69 KB
Unused64%
Monthly Cost€3/mo
Microsoft Clarity
Session Replay
Costly
Execution217ms
Transfer0 KB
Monthly Cost€2/mo
Zendesk Widget
Customer Support
Costly
Execution208ms
Transfer184 KB
Unused63%
Monthly Cost€2/mo
Hotjar
Session Replay
Optional
Execution152ms
Transfer0 KB
Monthly Cost€2/mo
Zendesk Widget
Customer Support
Optional
Execution87ms
Transfer139 KB
Unused91%
Monthly Cost€1/mo
Zendesk Widget
Customer Support
Optional
Execution51ms
Transfer6 KB
Monthly Cost€1/mo
These scripts may cost more than they're worth
Google Tag Manager adds 467ms and costs ~€5/month
Google Tag Manager adds 341ms and costs ~€4/month
cdn.onesignal.com adds 243ms and costs ~€3/month
Microsoft Clarity adds 217ms and costs ~€2/month
Zendesk Widget adds 208ms and costs ~€2/month
Google Tag Manager takes 467ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 341ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
cdn.onesignal.com takes 243ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
64% of cdn.onesignal.com's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
Microsoft Clarity takes 217ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Zendesk Widget takes 208ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
63% of Zendesk Widget's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
91% of Zendesk Widget's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
727 ms
1.5 s
2.2 s
2.9 s
5.8 s