co.com speed test — 20 Oct 2026

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

https://co.com/

20 October 2026 at 13:14 UTC · Free test · report pt_7d97d9ff379c

Re-test this page Test your own site

Grade

95/100

Performance95/100

Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)373 msmeasured from this server

Fully loaded373 msfirst byte + slowest asset

Requests1document + assets

Page weight255 Bcompressed transfer

HTML document255 Bno compression

ProtocolHTTP/2Apache

Where the first byte went

DNS lookup 101 ms 27%
TCP connect 78 ms 21%
Server wait 195 ms 52%

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 61% of 4,999 pages tested here373 ms against a median of 449 ms

Page weightlighter than 99% of 4,999 pages tested here255 B against a median of 650.5 KB

Fully loadedfaster than 99% of 4,999 pages tested here373 ms against a median of 1.84 s

Requestssends fewer requests than 98% of 4,999 pages tested here1 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 373 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 255 B over 1 request(s), which is lean.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 380 ms, inside the 2.5 s Google calls good.

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

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 co.com — **Desktop** 1366 × 768 · 12.8 KB · page is 768 px tall

Mobile screenshot of co.com — **Mobile** 390 × 844 · 5.1 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 paint380 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint380 msfirst content on screen

Browser page weight255 B1 request(s), scripts included

Largest contentful paint380 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking timenone over 50 ms

Goodgood under 200 ms, poor over 600 ms

Top issues

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.

Report this page

Run this test on your own site

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

Run a website speed test Have it fixed