JavaScript is 941 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 941 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
99 HTTP requests
Info::
i
Estimated 0.32 g CO2 per page load
1.5 MBtransferred
99 requests
0.32 g CO2 per page load
JavaScript940.7 KiB61%
Fonts234.7 KiB15%
Images173.9 KiB11%
CSS102.5 KiB7%
HTML55.5 KiB4%
Other22.5 KiB1%
Other11.4 KiB1%
Other8.3 KiB1%
Other1.0 KiB0%
Other476 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
B
Image Optimization
22 images, 0 KB saveable
REVIEW
22 images, 0 KB saveable
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.
22images174 KB
0oversized-0 KB
11legacy format
1missing 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
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.
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::
!
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.6 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 time86 ms
Start70 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-Italic.woff2woff2swap
Size61 KB
Load time76 ms
Start71 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-SemiBold.woff2woff2swap
Size58 KB
Load time81 ms
Start71 ms
RiskFOUT — text flashes from fallback to web font
OpenSans-Bold.woff2woff2swap
Size57 KB
Load time61 ms
Start71 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+
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
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Cloudflare
Network Waterfall
99 requests over 1662ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
72%of JavaScript execution is third-party
First-party Third-party3269ms · 756KB · €17/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Unattributable
Unattributable
Other
848ms
0 KB
—
€4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
782ms
183 KB
37%
€4/mo
Costly
cdn-4.convertexperiments.com
cdn-4.convertexperiments.com
Other
713ms
105 KB
55%
€4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
320ms
170 KB
51%
€2/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
218ms
144 KB
57%
€1/mo
Costly
OneTrust
cdn.cookielaw.org
Consent
162ms
124 KB
62%
€1/mo
Essential
widget.trustpilot.com
widget.trustpilot.com
Other
114ms
8 KB
—
€1/mo
Optional
beacon-v2.helpscout.net
beacon-v2.helpscout.net
Other
61ms
13 KB
—
€0/mo
Optional
mbyoastbv.activehosted.com
mbyoastbv.activehosted.com
Other
50ms
10 KB
—
€0/mo
Optional
Unattributable
Other
Costly
Execution848ms
Transfer0 KB
Monthly Cost€4/mo
Google Tag Manager
Tag Manager
Costly
Execution782ms
Transfer183 KB
Unused37%
Monthly Cost€4/mo
cdn-4.convertexperiments.com
Other
Costly
Execution713ms
Transfer105 KB
Unused55%
Monthly Cost€4/mo
Google Tag Manager
Tag Manager
Costly
Execution320ms
Transfer170 KB
Unused51%
Monthly Cost€2/mo
Google Tag Manager
Tag Manager
Costly
Execution218ms
Transfer144 KB
Unused57%
Monthly Cost€1/mo
OneTrust
Consent
Essential
Execution162ms
Transfer124 KB
Unused62%
Monthly Cost€1/mo
widget.trustpilot.com
Other
Optional
Execution114ms
Transfer8 KB
Monthly Cost€1/mo
beacon-v2.helpscout.net
Other
Optional
Execution61ms
Transfer13 KB
Monthly Cost€0/mo
mbyoastbv.activehosted.com
Other
Optional
Execution50ms
Transfer10 KB
Monthly Cost€0/mo
These scripts may cost more than they're worth
Unattributable adds 848ms and costs ~€4/month
Google Tag Manager adds 782ms and costs ~€4/month
cdn-4.convertexperiments.com adds 713ms and costs ~€4/month
Google Tag Manager adds 320ms and costs ~€2/month
Google Tag Manager adds 218ms and costs ~€1/month
72% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
Why this matters
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev
Unattributable takes 848ms 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 782ms 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 713ms 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
Google Tag Manager takes 320ms 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 218ms 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
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.