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
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
Main HTML Cache-Control
Main HTML max-age=3600 (~60min)
REVIEW
Main HTML max-age=3600 (~60min)
Info::
i
Main HTML cached for 60 minutes -- mild staleness risk
Got: max-age=3600
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
Page Weight Budget
924 KB transferred, 34 requests
PASS
924 KB transferred, 34 requests
Info::
✓
Page weighs 1.6 MB (924 KB transferred)
Info::
✓
34 HTTP requests
Info::
i
Estimated 0.19 g CO2 per page load
924 KBtransferred
34 requests
0.19 g CO2 per page load
Images352.2 KiB38%
JavaScript325.0 KiB35%
Fonts186.5 KiB20%
CSS35.6 KiB4%
HTML16.2 KiB2%
Other6.4 KiB1%
Other695 B0%
Other568 B0%
Other477 B0%
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
5 fonts (186 KB)
PASS
5 fonts (186 KB)
Info::
i
5 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
5
186 KB total
Render-blocking
0
of 5
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
CircularStd-Bold.woff2woff2swap
Size29 KB
Load time304 ms
Start292 ms
RiskFOUT — text flashes from fallback to web font
CircularStd-Medium.woff2woff2swap
Size28 KB
Load time355 ms
Start292 ms
RiskFOUT — text flashes from fallback to web font
CircularStd-Book.woff2woff2swap
Size25 KB
Load time296 ms
Start292 ms
RiskFOUT — text flashes from fallback to web font
CircularStd-Black.woff2woff2swap
Size29 KB
Load time270 ms
Start293 ms
RiskFOUT — text flashes from fallback to web font
fontawesome-webfont.woff2woff2swap
Size76 KB
Load time244 ms
Start405 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)
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
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::
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.
No render-blocking JS or document.write usage detected
PASS
No render-blocking JS or document.write usage detected
Info::
✓
No JavaScript blocking issues detected
A+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
✓
No CSS performance depth issues detected
A
HTTP Caching
max-age=3600 (1 hour)
PASS
max-age=3600 (1 hour)
Info::
✓
Cache-Control header is set
Got: max-age=3600
Info::
✓
Effective TTL: 1 hour (max-age=3600)
Info::
i
No ETag or Last-Modified header
Conditional requests (304 Not Modified) are not possible without validators.
Cache-Control
max-age=3600
Directive
Value
Meaning
max-age
3600
Cache for 1 hour
Effective TTL: 3600 seconds
Asset Compression
No text asset hosts to measure
INFO
No text asset hosts to measure
Info::
i
No third-party or subdomain host served enough text assets to measure
Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.
Network Waterfall
34 requests over 2590ms
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-party882ms · 341KB · £9/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.fayesdoggyboutique.co.uk
www.fayesdoggyboutique.co.uk
Other
378ms
16 KB
—
£4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
326ms
197 KB
40%
£3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
178ms
128 KB
51%
£2/mo
Optional
www.fayesdoggyboutique.co.uk
Other
Costly
Execution378ms
Transfer16 KB
Monthly Cost£4/mo
Google Tag Manager
Tag Manager
Costly
Execution326ms
Transfer197 KB
Unused40%
Monthly Cost£3/mo
Google Tag Manager
Tag Manager
Optional
Execution178ms
Transfer128 KB
Unused51%
Monthly Cost£2/mo
These scripts may cost more than they're worth
www.fayesdoggyboutique.co.uk adds 378ms and costs ~£4/month
Google Tag Manager adds 326ms and costs ~£3/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.fayesdoggyboutique.co.uk takes 378ms 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 326ms 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 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.