data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOUA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAFAA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOUA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOUA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAANEA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADcA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAANAA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJAA... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
14images2.6 MB
0oversized-0 KB
3legacy format
8missing dimensionsCLS risk
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
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, must-revalidate
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
35% third-party, 0 ms blocking
PASS
35% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 35% of page weight (1.4 MiB of 4.1 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
65%
35%
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
6 fonts (135 KB)
PASS
6 fonts (135 KB)
Info::
i
6 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
6
135 KB total
Render-blocking
0
of 6
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
co3smX5slCNuHLi8bLeY9MK...woff2swap
Size23 KB
Load time20 ms
Start706 ms
RiskFOUT — text flashes from fallback to web font
co3umX5slCNuHLi8bLeY9MK...woff2swap
Size22 KB
Load time28 ms
Start707 ms
RiskFOUT — text flashes from fallback to web font
gyByhwUxId8gMEwcGFWNOIT...woff2swap
Size29 KB
Load time28 ms
Start708 ms
RiskFOUT — text flashes from fallback to web font
jizBRFtNs2ka5fXjeivQ4Lr...woff2swap
Size15 KB
Load time18 ms
Start2.3 s
RiskFOUT — text flashes from fallback to web font
tDbv2o-flEEny0FZhsfKu5W...woff2swap
Size31 KB
Load time23 ms
Start2.3 s
RiskFOUT — text flashes from fallback to web font
jizHRFtNs2ka5fXjeivQ4Lr...woff2swap
Size15 KB
Load time26 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)
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+
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
1 of 1 asset host still on gzip
PASS
1 of 1 asset host still on gzip
Info::
i
unpkg.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: unpkg.com (text/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+
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.
A+
HTTP Caching
max-age=3600 (1 hour)
PASS
max-age=3600 (1 hour)
Info::
✓
Cache-Control header is set
Got: max-age=3600, must-revalidate
Info::
✓
Effective TTL: 1 hour (max-age=3600)
Info::
✓
Last-Modified header present
Cache-Control
max-age=3600, must-revalidate
Directive
Value
Meaning
max-age
3600
Cache for 1 hour
must-revalidate
—
Must recheck with server after expiry
Effective TTL: 3600 seconds
Network Waterfall
50 requests over 3599ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
62%of JavaScript execution is third-party
First-party Third-party1923ms · 1178KB · $26/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
unpkg
unpkg.com
CDN
1128ms
640 KB
49%
$15/mo
Costly
Tawk.to
embed.tawk.to
Chat
242ms
118 KB
39%
$3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
229ms
164 KB
37%
$3/mo
Costly
unpkg
unpkg.com
CDN
189ms
228 KB
46%
$3/mo
Optional
unpkg
unpkg.com
CDN
136ms
28 KB
—
$2/mo
Optional
unpkg
CDN
Costly
Execution1128ms
Transfer640 KB
Unused49%
Monthly Cost$15/mo
Tawk.to
Chat
Costly
Execution242ms
Transfer118 KB
Unused39%
Monthly Cost$3/mo
Google Tag Manager
Tag Manager
Costly
Execution229ms
Transfer164 KB
Unused37%
Monthly Cost$3/mo
unpkg
CDN
Optional
Execution189ms
Transfer228 KB
Unused46%
Monthly Cost$3/mo
unpkg
CDN
Optional
Execution136ms
Transfer28 KB
Monthly Cost$2/mo
These scripts may cost more than they're worth
unpkg adds 1128ms and costs ~$15/month
Tawk.to adds 242ms and costs ~$3/month
Google Tag Manager adds 229ms and costs ~$3/month
62% of JavaScript execution time comes from third-party scripts.
Why this matters
Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.
Learn more ▾▴
Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.
Source: web.dev / HTTP Archive Web Almanac
unpkg takes 1128ms 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
Tawk.to takes 242ms 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 229ms 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.