Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
C
Image Optimization
Action
32 images, 0 KB saveable
REVIEW
32 images, 0 KB saveable
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/defe... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2024/04/paja... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/fore... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2024/04/ph_l... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2024/04/ph_y... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/the_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2024/06/WSJ_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/news... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/04/ai-a... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/fina... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/dece... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/mit_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/reut... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/04/airf... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/04/air-... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/05/cnbc... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://bavovna.ai/wp-content/uploads/2026/04/seaw... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
32images11.3 MB
0oversized-0 KB
29legacy format
17missing 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
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
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
No Cache-Control header on main HTML response
REVIEW
No Cache-Control header on main HTML response
Info::
i
Main HTML response has no Cache-Control header
Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.
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.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 JS blocking issue(s) detected
Warning::
!
2 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 11.2 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
9% third-party, 0 ms blocking
PASS
9% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 9% of page weight (1.2 MiB of 13.8 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
91%
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
2 fonts (28 KB)
PASS
2 fonts (28 KB)
Info::
i
2 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
2
28 KB total
Render-blocking
0
of 2
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
S6uyw4BMUTPHjx4wXiWtFCc...woff2swap
Size14 KB
Load time9 ms
Start1.2 s
RiskFOUT — text flashes from fallback to web font
S6u9w4BMUTPHh6UVSwiPGQ3...woff2swap
Size14 KB
Load time19 ms
Start1.2 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
3 hints, 0 missing preconnects
PASS
3 hints, 0 missing preconnects
Info::
✓
Page uses 3 resource hint(s)
Current Resource Hints
preconnect
2
preload—
dns-prefetch
1
prefetch—
3 resource hints configured
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 3 asset hosts still on gzip
PASS
1 of 3 asset hosts still on gzip
Info::
✓
cdnjs.cloudflare.com serves assets with brotli (assets: 4)
Got: cdnjs.cloudflare.com (text/css)
Info::
i
www.googletagmanager.com serves assets with gzip; brotli would be ~20% smaller (assets: 4)
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.
cdn.jsdelivr.net serves assets with brotli (assets: 3)
Got: cdn.jsdelivr.net (text/css)
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::
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.
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.
Network Waterfall
90 requests over 3812ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
52%of JavaScript execution is third-party
First-party Third-party5797ms · 1218KB · €63/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
jsDelivr
cdn.jsdelivr.net
CDN
1785ms
43 KB
58%
€19/mo
Costly
Microsoft Clarity
scripts.clarity.ms
Session Replay
1008ms
25 KB
—
€11/mo
Costly
www.gstatic.com
www.gstatic.com
Other
918ms
346 KB
71%
€10/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
588ms
187 KB
41%
€6/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
517ms
160 KB
39%
€6/mo
Costly
cdnjs
cdnjs.cloudflare.com
CDN
316ms
27 KB
—
€3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
228ms
119 KB
57%
€2/mo
Costly
accounts.google.com
accounts.google.com
Other
142ms
99 KB
83%
€2/mo
Optional
Google Tag Manager
www.googletagmanager.com
Tag Manager
96ms
160 KB
71%
€1/mo
Optional
sc.lfeeder.com
sc.lfeeder.com
Other
81ms
12 KB
—
€1/mo
Optional
cdnjs
cdnjs.cloudflare.com
CDN
59ms
17 KB
—
€1/mo
Optional
LinkedIn Insight
snap.licdn.com
Advertising
58ms
21 KB
—
€1/mo
Optional
jsDelivr
CDN
Costly
Execution1785ms
Transfer43 KB
Unused58%
Monthly Cost€19/mo
Microsoft Clarity
Session Replay
Costly
Execution1008ms
Transfer25 KB
Monthly Cost€11/mo
www.gstatic.com
Other
Costly
Execution918ms
Transfer346 KB
Unused71%
Monthly Cost€10/mo
Google Tag Manager
Tag Manager
Costly
Execution588ms
Transfer187 KB
Unused41%
Monthly Cost€6/mo
Google Tag Manager
Tag Manager
Costly
Execution517ms
Transfer160 KB
Unused39%
Monthly Cost€6/mo
cdnjs
CDN
Costly
Execution316ms
Transfer27 KB
Monthly Cost€3/mo
Google Tag Manager
Tag Manager
Costly
Execution228ms
Transfer119 KB
Unused57%
Monthly Cost€2/mo
accounts.google.com
Other
Optional
Execution142ms
Transfer99 KB
Unused83%
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Optional
Execution96ms
Transfer160 KB
Unused71%
Monthly Cost€1/mo
sc.lfeeder.com
Other
Optional
Execution81ms
Transfer12 KB
Monthly Cost€1/mo
cdnjs
CDN
Optional
Execution59ms
Transfer17 KB
Monthly Cost€1/mo
LinkedIn Insight
Advertising
Optional
Execution58ms
Transfer21 KB
Monthly Cost€1/mo
These scripts may cost more than they're worth
jsDelivr adds 1785ms and costs ~€19/month
Microsoft Clarity adds 1008ms and costs ~€11/month
www.gstatic.com adds 918ms and costs ~€10/month
Google Tag Manager adds 588ms and costs ~€6/month
Google Tag Manager adds 517ms and costs ~€6/month
cdnjs adds 316ms and costs ~€3/month
Google Tag Manager adds 228ms and costs ~€2/month
52% 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
jsDelivr takes 1785ms 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
58% of jsDelivr'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.
Source: web.dev
Microsoft Clarity takes 1008ms 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
www.gstatic.com takes 918ms 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
71% of www.gstatic.com'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.
Source: web.dev
Google Tag Manager takes 588ms 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 517ms 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
cdnjs takes 316ms 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 228ms 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
57% of Google Tag Manager'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.
Source: web.dev
83% of accounts.google.com'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.
Source: web.dev
71% of Google Tag Manager'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.