aliexpress.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:23 UTC. Grade B (80/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 58 ms 5%
- TCP connect 246 ms 23%
- Server wait 786 ms 72%
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
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 1.09 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
- The page transfers 843 B over 1 request(s), which is lean.
- 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.82 s, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.018), so nothing jumps under the reader's cursor.
- The main thread was blocked for 436 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.
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.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 1090 ms. Of that, 786 ms was the server thinking and 304 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.
Mobile viewport
medium impactNo viewport meta tag, so a phone renders the desktop layout scaled down.
Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.
Strict-Transport-Security
low impactHSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.
Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.