zuimeitianqi.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:18 UTC. Grade E (53/100), with the screenshots, the timings and the fixes that matter.

https://zuimeitianqi.com/

20 October 2026 at 14:18 UTC · Free test · report pt_de34d0f1d8b2
Grade
E
53/100
Performance47/100
Structure61/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.68 smeasured from this server
Fully loaded4.13 sfirst byte + slowest asset
Requests7document + assets
Page weight1.79 MBcompressed transfer
HTML document826 Bno compression
ProtocolHTTP/2elb
Third-party201.1 KBother hosts

Where the first byte went

  • DNS lookup 62 ms 4%
  • TCP connect 226 ms 13%
  • Server wait 1.39 s 83%

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 96% of 4,999 pages tested here1.68 s against a median of 448 ms
Page weightheavier than 78% of 4,999 pages tested here1.79 MB against a median of 650.3 KB
Fully loadedslower than 88% of 4,999 pages tested here4.13 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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.68 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.79 MB over 7 request(s), which is lean. Javascript files are 79% 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.
  • The largest element took 14.26 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout stayed still (CLS 0.062), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 65 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.

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 paint14.26 sgood is under 2.5 s
Cumulative layout shift0.062under 0.1 is stable
Total blocking time65 mslong tasks during load
First contentful paint13.30 sfirst content on screen
Browser page weight3.54 MB32 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint14.26 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.062
Goodgood under 0.1, poor over 0.25
Total blocking time65 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 3 requests
1.41 MB 79%
Css 2 requests
382.6 KB 21%
Images 1 request
4.2 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1675 ms. Of that, 1387 ms was the server thinking and 288 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.

Compress text responses

high impact

5 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 1.78 MB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Total page weight

high impact

The page transfers 1.79 MB across 7 request(s), with the document itself at 826 B.

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

Cache static assets

medium impact

5 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

JavaScript weight

medium impact

2 JavaScript file(s) over 200 KB: chunk-vendors.fdf8ed9a.js (1.19 MB), adsbygoogle.js (201.1 KB)

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

Waterfall

Slowest requests

CSSzuimeitianqi.com/static/css/chunk-vendors.a3978605.css
2.45 s
JAVASCRIPTzuimeitianqi.com/static/js/chunk-vendors.fdf8ed9a.js
1.68 s
IMAGESzuimeitianqi.com/favicon.ico
1.33 s
JAVASCRIPTzuimeitianqi.com/static/js/app.e609dfbf.js
1.05 s
CSSzuimeitianqi.com/static/css/app.89edb5a1.css
895 ms
JAVASCRIPTpagead2.googlesyndication.com/pagead/js/adsbygoogle.js
224 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://zuimeitianqi.com/static/css/chunk-vendors.a3978605.csscss2002.45 s342.8 KB
https://zuimeitianqi.com/static/js/chunk-vendors.fdf8ed9a.jsjavascript2001.68 s1.19 MB
https://zuimeitianqi.com/favicon.icoimages2001.33 s4.2 KB
https://zuimeitianqi.com/static/js/app.e609dfbf.jsjavascript2001.05 s26.9 KB
https://zuimeitianqi.com/static/css/app.89edb5a1.csscss200895 ms39.8 KB
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-4801782203237916 3rd partyjavascript200224 ms201.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.