www.google.com speed test — 20 Oct 2026

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

A newer test of this page exists: 20 Oct 2026, grade A (96/100). This older result is kept for comparison.

https://www.google.com/

20 October 2026 at 12:26 UTC · Free test · report pt_05e75611703a
Grade
A
97/100
Performance100/100
Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)206 msmeasured from this server
Fully loaded456 msfirst byte + slowest asset
Requests5document + assets
Page weight44.3 KBcompressed transfer
HTML document28.4 KBgzip
ProtocolHTTP/3gws

Where the first byte went

  • DNS lookup 48 ms 23%
  • TCP connect 27 ms 13%
  • Server wait 130 ms 63%

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 92% of 4,999 pages tested here206 ms against a median of 449 ms
Page weightlighter than 92% of 4,999 pages tested here44.3 KB against a median of 650.5 KB
Fully loadedfaster than 98% of 4,999 pages tested here456 ms against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 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.

Score history

4 tests of this URL, oldest to newest: 93 → 97 → 95 → 96 out of 100. The top line is a perfect score.

What these numbers mean

  • The first byte arrived in 206 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 44.3 KB over 5 request(s), which is lean. Images files are 32% 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.
  • The largest element painted at 908 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 72 ms in total, which is not enough to feel.

Fix first: Avoid extra redirects - Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

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.

Since the test on 20 Oct 2026

MetricThenNowChange
Grade93/10097/100better
Performance95/100100/100better
Structure91/10092/100better
First byte387 ms206 msbetter
Fully loaded672 ms456 msbetter
Page weight44.4 KB44.3 KBbetter
Largest contentful paint608 ms908 msworse
Total blocking time96 ms72 msbetter

Both runs came from this server, so the difference is the page, not the network in between. Open the earlier report.

Screenshot

What the page looks like

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

Mobile screenshot of www.google.com
Mobile 390 × 844 · 11.4 KB · page is 2121 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 paint908 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time72 mslong tasks during load
First contentful paint528 msfirst content on screen
Browser page weight1.00 MB44 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint908 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time72 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 2 requests
14.4 KB 32%
Html 1 request
1.5 KB 3%

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

Top issues

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESwww.google.com/images/nav_logo229.png
250 ms
HTMLwww.google.com/a
229 ms
CSSwww.google.com/xjs/_/ss/k=xjs.hp.2MyD3oTtWh0.L.X.O/am…
201 ms
IMAGESwww.google.com/images/branding/google_wordmark/v1/1x/…
192 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.google.com/images/nav_logo229.pngimages200250 ms12.0 KB
https://www.google.com/ahtml404229 ms1.5 KB
https://www.google.com/xjs/_/ss/k=xjs.hp.2MyD3oTtWh0.L.X.O/am=AAABAAAAAAAAAAABAAAAAAAAAAAAAAgAAAAAAAAAAAAEACBAABIAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAEAIAQgAAAAAAAAAAAAAAAAAAAAAEAECQAAQAAQAAAAAAAgAAAAAAAD/d=1/ed=1/rs=ACT90oE6p_8DuDmBf9wXT3DFyrzrgu9NDg/m=sb_he,d?cb=121990236css200201 ms0 B
https://www.google.com/images/branding/google_wordmark/v1/1x/googlelogo_color_white_background_272x92dp.pngimages200192 ms2.4 KB

Earlier tests of www.google.com

All reports for www.google.com

Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.