www.strava.com speed test — 20 Oct 2026

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

https://www.strava.com/

20 October 2026 at 13:01 UTC · Free test · report pt_fc2ebc7df83f

Re-test this page Test your own site

Grade

72/100

Performance64/100

Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)601 msmeasured from this server

Fully loaded10.75 sfirst byte + slowest asset

Requests26document + assets

Page weight282.1 KBcompressed transfer

HTML document154.3 KBgzip

ProtocolHTTP/3istio-envoy

Third-party127.7 KBother hosts

Where the first byte went

DNS lookup 90 ms 15%
TCP connect 32 ms 5%
Server wait 479 ms 80%

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 byteslower than 63% of 4,999 pages tested here601 ms against a median of 448 ms

Page weightlighter than 73% of 4,999 pages tested here282.1 KB against a median of 650.5 KB

Fully loadedslower than 99% of 4,999 pages tested here10.75 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 first byte took 601 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 282.1 KB over 26 request(s). Images files are 45% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
45% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 25 requests

127.7 KB 45%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 601 ms. Of that, 479 ms was the server thinking and 122 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

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

HTML document size

medium impact

The document transfers 154.3 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.