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
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.
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
i
Main HTML response has no Content-Encoding (uncompressed)
The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.
B
Main HTML Cache-Control
No Cache-Control header on main HTML response
REVIEW
No Cache-Control header on main HTML response
Info::
i
Main HTML response has no Cache-Control header
Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.
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.
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A
Page Weight Budget
857 KB transferred, 56 requests
PASS
857 KB transferred, 56 requests
Info::
✓
Page weighs 2.6 MB (857 KB transferred)
Info::
i
56 HTTP requests
Info::
i
Estimated 0.18 g CO2 per page load
857 KBtransferred
56 requests
0.18 g CO2 per page load
JavaScript455.1 KiB53%
Images154.2 KiB18%
HTML103.2 KiB12%
Fonts84.1 KiB10%
CSS50.0 KiB6%
Other8.0 KiB1%
Other2.1 KiB0%
02.4 MB4.9 MB
Under budget
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
3 fonts (84 KB)
PASS
3 fonts (84 KB)
Info::
i
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
84 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
memvYaGs126MiZpBA-UvWbX...woff2swap
Size42 KB
Load time439 ms
Start1.4 s
RiskFOUT — text flashes from fallback to web font
memvYaGs126MiZpBA-UvWbX...woff2swap
Size42 KB
Load time175 ms
Start4.2 s
RiskFOUT — text flashes from fallback to web font
memvYaGs126MiZpBA-UvWbX...woff2swap
Size0 KB
Load time169 ms
Start4.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
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
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
1 server-response signal(s) detected
PASS
1 server-response signal(s) detected
Info::
i
No `ETag` or `Last-Modified` -- conditional GET not supported
Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A
JavaScript Blocking
1 JS blocking issue(s) detected
PASS
1 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.
A+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
✓
No CSS performance depth issues detected
Network Waterfall
56 requests over 5011ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
86%of JavaScript execution is third-party
First-party Third-party2184ms · 371KB · €24/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
sitevalue.net
sitevalue.net
Other
617ms
0 KB
—
€7/mo
Costly
sitevalue.net
sitevalue.net
Other
486ms
6 KB
—
€5/mo
Costly
fundingchoicesmessages.google.com
fundingchoicesmessages.google.com
Other
313ms
69 KB
—
€3/mo
Costly
fundingchoicesmessages.google.com
fundingchoicesmessages.google.com
Other
246ms
70 KB
51%
€3/mo
Costly
sitevalue.net
sitevalue.net
Other
240ms
4 KB
—
€3/mo
Costly
pagead2.googlesyndication.com
pagead2.googlesyndication.com
Other
160ms
166 KB
83%
€2/mo
Optional
pagead2.googlesyndication.com
pagead2.googlesyndication.com
Other
121ms
55 KB
54%
€1/mo
Optional
sitevalue.net
Other
Costly
Execution617ms
Transfer0 KB
Monthly Cost€7/mo
sitevalue.net
Other
Costly
Execution486ms
Transfer6 KB
Monthly Cost€5/mo
fundingchoicesmessages.google.com
Other
Costly
Execution313ms
Transfer69 KB
Monthly Cost€3/mo
fundingchoicesmessages.google.com
Other
Costly
Execution246ms
Transfer70 KB
Unused51%
Monthly Cost€3/mo
sitevalue.net
Other
Costly
Execution240ms
Transfer4 KB
Monthly Cost€3/mo
pagead2.googlesyndication.com
Other
Optional
Execution160ms
Transfer166 KB
Unused83%
Monthly Cost€2/mo
pagead2.googlesyndication.com
Other
Optional
Execution121ms
Transfer55 KB
Unused54%
Monthly Cost€1/mo
These scripts may cost more than they're worth
sitevalue.net adds 617ms and costs ~€7/month
sitevalue.net adds 486ms and costs ~€5/month
fundingchoicesmessages.google.com adds 313ms and costs ~€3/month
fundingchoicesmessages.google.com adds 246ms and costs ~€3/month
sitevalue.net adds 240ms and costs ~€3/month
86% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
Why this matters
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
sitevalue.net takes 617ms 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
sitevalue.net takes 486ms 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
fundingchoicesmessages.google.com takes 313ms 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
fundingchoicesmessages.google.com takes 246ms 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
51% of fundingchoicesmessages.google.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
sitevalue.net takes 240ms 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
83% of pagead2.googlesyndication.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
54% of pagead2.googlesyndication.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.