yoast.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:04 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.

https://yoast.com/

20 October 2026 at 15:04 UTC · Free test · report pt_f74318bd79ba

Re-test this page Test your own site

Grade

96/100

Performance100/100

Structure91/100

15 audit(s) passed, 1 need work

First byte (TTFB)194 msmeasured from this server

Fully loaded1.26 sfirst byte + slowest asset

Requests26document + assets

Page weight63.5 KBcompressed transfer

HTML document46.4 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 54 ms 28%
TCP connect 26 ms 13%
Server wait 114 ms 59%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 93% of 4,999 pages tested here194 ms against a median of 449 ms

Page weightlighter than 90% of 4,999 pages tested here63.5 KB against a median of 650.5 KB

Fully loadedfaster than 85% of 4,999 pages tested here1.26 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The server answered in 194 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 63.5 KB over 26 request(s).
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.26 s, inside the 2.5 s Google calls good.
Layout shift is 0.209 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 187 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of yoast.com — **Desktop** 1366 × 768 · 403.1 KB · page is 6000 px tall

Mobile screenshot of yoast.com — **Mobile** 390 × 844 · 141.4 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.26 sgood is under 2.5 s

Cumulative layout shift0.209under 0.1 is stable

Total blocking time187 mslong tasks during load

First contentful paint520 msfirst content on screen

Browser page weight1.72 MB93 request(s), scripts included

Largest contentful paint1.26 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.209

Needs improvementgood under 0.1, poor over 0.25

Total blocking time187 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

17.1 KB 27%

Transfer size, compressed as sent. 26 request(s) in total, 63.5 KB across all of them.

Top issues

Render-blocking resources

high impact

16 render-blocking resource(s) in the document head (2 script(s), 14 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.