www.alipay.com speed test — 20 Oct 2026

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

https://www.alipay.com/

20 October 2026 at 12:39 UTC · Free test · report pt_a056047f1ff3
Grade
B
80/100
Performance85/100
Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)571 msmeasured from this server
Fully loaded2.82 sfirst byte + slowest asset
Requests15document + assets
Page weight628.3 KBcompressed transfer
HTML document6.7 KBno compression
ProtocolHTTP/2Tengine
Third-party621.7 KBother hosts

Where the first byte went

  • DNS lookup 272 ms 48%
  • TCP connect 74 ms 13%
  • Server wait 224 ms 39%

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 60% of 4,999 pages tested here571 ms against a median of 448 ms
Page weightlighter than 51% of 4,999 pages tested here628.3 KB against a median of 650.5 KB
Fully loadedslower than 79% of 4,999 pages tested here2.82 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 571 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 628.3 KB over 15 request(s), which is lean. Javascript files are 91% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The main thread was blocked for 43 ms in total, which is not enough to feel.

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 www.alipay.com
Mobile 390 × 844 · 2.7 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 paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time43 mslong tasks during load
First contentful paintnot reportedfirst content on screen
Browser page weight590.9 KB15 request(s), scripts included
Largest contentful paintnot reported
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time43 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 10 requests
573.0 KB 91%
Images 2 requests
45.9 KB 7%
Css 2 requests
2.8 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 571 ms. Of that, 224 ms was the server thinking and 346 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

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

Third-party weight

medium impact

4 third-party host(s) serve 621.7 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: umi.6adf1493.js (218.8 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.

Waterfall

Slowest requests

JAVASCRIPTgw.alipayobjects.com/os/lib/jquery/3.7.1/dist/jquery.min.js
2.25 s
JAVASCRIPTgw.alipayobjects.com/render/p/yuyan/180020010001278576/lib-…
2.19 s
JAVASCRIPTgw.alipayobjects.com/os/lib/history/5.3.0/umd/history.produ…
2.07 s
CSSgw.alipayobjects.com/render/p/yuyan/180020010001278576/a10a…
1.74 s
JAVASCRIPTgw.alipayobjects.com/render/p/yuyan/180020010001278576/fram…
1.63 s
JAVASCRIPTgw.alipayobjects.com/os/lib/moment/2.30.1/min/moment-with-l…
1.30 s
JAVASCRIPTgw.alipayobjects.com/render/p/yuyan/180020010001278576/umi.…
752 ms
IMAGESmdn.alipayobjects.com/rms/afts/file/A*7EyORZxdNDkAAAAAAAAAAA…
693 ms
CSSgw.alipayobjects.com/render/p/yuyan/180020010001278576/umi.…
682 ms
IMAGESimg.alicdn.com/tfs/TB1qEwuzrj1gK0jSZFOXXc7GpXa-32-32.ico
681 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://gw.alipayobjects.com/os/lib/jquery/3.7.1/dist/jquery.min.js 3rd partyjavascript2002.25 s29.7 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/lib-async.17f7f058.js 3rd partyjavascript2002.19 s8.5 KB
https://gw.alipayobjects.com/os/lib/history/5.3.0/umd/history.production.min.js 3rd partyjavascript2002.07 s2.0 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/a10a3151-async.efe93249.css 3rd partycss2001.74 s1.6 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/framework.0bdc944f.js 3rd partyjavascript2001.63 s51.0 KB
https://gw.alipayobjects.com/os/lib/moment/2.30.1/min/moment-with-locales.min.js 3rd partyjavascript2001.30 s74.7 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/umi.6adf1493.js 3rd partyjavascript200752 ms218.8 KB
https://mdn.alipayobjects.com/rms/afts/file/A*7EyORZxdNDkAAAAAAAAAAAAAARQnAQ 3rd partyimages200693 ms41.7 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/umi.9734f39a.css 3rd partycss200682 ms1.2 KB
https://img.alicdn.com/tfs/TB1qEwuzrj1gK0jSZFOXXc7GpXa-32-32.ico 3rd partyimages200681 ms4.2 KB
https://gw.alipayobjects.com/render/p/yuyan/180020010001278576/a10a3151-async.d9e17fd4.js 3rd partyjavascript200666 ms10.1 KB
https://gw.alipayobjects.com/os/lib/lodash/4.18.1/lodash.min.js 3rd partyjavascript200662 ms25.3 KB
https://gw.alipayobjects.com/os/lib/dayjs/1.11.23/dayjs.min.js 3rd partyjavascript200661 ms3.0 KB
https://render-intl.alipayobjects.com/p/yuyan/180020010001265696/main-25d9ea75.js 3rd partyjavascript200646 ms150.1 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.