amplitude.com speed test — 20 Oct 2026

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

https://amplitude.com/

20 October 2026 at 12:36 UTC · Free test · report pt_6bffcc923394

Re-test this page Test your own site

Grade

84/100

Performance86/100

Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)668 msmeasured from this server

Fully loaded1.80 sfirst byte + slowest asset

Requests26document + assets

Page weight811.4 KBcompressed transfer

HTML document53.6 KBbr

ProtocolHTTP/3nginx/1.22.0

Third-party1.5 KBother hosts

Where the first byte went

DNS lookup 74 ms 11%
TCP connect 66 ms 10%
Server wait 528 ms 79%

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

Page weightheavier than 57% of 4,999 pages tested here811.4 KB against a median of 650.3 KB

Fully loadedfaster than 52% of 4,999 pages tested here1.80 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 668 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 811.4 KB over 26 request(s). Images files are 93% of it, so resize and recompress the largest images before anything else.
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 1.16 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 304 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.

Mobile screenshot of amplitude.com — **Mobile** 390 × 844 · 48.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.16 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time304 mslong tasks during load

First contentful paint892 msfirst content on screen

Browser page weight4.47 MB259 request(s), scripts included

Failed requests7blocked or unreachable

Largest contentful paint1.16 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time304 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

757.8 KB 93%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 668 ms. Of that, 528 ms was the server thinking and 140 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.

Image delivery and format

high impact

1 image(s) over 200 KB and 0 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.

Render-blocking resources

high impact

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