Consider code splitting or tree shaking to reduce unused code.
Why this matters
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.
Why this matters
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.
Why this matters
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.
Why this matters
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.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
D
Asset Compression
Action
2 of 3 asset hosts serve text uncompressed
FIX
2 of 3 asset hosts serve text uncompressed
Warning::
!
image-tc.galaxy.tf serves text assets uncompressed (assets: 38)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Got: image-tc.galaxy.tf (image/svg+xml)
Warning::
!
fonts.googleapis.com serves text assets uncompressed (assets: 8)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Got: fonts.googleapis.com (text/css)
Info::
✓
www.googletagmanager.com serves assets with brotli (assets: 5)
https://image-tc.galaxy.tf/wipng-4mjbeqpef6vwcujkv... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wisvg-auwi8uvqhm4ryhwtp... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wijpeg-1dj0e92ubejq9jge... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wijpeg-97x4b5bdvcoyud51... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wijpeg-bup5u06i0xj1sc6n... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wijpeg-c4v9kkjybcu287op... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wijpeg-2m258tyuocrthvim... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://image-tc.galaxy.tf/wipng-blm332wqxjtip0a6r... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
36images3.2 MB
0oversized-0 KB
32legacy format
9missing 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
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
Set explicit width and height to prevent CLS.
Why this matters
Performance issues directly impact user engagement and conversion rates.
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
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
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
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
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
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
Document Compression
Document response uses gzip; brotli would be ~20% smaller
REVIEW
Document 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.
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::
!
4 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 5.0 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
4 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
4
58 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
pxiByp8kv8JHgFVrLCz7Z1x...woff2swap
Size8 KB
Load time20 ms
Start798 ms
RiskFOUT — text flashes from fallback to web font
pxiEyp8kv8JHgFVrJJfecnF...woff2swap
Size8 KB
Load time20 ms
Start798 ms
RiskFOUT — text flashes from fallback to web font
Qw3GZR9MED_6PSuS_50nEaV...woff2swap
Size22 KB
Load time22 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
1Ptxg8zYS_SKggPN4iEgvnH...woff2swap
Size21 KB
Load time31 ms
Start1.2 s
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)
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
8 hints, 0 missing preconnects
PASS
8 hints, 0 missing preconnects
Info::
✓
Page uses 8 resource hint(s)
Current Resource Hints
preconnect
1
preload
7
dns-prefetch—
prefetch—
8 resource hints configured
A+
HTTP/3 (QUIC)
HTTP/3 advertised via Alt-Svc
PASS
HTTP/3 advertised via Alt-Svc
Info::
✓
HTTP/3 (QUIC) is supported
First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.
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+
Main HTML Cache-Control
Main HTML uses no-cache -- safe revalidate-on-request policy
PASS
Main HTML uses no-cache -- safe revalidate-on-request policy
Info::
✓
Main HTML uses no-cache -- safe revalidate-on-request policy
Got: no-cache
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::
✓
Both `ETag` and `Last-Modified` present -- efficient revalidation supported
The page returns both `ETag` (content hash) and `Last-Modified` (timestamp) headers. Browsers can issue conditional GETs with `If-None-Match` or `If-Modified-Since`; the server returns 304 Not Modified for unchanged content, saving bandwidth. ETag is the more reliable of the two (timestamps fail in DST transitions and clock skew).
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.
Network Waterfall
89 requests over 2325ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
29%of JavaScript execution is third-party
First-party Third-party1462ms · 812KB · €8/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Google Tag Manager
www.googletagmanager.com
Tag Manager
319ms
166 KB
42%
€2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
283ms
166 KB
41%
€2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
278ms
144 KB
42%
€1/mo
Costly
cmp.secureprivacy.ai
cmp.secureprivacy.ai
Other
277ms
40 KB
54%
€1/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
235ms
132 KB
49%
€1/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
71ms
165 KB
69%
€0/mo
Optional
Google Tag Manager
Tag Manager
Costly
Execution319ms
Transfer166 KB
Unused42%
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Costly
Execution283ms
Transfer166 KB
Unused41%
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Costly
Execution278ms
Transfer144 KB
Unused42%
Monthly Cost€1/mo
cmp.secureprivacy.ai
Other
Costly
Execution277ms
Transfer40 KB
Unused54%
Monthly Cost€1/mo
Google Tag Manager
Tag Manager
Costly
Execution235ms
Transfer132 KB
Unused49%
Monthly Cost€1/mo
Google Tag Manager
Tag Manager
Optional
Execution71ms
Transfer165 KB
Unused69%
Monthly Cost€0/mo
These scripts may cost more than they're worth
Google Tag Manager adds 319ms and costs ~€2/month
Google Tag Manager adds 283ms and costs ~€2/month
Google Tag Manager adds 278ms and costs ~€1/month
cmp.secureprivacy.ai adds 277ms and costs ~€1/month
Google Tag Manager adds 235ms and costs ~€1/month
Google Tag Manager takes 319ms 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 283ms 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 278ms 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
cmp.secureprivacy.ai takes 277ms 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
54% of cmp.secureprivacy.ai'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
Google Tag Manager takes 235ms 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
69% of Google Tag Manager'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.