centurylink.net speed test — 20 Oct 2026

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

https://centurylink.net/

20 October 2026 at 14:55 UTC · Free test · report pt_41bfa7804595
Grade
A
96/100
Performance97/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)314 msmeasured from this server
Fully loaded759 msfirst byte + slowest asset
Requests7document + assets
Page weight25.8 KBcompressed transfer
HTML document3.3 KBgzip
ProtocolHTTP/3nginx
Third-party22.5 KBother hosts

Where the first byte went

  • DNS lookup 55 ms 18%
  • TCP connect 68 ms 22%
  • Server wait 191 ms 61%

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 71% of 4,999 pages tested here314 ms against a median of 449 ms
Page weightlighter than 93% of 4,999 pages tested here25.8 KB against a median of 650.5 KB
Fully loadedfaster than 95% of 4,999 pages tested here759 ms against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 314 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 25.8 KB over 7 request(s), which is lean. Javascript files are 53% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 87% 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.65 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.010), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 436 ms, so taps and scrolling wait while scripts run.

Fix first: Third-party weight - Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.

Mobile screenshot of centurylink.net
Mobile 390 × 844 · 53.1 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.65 sgood is under 2.5 s
Cumulative layout shift0.010under 0.1 is stable
Total blocking time436 mslong tasks during load
First contentful paint1.05 sfirst content on screen
Browser page weight3.76 MB189 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint1.65 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.010
Goodgood under 0.1, poor over 0.25
Total blocking time436 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
13.6 KB 53%
Images 2 requests
6.6 KB 25%
Css 1 request
2.2 KB 9%
Html 2 requests
92 B 0%

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

Top issues

Third-party weight

low impact

5 third-party host(s) serve 22.5 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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

HTMLudmserve.net/udm/img.fetch
445 ms
HTMLwww.googletagmanager.com/ns.html
405 ms
IMAGESportal-static.imds-cdn.com/images/centurylink-gen4/icons/apple-to…
381 ms
IMAGESportal-static.imds-cdn.com/images/centurylink-gen4/icons/favicon.ico
361 ms
CSStesseract.imds-cdn.com/centurylink.tesseract.css
324 ms
JAVASCRIPTcdn.cookielaw.org/scripttemplates/otSDKStub.js
296 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://udmserve.net/udm/img.fetch?sid=21516;tid=1;dt=8; 3rd partyhtml302445 ms0 B
https://www.googletagmanager.com/ns.html?id=GTM-NMSSCCBP 3rd partyhtml200405 ms92 B
https://portal-static.imds-cdn.com/images/centurylink-gen4/icons/apple-touch-icon-180.png 3rd partyimages200381 ms3.9 KB
https://portal-static.imds-cdn.com/images/centurylink-gen4/icons/favicon.ico 3rd partyimages200361 ms2.6 KB
https://tesseract.imds-cdn.com/centurylink.tesseract.css 3rd partycss200324 ms2.2 KB
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js 3rd partyjavascript200296 ms13.6 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.