blog.google speed test — 20 Oct 2026

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

https://blog.google/

20 October 2026 at 13:03 UTC · Free test · report pt_1a7421fa45fe
Grade
A
91/100
Performance93/100
Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)450 msmeasured from this server
Fully loaded1.02 sfirst byte + slowest asset
Requests11document + assets
Page weight289.5 KBcompressed transfer
HTML document68.2 KBgzip
ProtocolHTTP/3Google Frontend
Third-party134.9 KBother hosts

Where the first byte went

  • DNS lookup 74 ms 16%
  • TCP connect 59 ms 13%
  • Server wait 317 ms 70%

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 50% of 4,999 pages tested here450 ms against a median of 448 ms
Page weightlighter than 73% of 4,999 pages tested here289.5 KB against a median of 650.5 KB
Fully loadedfaster than 92% of 4,999 pages tested here1.02 s against a median of 1.84 s
Requestssends fewer requests than 87% of 4,999 pages tested here11 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 450 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 289.5 KB over 11 request(s), which is lean. Other files are 46% of it, so that one type is worth a look on its own.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 47% 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.43 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.013), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 17 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.

Desktop screenshot of blog.google
Desktop 1366 × 768 · 832.6 KB · page is 6000 px tall
Mobile screenshot of blog.google
Mobile 390 × 844 · 235.5 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.43 sgood is under 2.5 s
Cumulative layout shift0.013under 0.1 is stable
Total blocking time17 mslong tasks during load
First contentful paint528 msfirst content on screen
Browser page weight20.48 MB63 request(s), scripts included
Largest contentful paint1.43 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.013
Goodgood under 0.1, poor over 0.25
Total blocking time17 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Other 3 requests
132.7 KB 46%
Css 3 requests
78.7 KB 27%
Images 3 requests
9.9 KB 3%
Html 1 request
92 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 450 ms. Of that, 317 ms was the server thinking and 133 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

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

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

CSSwww.gstatic.com/glue/cookienotificationbar/cookienotif…
572 ms
CSSblog.google/static/keyword/css/blog/index.min.css
481 ms
CSSfonts.googleapis.com/css
461 ms
OTHERstorage.googleapis.com/gweb-uniblog-publish-prod/images/IRD_2…
438 ms
OTHERstorage.googleapis.com/gweb-uniblog-publish-prod/images/When_…
438 ms
IMAGESblog.google/static/blogv2/images/apple-touch-icon.png
438 ms
IMAGESblog.google/static/blogv2/images/super-g-aurora.svg
438 ms
HTMLwww.googletagmanager.com/ns.html
438 ms
OTHERstorage.googleapis.com/gweb-uniblog-publish-prod/images/Synth…
400 ms
IMAGESblog.google/static/blogv2/images/favicon.ico
400 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.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.css 3rd partycss200572 ms1.7 KB
https://blog.google/static/keyword/css/blog/index.min.css?version=pr20261009-1701css200481 ms76.5 KB
https://fonts.googleapis.com/css?family=Google+Sans:400,500,600,700|Google+Sans+Flex:400,500|Product+Sans:400&display=swap&lang=en 3rd partycss200461 ms501 B
https://storage.googleapis.com/gweb-uniblog-publish-prod/images/IRD_2026.2e16d0ba.fill-1200x800.format-webp.webp 3rd partyother200438 ms36.1 KB
https://storage.googleapis.com/gweb-uniblog-publish-prod/images/When_to_buy_guide_re.2e16d0ba.fill-1200x800.format-webp.webp 3rd partyother200438 ms28.7 KB
https://blog.google/static/blogv2/images/apple-touch-icon.png?version=pr20261009-1701images200438 ms4.0 KB
https://blog.google/static/blogv2/images/super-g-aurora.svg?version=pr20261009-1701images200438 ms2.5 KB
https://www.googletagmanager.com/ns.html?id=GTM-TRV24V 3rd partyhtml200438 ms92 B
https://storage.googleapis.com/gweb-uniblog-publish-prod/images/SynthID_Detector_her.2e16d0ba.fill-1200x800.format-webp_TDwLvt4.webp 3rd partyother200400 ms67.9 KB
https://blog.google/static/blogv2/images/favicon.ico?version=pr20261009-1701images200400 ms3.5 KB
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.