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.
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.
C
Main HTML Cache-Control
Action
Main HTML max-age=7200 (~120min) is aggressive
REVIEW
Main HTML max-age=7200 (~120min) is aggressive
Warning::
!
Main HTML cached for 120 minutes -- risks stale auth / SPA state
Long max-age on the main HTML document means users may see outdated auth state, SPA shells, or A/B variants until the cache expires. Consider Cache-Control: no-cache (or max-age=300) for HTML and let your hashed assets (JS/CSS/images) carry the long cache instead.
Got: max-age=7200
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.
13 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 4.7 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
REVIEW
Green Hosting
No green hosting detected
A+
Third-Party Impact
12% third-party, 0 ms blocking
PASS
12% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 12% of page weight (213.4 KiB of 1.8 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
88%
First-party Third-party
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 (302 KB)
PASS
3 fonts (302 KB)
Info::
i
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
302 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
fa-brands-400.woff2woff2swap
Size115 KB
Load time161 ms
Start5.7 s
RiskFOUT — text flashes from fallback to web font
Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
fa-solid-900.woff2woff2swap
Size153 KB
Load time166 ms
Start5.7 s
RiskFOUT — text flashes from fallback to web font
Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
JTUSjIg1_i6t8kCHKm459Wl...woff2swap
Size35 KB
Load time23 ms
Start5.7 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 ~134 KB and ~268 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
8 hints, 0 missing preconnects
PASS
8 hints, 0 missing preconnects
Info::
i
2 dns-prefetch redundant with preconnect on same origin
preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://www.googletagmanager.com, https://fonts.googleapis.com. Remove the redundant dns-prefetch entries.
Info::
✓
Page uses 8 resource hint(s)
Current Resource Hints
preconnect
3
preload
2
dns-prefetch
3
prefetch—
8 resource hints configured
preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://www.googletagmanager.com, https://fonts.googleapis.com. Remove the redundant dns-prefetch entries.
Why this matters
Performance issues directly impact user engagement and conversion rates.
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
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::
✓
`Last-Modified` present -- timestamp-based conditional GET supported
Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.
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+
HTTP Caching
max-age=7200 (2 hours)
PASS
max-age=7200 (2 hours)
Info::
✓
Cache-Control header is set
Got: max-age=7200
Info::
✓
Effective TTL: 2 hours (max-age=7200)
Info::
✓
Last-Modified header present
Cache-Control
max-age=7200
Directive
Value
Meaning
max-age
7200
Cache for 2 hours
Effective TTL: 7200 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
66 requests over 12745ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
9%of JavaScript execution is third-party
First-party Third-party445ms · 177KB · MX$33/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Google Tag Manager
www.googletagmanager.com
Tag Manager
445ms
177 KB
41%
MX$33/mo
Costly
Google Tag Manager
Tag Manager
Costly
Execution445ms
Transfer177 KB
Unused41%
Monthly CostMX$33/mo
These scripts may cost more than they're worth
Google Tag Manager adds 445ms and costs ~MX$33/month
Google Tag Manager takes 445ms 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.