www.google.com.nf speed test — 20 Oct 2026

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

https://www.google.com.nf/

20 October 2026 at 15:01 UTC · Free test · report pt_41e1caf7d7d7
Grade
A
95/100
Performance97/100
Structure92/100

13 audit(s) passed, 3 need work

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

Where the first byte went

  • DNS lookup 85 ms 26%
  • TCP connect 48 ms 15%
  • Server wait 195 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 69% of 4,999 pages tested here329 ms against a median of 449 ms
Page weightlighter than 91% of 4,999 pages tested here44.6 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here711 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.

What these numbers mean

  • The first byte arrived in 329 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 44.6 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 680 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 116 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.

Screenshot

What the page looks like

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

Desktop screenshot of www.google.com.nf
Desktop 1366 × 768 · 34.2 KB · page is 768 px tall
Mobile screenshot of www.google.com.nf
Mobile 390 × 844 · 13.0 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 paint680 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time116 mslong tasks during load
First contentful paint680 msfirst content on screen
Browser page weight991.2 KB33 request(s), scripts included
Failed requests3blocked or unreachable
Largest contentful paint680 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time116 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.6 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

CSSwww.google.com.nf/xjs/_/ss/k=xjs.hp.2MyD3oTtWh0.L.X.O/am…
382 ms
IMAGESwww.google.com.nf/images/branding/google_wordmark/v1/1x/…
379 ms
HTMLwww.google.com.nf/a
352 ms
IMAGESwww.google.com.nf/images/nav_logo229.png
320 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.nf/xjs/_/ss/k=xjs.hp.2MyD3oTtWh0.L.X.O/am=AAABAAAAAAAAAAABAAAAAAAAAAAAAAgAAAAAAAAAAAAEACBAABIAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAEAIAQgAAAAAAAAAAAAAAAAAAAAAEAECQAAQAAQAAAAAAAgAAAAAAAD/d=1/ed=1/rs=ACT90oE6p_8DuDmBf9wXT3DFyrzrgu9NDg/m=sb_he,d?cb=121990236css200382 ms0 B
https://www.google.com.nf/images/branding/google_wordmark/v1/1x/googlelogo_color_white_background_272x92dp.pngimages200379 ms2.4 KB
https://www.google.com.nf/ahtml404352 ms1.5 KB
https://www.google.com.nf/images/nav_logo229.pngimages200320 ms12.0 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.