www.digitalocean.com speed test — 20 Oct 2026

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

https://www.digitalocean.com/

20 October 2026 at 12:25 UTC · Free test · report pt_2c0747493100

Re-test this page Test your own site

Grade

96/100

Performance100/100

Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)109 msmeasured from this server

Fully loaded1.21 sfirst byte + slowest asset

Requests26document + assets

Page weight40.6 KBcompressed transfer

HTML document40.6 KBgzip

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 64 ms 59%
TCP connect 1 ms 1%
Server wait 44 ms 40%

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

Page weightlighter than 92% of 4,999 pages tested here40.6 KB against a median of 650.5 KB

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

Requestssends more requests than 100% of 4,999 pages tested here26 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 server answered in 109 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 40.6 KB over 26 request(s).
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 520 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 243 ms, so taps and scrolling wait while scripts run.

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.

Mobile screenshot of www.digitalocean.com — **Mobile** 390 × 844 · 103.0 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 paint520 msgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time243 mslong tasks during load

First contentful paint412 msfirst content on screen

Browser page weight2.47 MB179 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint520 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time243 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

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

Top issues

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (1 script(s), 4 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.

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.

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.