www.cox.com/residential/home.html speed test — 20 Oct 2026

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

https://www.cox.com/residential/home.html

20 October 2026 at 13:58 UTC · Free test · report pt_841d651766ae

Re-test this page Test your own site

Grade

96/100

Performance96/100

Structure95/100

14 audit(s) passed, 2 need work

First byte (TTFB)350 msmeasured from this server

Fully loaded1.36 sfirst byte + slowest asset

Requests15document + assets

Page weight327.9 KBcompressed transfer

HTML document30.3 KBgzip

ProtocolHTTP/3CloudFront

Third-party73.0 KBother hosts

Where the first byte went

DNS lookup 66 ms 19%
TCP connect 61 ms 17%
Server wait 224 ms 64%

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

Page weightlighter than 70% of 4,999 pages tested here327.9 KB against a median of 650.5 KB

Fully loadedfaster than 80% of 4,999 pages tested here1.36 s against a median of 1.84 s

Requestssends fewer requests than 83% of 4,999 pages tested here15 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 350 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 327.9 KB over 15 request(s), which is lean. Html files are 68% 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.
22% 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 2.16 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 230 ms, so taps and scrolling wait while scripts run.

Fix first: Cache static assets - Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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

Mobile screenshot of www.cox.com — **Mobile** 390 × 844 · 43.6 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 paint2.16 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time230 mslong tasks during load

First contentful paint784 msfirst content on screen

Browser page weight1.11 MB110 request(s), scripts included

Largest contentful paint2.16 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time230 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 8 requests

224.6 KB 68%

Fonts 2 requests

55.1 KB 17%

Images 3 requests

17.9 KB 5%

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

Top issues

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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.