JavaScript is 940 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 940 KB
Info::
i
Fonts are 235 KB — consider subsetting or using system fonts
Subset fonts to include only used characters, or switch to system font stacks.
Got: 235 KB
Info::
i
100 HTTP requests
Info::
i
Estimated 0.32 g CO2 per page load
1.5 MBtransferred
100 requests
0.32 g CO2 per page load
JavaScript940.4 KiB60%
Fonts234.6 KiB15%
Images186.7 KiB12%
CSS103.7 KiB7%
HTML55.9 KiB4%
Other22.0 KiB1%
Other11.4 KiB1%
Other9.1 KiB1%
Other1.6 KiB0%
Other474 B0%
02.4 MB4.9 MB
Approaching limit
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Why this matters
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
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
C
Image Optimization
Action
23 images, 0 KB saveable
REVIEW
23 images, 0 KB saveable
Warning::
!
https://yoast.com/app/uploads/2023/03/support_usp_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://yoast.com/app/uploads/2023/03/technical_us... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://yoast.com/app/uploads/2023/03/content_usp_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://yoast.com/app/uploads/2025/04/yoast_logo_2... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://yoast.com/app/uploads/2023/03/results_usp_... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
23images187 KB
0oversized-0 KB
10legacy format
5missing 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
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
i
Main HTML response has no Content-Encoding (uncompressed)
The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.
C
Main HTML Cache-Control
Action
Main HTML max-age=57328 (~955min) is aggressive
REVIEW
Main HTML max-age=57328 (~955min) is aggressive
Warning::
!
Main HTML cached for 955 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.
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::
!
7 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 4.8 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.
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.
Info::
i
1 `@import` rule(s) in inline `<style>` blocks -- chains an extra round-trip
Each `@import` in CSS forces a serial dependency: the parent stylesheet must download and parse before the browser even knows which URL to fetch next. This used to be catastrophic on HTTP/1.1; HTTP/2 and HTTP/3 multiplexing make it less painful but still strictly worse than declaring `<link rel="stylesheet">` siblings. Replace `@import url(...)` with `<link rel="stylesheet" href="...">` in HTML so the browser discovers and fetches in parallel.
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
4 fonts (235 KB)
PASS
4 fonts (235 KB)
Info::
i
4 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
4
235 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
OpenSans-Regular.woff2woff2swap
Size58 KB
Load time62 ms
Start56 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-Italic.woff2woff2swap
Size61 KB
Load time64 ms
Start56 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-SemiBold.woff2woff2swap
Size58 KB
Load time69 ms
Start61 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-Bold.woff2woff2swap
Size57 KB
Load time60 ms
Start61 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
6 hints, 0 missing preconnects
PASS
6 hints, 0 missing preconnects
Warning::
!
4 font preload(s) missing `crossorigin` -- font will be downloaded twice
Fonts are always fetched as crossorigin=anonymous; a preload without the attribute creates a different cache key, so the browser refetches when the actual font request happens. Sample: https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-Regular.woff2, https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-Italic.woff2, https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-SemiBold.woff2 (+1 more). Add `crossorigin` (or `crossorigin="anonymous"`) to each preload.
Info::
✓
Page uses 6 resource hint(s)
Current Resource Hints
preconnect—
preload
4
dns-prefetch
2
prefetch—
6 resource hints configured
Fonts are always fetched as crossorigin=anonymous; a preload without the attribute creates a different cache key, so the browser refetches when the actual font request happens. Sample: https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-Regular.woff2, https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-Italic.woff2, https://yoast.com/app/themes/yoast-com/assets/fonts/OpenSansStatic/OpenSans-SemiBold.woff2 (+1 more). Add `crossorigin` (or `crossorigin="anonymous"`) to each preload.
Why this matters
Performance issues directly impact user engagement and conversion rates.
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+
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+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Per-script blocking time, transfer cost, and cache headers
INFO
64%of JavaScript execution is third-party
First-party Third-party3042ms · 756KB · €16/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Google Tag Manager
www.googletagmanager.com
Tag Manager
790ms
183 KB
37%
€4/mo
Costly
cdn-4.convertexperiments.com
cdn-4.convertexperiments.com
Other
693ms
105 KB
55%
€4/mo
Costly
Unattributable
Unattributable
Other
571ms
0 KB
—
€3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
347ms
171 KB
51%
€2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
262ms
144 KB
56%
€1/mo
Costly
OneTrust
cdn.cookielaw.org
Consent
182ms
124 KB
62%
€1/mo
Essential
widget.trustpilot.com
widget.trustpilot.com
Other
79ms
8 KB
—
€0/mo
Optional
beacon-v2.helpscout.net
beacon-v2.helpscout.net
Other
65ms
13 KB
—
€0/mo
Optional
OneTrust
cdn.cookielaw.org
Consent
53ms
9 KB
—
€0/mo
Essential
Google Tag Manager
Tag Manager
Costly
Execution790ms
Transfer183 KB
Unused37%
Monthly Cost€4/mo
cdn-4.convertexperiments.com
Other
Costly
Execution693ms
Transfer105 KB
Unused55%
Monthly Cost€4/mo
Unattributable
Other
Costly
Execution571ms
Transfer0 KB
Monthly Cost€3/mo
Google Tag Manager
Tag Manager
Costly
Execution347ms
Transfer171 KB
Unused51%
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Costly
Execution262ms
Transfer144 KB
Unused56%
Monthly Cost€1/mo
OneTrust
Consent
Essential
Execution182ms
Transfer124 KB
Unused62%
Monthly Cost€1/mo
widget.trustpilot.com
Other
Optional
Execution79ms
Transfer8 KB
Monthly Cost€0/mo
beacon-v2.helpscout.net
Other
Optional
Execution65ms
Transfer13 KB
Monthly Cost€0/mo
OneTrust
Consent
Essential
Execution53ms
Transfer9 KB
Monthly Cost€0/mo
These scripts may cost more than they're worth
Google Tag Manager adds 790ms and costs ~€4/month
cdn-4.convertexperiments.com adds 693ms and costs ~€4/month
Unattributable adds 571ms and costs ~€3/month
Google Tag Manager adds 347ms and costs ~€2/month
Google Tag Manager adds 262ms and costs ~€1/month
64% 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
Google Tag Manager takes 790ms 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
cdn-4.convertexperiments.com takes 693ms 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
55% of cdn-4.convertexperiments.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
Unattributable takes 571ms 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 347ms 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
51% 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
Google Tag Manager takes 262ms 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
56% 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
62% 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.