g.co speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:28 UTC. Grade A (97/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 62 ms 26%
- TCP connect 31 ms 13%
- Server wait 140 ms 60%
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
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 234 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 23.1 KB over 6 request(s), which is lean. Css files are 53% of it, so split the stylesheet so the first screen does not download the whole site.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- 91% 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 404 ms, inside the 2.5 s Google calls good.
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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 6 request(s) in total, 23.1 KB across all of them.
Top issues
Render-blocking resources
high impact3 render-blocking resource(s) in the document head (1 script(s), 2 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.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://www.google.com/js/gweb/analytics/autotrack.js 3rd party | javascript | 200 | 375 ms | 1.9 KB |
| https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700|Product+Sans:400&subset=latin 3rd party | css | 200 | 297 ms | 328 B |
| https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_116x41dp.png 3rd party | images | 200 | 294 ms | 2.4 KB |
| https://www.google.com/css/maia.css 3rd party | css | 200 | 289 ms | 11.9 KB |
| https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_116x41dp.png 3rd party | images | 200 | 230 ms | 4.5 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.