cash.app speed test — 20 Oct 2026

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

https://cash.app/

20 October 2026 at 15:41 UTC · Free test · report pt_a05dd00b19dd

Re-test this page Test your own site

Grade

90/100

Performance96/100

Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)337 msmeasured from this server

Fully loaded1.42 sfirst byte + slowest asset

Requests26document + assets

Page weight769.0 KBcompressed transfer

HTML document275.6 KBgzip

ProtocolHTTP/3cloudflare

Third-party493.4 KBother hosts

Where the first byte went

DNS lookup 70 ms 21%
TCP connect 55 ms 16%
Server wait 212 ms 63%

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

Page weightheavier than 55% of 4,999 pages tested here769.0 KB against a median of 650.3 KB

Fully loadedfaster than 76% of 4,999 pages tested here1.42 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 337 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 769.0 KB over 26 request(s). 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.
64% 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.32 s, inside the 2.5 s Google calls good.
The main thread was blocked for 174 ms in total, which is not enough to feel.

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 cash.app — **Mobile** 390 × 844 · 42.5 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.32 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time174 mslong tasks during load

First contentful paint1.32 sfirst content on screen

Browser page weight15.04 MB130 request(s), scripts included

Failed requests9blocked or unreachable

Largest contentful paint1.32 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time174 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 19 requests

405.0 KB 53%

Images 6 requests

88.4 KB 11%

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

Top issues

Render-blocking resources

high impact

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

Third-party weight

medium impact

1 third-party host(s) serve 493.4 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.

HTML document size

medium impact

The document transfers 275.6 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.