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
Asset Compression
Action
1 of 2 asset hosts serve text uncompressed
REVIEW
1 of 2 asset hosts serve text uncompressed
Warning::
!
fonts.googleapis.com serves text assets uncompressed (assets: 4)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Got: fonts.googleapis.com (text/css)
Info::
i
cdn.chatbot.com serves assets with gzip; brotli would be ~20% smaller (assets: 3)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: cdn.chatbot.com (text/javascript)
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
Third-Party Impact
28% third-party, 0 ms blocking
PASS
28% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 28% of page weight (755.0 KiB of 2.6 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
72%
28%
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
5 fonts (197 KB)
PASS
5 fonts (197 KB)
Info::
i
5 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
5
197 KB total
Render-blocking
0
of 5
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
8vIQ7wUr0m80wwYf0QCXZzY...woff2swap
Size30 KB
Load time42 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
fa-brands-400.woff2woff2swap
Size116 KB
Load time57 ms
Start1.2 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-regular-400.woff2woff2swap
Size26 KB
Load time52 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
source-sans-pro-v14-lat...woff2swap
Size0 KB
Load time-1665 ms
Start1.7 s
RiskFOUT — text flashes from fallback to web font
source-sans-pro-v14-lat...woff2swap
Size26 KB
Load time22 ms
Start2.3 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 ~58 KB and ~116 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+
Main HTML Cache-Control
Main HTML uses no-store -- correct for sensitive/dynamic content
PASS
Main HTML uses no-store -- correct for sensitive/dynamic content
Info::
✓
Main HTML uses no-store -- correct for sensitive/dynamic content
Got: no-cache, no-store
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::
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
66 requests over 2666ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
5%of JavaScript execution is third-party
First-party Third-party60ms · 92KB · $1/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
OneTrust
cdn.cookielaw.org
Consent
60ms
92 KB
53%
$1/mo
Essential
OneTrust
Consent
Essential
Execution60ms
Transfer92 KB
Unused53%
Monthly Cost$1/mo
53% of OneTrust'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.