www.dingtalk.com speed test — 20 Oct 2026

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

https://www.dingtalk.com/

20 October 2026 at 13:40 UTC · Free test · report pt_cc50c74ace3b
Grade
D
62/100
Performance58/100
Structure68/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.54 smeasured from this server
Fully loaded2.37 sfirst byte + slowest asset
Requests9document + assets
Page weight1.36 MBcompressed transfer
HTML document12.2 KBgzip
ProtocolHTTP/3Tengine
Third-party1.35 MBother hosts

Where the first byte went

  • DNS lookup 287 ms 19%
  • TCP connect 102 ms 7%
  • Server wait 1.15 s 75%

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 95% of 4,999 pages tested here1.54 s against a median of 448 ms
Page weightheavier than 72% of 4,999 pages tested here1.36 MB against a median of 650.3 KB
Fully loadedslower than 70% of 4,999 pages tested here2.37 s against a median of 1.84 s
Requestssends fewer requests than 89% of 4,999 pages tested here9 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 1.54 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 1.36 MB over 9 request(s), which is lean. Images files are 99% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, 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.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 7 requests
1.35 MB 99%

Transfer size, compressed as sent. 9 request(s) in total, 1.36 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1536 ms. Of that, 1147 ms was the server thinking and 389 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 1 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.

Total page weight

medium impact

The page transfers 1.36 MB across 9 request(s), with the document itself at 12.2 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

3 third-party host(s) serve 1.35 MB 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.

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

OTHERcloud.video.taobao.com/vod/mzXJgRjKVuYzW2JFpImr3DYGNzXY8MUlqO…
831 ms
IMAGESimg.alicdn.com/imgextra/i1/O1CN01XYPcGH5UOcK5tJVk_!!6…
469 ms
IMAGESgw.alicdn.com/imgextra/i1/O1CN01YqGsfb1vyR0W4LhPU_!!…
397 ms
IMAGESgw.alicdn.com/imgextra/i4/O1CN01usckxw1kOHyZ5rtA6_!!…
309 ms
IMAGESgw.alicdn.com/imgextra/i1/O1CN013k4bzn1Gqk6xZzlQ5_!!…
301 ms
IMAGESgw.alicdn.com/imgextra/i3/O1CN01yWKrO61tIddDmGTPV_!!…
300 ms
IMAGESgw.alicdn.com/imgextra/i3/O1CN014ZbI6ZTEhdC0ttN2_!!6…
295 ms
IMAGESgw.alicdn.com/imgextra/i2/O1CN01t9bxoW1GsZhLmjGVy_!!…
295 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://cloud.video.taobao.com/vod/mzXJgRjKVuYzW2JFpImr3DYGNzXY8MUlqOAhG91zO_I.mp4 3rd partyother302831 ms0 B
https://img.alicdn.com/imgextra/i1/O1CN01XYPcGH5UOcK5tJVk_!!6000000000850-2-tps-2902-1822.png 3rd partyimages200469 ms1.31 MB
https://gw.alicdn.com/imgextra/i1/O1CN01YqGsfb1vyR0W4LhPU_!!6000000006241-55-tps-16-16.svg 3rd partyimages200397 ms570 B
https://gw.alicdn.com/imgextra/i4/O1CN01usckxw1kOHyZ5rtA6_!!6000000004673-55-tps-16-16.svg 3rd partyimages200309 ms566 B
https://gw.alicdn.com/imgextra/i1/O1CN013k4bzn1Gqk6xZzlQ5_!!6000000000674-49-tps-240-240.webp 3rd partyimages200301 ms24.0 KB
https://gw.alicdn.com/imgextra/i3/O1CN01yWKrO61tIddDmGTPV_!!6000000005879-55-tps-91-27.svg 3rd partyimages200300 ms1.2 KB
https://gw.alicdn.com/imgextra/i3/O1CN014ZbI6ZTEhdC0ttN2_!!6000000003783-2-tps-444-444.png 3rd partyimages200295 ms11.2 KB
https://gw.alicdn.com/imgextra/i2/O1CN01t9bxoW1GsZhLmjGVy_!!6000000000678-55-tps-24-24.svg 3rd partyimages200295 ms860 B
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.