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.
B
JavaScript Blocking
1 JS blocking issue(s) detected
REVIEW
1 JS blocking issue(s) detected
Warning::
!
16 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+
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
7 fonts (121 KB)
PASS
7 fonts (121 KB)
Info::
i
7 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
7
121 KB total
Render-blocking
0
of 7
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
pxiEyp8kv8JHgFVrJJfecnF...woff2swap
Size8 KB
Load time21 ms
Start824 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLGT9Z1x...woff2swap
Size8 KB
Load time20 ms
Start887 ms
RiskFOUT — text flashes from fallback to web font
Flaticon.woffwoffswap
Size7 KB
Load time60 ms
Start887 ms
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
fontawesome-webfont.woff2woff2swap
Size76 KB
Load time66 ms
Start887 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLCz7Z1x...woff2swap
Size8 KB
Load time21 ms
Start888 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLEj6Z1x...woff2swap
Size8 KB
Load time25 ms
Start888 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLDz8Z1x...woff2swap
Size8 KB
Load time26 ms
Start985 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 ~2 KB and ~4 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+
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.
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+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Seeweb
Network Waterfall
59 requests over 5462ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
90%of JavaScript execution is third-party
First-party Third-party2724ms · 191KB · €30/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.pinogalvagno.com
www.pinogalvagno.com
Other
1739ms
6 KB
—
€19/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
335ms
121 KB
57%
€4/mo
Costly
www.pinogalvagno.com
www.pinogalvagno.com
Other
281ms
33 KB
—
€3/mo
Costly
www.pinogalvagno.com
www.pinogalvagno.com
Other
164ms
1 KB
—
€2/mo
Optional
www.pinogalvagno.com
www.pinogalvagno.com
Other
136ms
8 KB
—
€1/mo
Optional
Google Analytics
www.google-analytics.com
Analytics
69ms
21 KB
—
€1/mo
Optional
www.pinogalvagno.com
Other
Costly
Execution1739ms
Transfer6 KB
Monthly Cost€19/mo
Google Tag Manager
Tag Manager
Costly
Execution335ms
Transfer121 KB
Unused57%
Monthly Cost€4/mo
www.pinogalvagno.com
Other
Costly
Execution281ms
Transfer33 KB
Monthly Cost€3/mo
www.pinogalvagno.com
Other
Optional
Execution164ms
Transfer1 KB
Monthly Cost€2/mo
www.pinogalvagno.com
Other
Optional
Execution136ms
Transfer8 KB
Monthly Cost€1/mo
Google Analytics
Analytics
Optional
Execution69ms
Transfer21 KB
Monthly Cost€1/mo
These scripts may cost more than they're worth
www.pinogalvagno.com adds 1739ms and costs ~€19/month
Google Tag Manager adds 335ms and costs ~€4/month
www.pinogalvagno.com adds 281ms and costs ~€3/month
90% 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.pinogalvagno.com takes 1739ms 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 335ms 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
57% 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.
Source: web.dev
www.pinogalvagno.com takes 281ms 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.