www.sumup.com/en-us speed test — 20 Oct 2026

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

https://www.sumup.com/en-us/

20 October 2026 at 14:06 UTC · Free test · report pt_5e2e36ca9d2f

Re-test this page Test your own site

Grade

72/100

Performance65/100

Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)836 msmeasured from this server

Fully loaded6.23 sfirst byte + slowest asset

Requests26document + assets

Page weight130.9 KBcompressed transfer

HTML document130.9 KBgzip

ProtocolHTTP/3cloudflare

Third-party35 Bother hosts

Where the first byte went

DNS lookup 78 ms 9%
TCP connect 23 ms 3%
Server wait 735 ms 88%

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 77% of 4,999 pages tested here836 ms against a median of 448 ms

Page weightlighter than 85% of 4,999 pages tested here130.9 KB against a median of 650.5 KB

Fully loadedslower than 96% of 4,999 pages tested here6.23 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 836 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 130.9 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 1.10 s, inside the 2.5 s Google calls good.
The main thread was blocked for 679 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 www.sumup.com — **Desktop** 1366 × 768 · 647.6 KB · page is 6000 px tall

Mobile screenshot of www.sumup.com — **Mobile** 390 × 844 · 190.4 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.10 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time679 mslong tasks during load

First contentful paint1.10 sfirst content on screen

Browser page weight3.98 MB117 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint1.10 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time679 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request

35 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 836 ms. Of that, 735 ms was the server thinking and 101 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

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