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
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.
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+
JS Execution Cost
366ms total JS execution
PASS
366ms total JS execution
Info::
i
https://www.geiraonlus.it/: 219ms CPU time
Info::
i
https://www.geiraonlus.it/wp/wp-includes/js/jquery...: 75ms CPU time
5 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
5
243 KB total
Render-blocking
0
of 5
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
memvYaGs126MiZpBA-UvWbX...woff2swap
Size42 KB
Load time33 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
JTUSjIg69CK48gW7PXoo9Wl...woff2swap
Size8 KB
Load time24 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
modules.woffwoffswap
Size37 KB
Load time89 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
fa-solid-900.woff2woff2swap
Size79 KB
Load time109 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
fa-brands-400.woff2woff2swap
Size77 KB
Load time111 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)
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
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
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+
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.
Network Waterfall
40 requests over 1612ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
81%of JavaScript execution is third-party
First-party Third-party295ms · 62KB · €2/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.geiraonlus.it
www.geiraonlus.it
Other
219ms
32 KB
—
€1/mo
Costly
www.geiraonlus.it
www.geiraonlus.it
Other
75ms
30 KB
—
€0/mo
Optional
www.geiraonlus.it
Other
Costly
Execution219ms
Transfer32 KB
Monthly Cost€1/mo
www.geiraonlus.it
Other
Optional
Execution75ms
Transfer30 KB
Monthly Cost€0/mo
These scripts may cost more than they're worth
www.geiraonlus.it adds 219ms and costs ~€1/month
81% 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
www.geiraonlus.it takes 219ms 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.
375 ms
1.1 s
1.5 s
1.9 s
2.6 s