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
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
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
362 KB transferred, 31 requests
PASS
362 KB transferred, 31 requests
Info::
✓
Page weighs 1.2 MB (362 KB transferred)
Info::
✓
31 HTTP requests
Info::
i
Estimated 0.07 g CO2 per page load
362 KBtransferred
31 requests
0.07 g CO2 per page load
JavaScript202.1 KiB56%
HTML81.5 KiB23%
Fonts41.3 KiB11%
Other15.9 KiB4%
Images13.2 KiB4%
Other4.1 KiB1%
Other1.8 KiB0%
Other1.1 KiB0%
Other967 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+
JS Execution Cost
291ms total JS execution
PASS
291ms total JS execution
Info::
i
https://yandex.com/: 174ms CPU time
Info::
i
https://yastatic.net/react/19.2.4/react-with-dom.m...: 60ms CPU time
1 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
1
41 KB total
Render-blocking
0
of 1
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
text-regular.woff2woff2swap
Size41 KB
Load time46 ms
Start450 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+
Document Compression
Document response uses brotli
PASS
Document response uses brotli
Info::
✓
Main HTML response uses brotli (Content-Encoding: br)
Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.
A+
Asset Compression
All 1 asset host use brotli
PASS
All 1 asset host use brotli
Info::
✓
yastatic.net serves assets with brotli (assets: 12)
Got: yastatic.net (application/javascript)
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
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.