unstop.com speed test — 20 Oct 2026

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

https://unstop.com/

20 October 2026 at 16:11 UTC · Free test · report pt_f3c103ec7284

Re-test this page Test your own site

Grade

87/100

Performance82/100

Structure95/100

15 audit(s) passed, 1 need work

First byte (TTFB)786 msmeasured from this server

Fully loaded2.10 sfirst byte + slowest asset

Requests19document + assets

Page weight293.3 KBcompressed transfer

HTML document9.0 KBgzip

ProtocolHTTP/3CloudFront

Third-party114.1 KBother hosts

Where the first byte went

DNS lookup 96 ms 12%
TCP connect 47 ms 6%
Server wait 643 ms 82%

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

Page weightlighter than 72% of 4,999 pages tested here293.3 KB against a median of 650.5 KB

Fully loadedslower than 61% of 4,999 pages tested here2.10 s against a median of 1.84 s

Requestssends fewer requests than 80% of 4,999 pages tested here19 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 786 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 293.3 KB over 19 request(s). Javascript files are 41% 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.
39% 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 2.43 s, inside the 2.5 s Google calls good.
The main thread was blocked for 290 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 unstop.com — **Mobile** 390 × 844 · 160.8 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 paint2.43 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time290 mslong tasks during load

First contentful paint968 msfirst content on screen

Browser page weight3.11 MB342 request(s), scripts included

Failed requests8blocked or unreachable

Largest contentful paint2.43 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time290 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 3 requests

121.5 KB 41%

Other 3 requests

95.9 KB 33%

Css 1 request

48.3 KB 16%

Images 10 requests

18.4 KB 6%

Html 1 request

246 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 786 ms. Of that, 643 ms was the server thinking and 143 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.