Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.10 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.74 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.28 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
1.76 s
Page Load Progression
375 ms
750 ms
1.1 s
1.5 s
1.9 s
2.2 s
2.6 s
3.0 s
Checks
23
11 PASS7 REVIEW1 FIX
D
Page Weight Budget
Action
2.1 MB transferred, 72 requests
FIX
2.1 MB transferred, 72 requests
Info::
i
Page weighs 3.4 MB (2.1 MB transferred)
Info::
i
Fonts are 563 KB — consider subsetting or using system fonts
Subset fonts to include only used characters, or switch to system font stacks.
Got: 563 KB
Info::
i
72 HTTP requests
Info::
i
Estimated 0.45 g CO2 per page load
2.1 MBtransferred
72 requests
0.45 g CO2 per page load
Images982.6 KiB45%
Fonts563.5 KiB26%
Other464.6 KiB21%
HTML126.1 KiB6%
CSS39.3 KiB2%
Other537 B0%
JavaScript-1 B-0%
02.4 MB4.9 MB
Approaching limit
Subset fonts to include only used characters, or switch to system font stacks.
Why this matters
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
B
JS Execution Cost
558ms total JS execution
REVIEW
558ms total JS execution
Warning::
!
https://nnnig.com/: 469ms CPU time
Info::
i
Unattributable: 89ms CPU time
Main Thread Breakdown
Style & Layout 48% Other 31% Parse HTML & CSS 8% Script Evaluation 7% Rendering 5%
Script
Total
Scripting
Parse/Compile
Party
https://nnnig.com/
469ms
34ms
7ms
1st
Unattributable
89ms
2ms
0ms
1st
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=2592000 (~43200min) is aggressive
REVIEW
Main HTML max-age=2592000 (~43200min) is aggressive
Warning::
!
Main HTML cached for 43200 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=2592000
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.
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+
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=2592000 (4 weeks)
PASS
max-age=2592000 (4 weeks)
Info::
✓
Cache-Control header is set
Got: max-age=2592000
Info::
✓
Effective TTL: 4 weeks (max-age=2592000)
Info::
✓
Last-Modified header present
Cache-Control
max-age=2592000
Directive
Value
Meaning
max-age
2592000
Cache for 4 weeks
Effective TTL: 2592000 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
72 requests over 1699ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Real-User Performance (CrUX)
Field metrics from the Chrome User Experience Report
INFO
Chrome User Experience (CrUX)
Real-user metrics from the Chrome UX Report (2026-09-24 — 2026-10-21)
LCP (p75)
2009 ms
81% good
INP (p75)
0 ms
0% good
CLS (p75)
0.020
81% good
FCP (p75)
1428 ms
TTFB (p75)
1219 ms
Image Optimization
22 images, 247 KB total, 0 KB wasted
INFO
Image Optimization Audit
Total Images
22
Total Size
247 KB
2 missing alt text7 missing dimensions10 missing lazy loading
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.
375 ms
1.5 s