research.google speed test — 20 Oct 2026

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

https://research.google/

20 October 2026 at 15:52 UTC · Free test · report pt_01863d43ca3a

Re-test this page Test your own site

Grade

90/100

Performance92/100

Structure86/100

14 audit(s) passed, 2 need work

First byte (TTFB)481 msmeasured from this server

Fully loaded1.52 sfirst byte + slowest asset

Requests26document + assets

Page weight82.0 KBcompressed transfer

HTML document48.7 KBgzip

ProtocolHTTP/3Google Frontend

Third-party33.2 KBother hosts

Where the first byte went

DNS lookup 77 ms 16%
TCP connect 71 ms 15%
Server wait 333 ms 69%

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 byteslower than 53% of 4,999 pages tested here481 ms against a median of 448 ms

Page weightlighter than 89% of 4,999 pages tested here82.0 KB against a median of 650.5 KB

Fully loadedfaster than 69% of 4,999 pages tested here1.52 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 first byte arrived in 481 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 82.0 KB over 26 request(s). Images files are 41% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
41% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.98 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 118 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Mobile screenshot of research.google — **Mobile** 390 × 844 · 85.1 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.98 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time118 mslong tasks during load

First contentful paint920 msfirst content on screen

Browser page weight113.72 MB81 request(s), scripts included

Failed requests11blocked or unreachable

Largest contentful paint1.98 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time118 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

33.2 KB 41%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 481 ms. Of that, 333 ms was the server thinking and 148 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

7 render-blocking resource(s) in the document head (0 script(s), 7 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.