replit.com speed test — 20 Oct 2026

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

https://replit.com/

20 October 2026 at 13:41 UTC · Free test · report pt_b2aa684978c2

Re-test this page Test your own site

Grade

97/100

Performance99/100

Structure95/100

15 audit(s) passed, 1 need work

First byte (TTFB)182 msmeasured from this server

Fully loaded1.82 sfirst byte + slowest asset

Requests26document + assets

Page weight405.8 KBcompressed transfer

HTML document80.7 KBbr

ProtocolHTTP/3cloudflare

Third-party36.7 KBother hosts

Where the first byte went

DNS lookup 62 ms 34%
TCP connect 28 ms 15%
Server wait 92 ms 51%

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

Page weightlighter than 65% of 4,999 pages tested here405.8 KB against a median of 650.5 KB

Fully loadedfaster than 51% of 4,999 pages tested here1.82 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 server answered in 182 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 405.8 KB over 26 request(s). Images files are 71% 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 700 ms, 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 2.35 s, so taps and scrolling wait while scripts run.

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.

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 paint700 msgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time2.35 slong tasks during load

First contentful paint700 msfirst content on screen

Browser page weight5.96 MB232 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint700 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time2.35 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 14 requests

288.4 KB 71%

Javascript 5 requests

36.7 KB 9%

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

Top issues

Render-blocking resources

high impact

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