robinhood.com/us/en speed test — 20 Oct 2026

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

https://robinhood.com/us/en/

20 October 2026 at 13:23 UTC · Free test · report pt_00c3edc6c90c

Re-test this page Test your own site

Grade

67/100

Performance68/100

Structure65/100

9 audit(s) passed, 7 need work

First byte (TTFB)404 msmeasured from this server

Fully loaded1.84 sfirst byte + slowest asset

Requests26document + assets

Page weight12.43 MBcompressed transfer

HTML document45.3 KBgzip

ProtocolHTTP/3envoy

Third-party12.39 MBother hosts

Where the first byte went

DNS lookup 73 ms 18%
TCP connect 39 ms 10%
Server wait 292 ms 72%

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

Page weightheavier than 98% of 4,999 pages tested here12.43 MB against a median of 650.3 KB

Fully loadedfaster than 50% of 4,999 pages tested here1.84 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 arrived in 404 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 12.43 MB over 26 request(s). Media files are 58% of it, so let video load on demand instead of on first paint.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 3.82 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 330 ms, so taps and scrolling wait while scripts run.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of robinhood.com — **Desktop** 1366 × 768 · 240.0 KB · page is 6000 px tall

Mobile screenshot of robinhood.com — **Mobile** 390 × 844 · 151.7 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 paint3.82 sgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time330 mslong tasks during load

First contentful paint3.32 sfirst content on screen

Browser page weight10.46 MB47 request(s), scripts included

Largest contentful paint3.82 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time330 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Media 2 requests

7.25 MB 58%

Images 11 requests

3.27 MB 26%

Javascript 12 requests

1.86 MB 15%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 404 ms. Of that, 292 ms was the server thinking and 112 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.

Compress text responses

high impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 60.0 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Image delivery and format

high impact

5 image(s) over 200 KB and 5 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 12.43 MB across 26 request(s), with the document itself at 45.3 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

3 third-party host(s) serve 12.39 MB 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.