www.icloud.com speed test — 20 Oct 2026

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

https://www.icloud.com/

20 October 2026 at 12:30 UTC · Free test · report pt_6a2357f61d9e
Grade
A
97/100
Performance99/100
Structure95/100

14 audit(s) passed, 2 need work

First byte (TTFB)237 msmeasured from this server
Fully loaded693 msfirst byte + slowest asset
Requests7document + assets
Page weight816.8 KBcompressed transfer
HTML document9.6 KBbr
ProtocolHTTP/3AppleHttpServer/07719a852974

Where the first byte went

  • DNS lookup 52 ms 22%
  • TCP connect 33 ms 14%
  • Server wait 152 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 87% of 4,999 pages tested here237 ms against a median of 449 ms
Page weightheavier than 57% of 4,999 pages tested here816.8 KB against a median of 650.3 KB
Fully loadedfaster than 96% of 4,999 pages tested here693 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 237 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 816.8 KB over 7 request(s), which is lean. Javascript files are 92% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 628 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 197 ms in total, which is not enough to feel.

Fix first: JavaScript weight - Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.icloud.com
Mobile 390 × 844 · 80.4 KB · page is 844 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 paint628 msgood is under 2.5 s
Cumulative layout shift0.003under 0.1 is stable
Total blocking time197 mslong tasks during load
First contentful paint260 msfirst content on screen
Browser page weight3.54 MB26 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint628 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.003
Goodgood under 0.1, poor over 0.25
Total blocking time197 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
752.7 KB 92%
Css 1 request
47.1 KB 6%
Images 1 request
3.9 KB 0%
Html 3 requests
3.5 KB 0%

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

Top issues

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: main.js (752.7 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.

Waterfall

Slowest requests

HTMLwww.icloud.com/favicons/default-favicon-light-32x32.png
456 ms
HTMLwww.icloud.com/image/webp
408 ms
HTMLwww.icloud.com/favicons/default-favicon-light-180x180…
380 ms
IMAGESwww.icloud.com/favicon.ico
372 ms
JAVASCRIPTwww.icloud.com/system/icloud.com/2638Build27/en-us/ma…
351 ms
CSSwww.icloud.com/system/icloud.com/2638Build27/en-us/ma…
343 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://www.icloud.com/favicons/default-favicon-light-32x32.pnghtml404456 ms1.2 KB
https://www.icloud.com/image/webphtml404408 ms1.2 KB
https://www.icloud.com/favicons/default-favicon-light-180x180.pnghtml404380 ms1.2 KB
https://www.icloud.com/favicon.icoimages200372 ms3.9 KB
https://www.icloud.com/system/icloud.com/2638Build27/en-us/main.jsjavascript200351 ms752.7 KB
https://www.icloud.com/system/icloud.com/2638Build27/en-us/main.csscss200343 ms47.1 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.