bj.58.com speed test — 20 Oct 2026

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

https://bj.58.com/

20 October 2026 at 14:09 UTC · Free test · report pt_da95a1b10f4c
Grade
B
81/100
Performance83/100
Structure77/100

10 audit(s) passed, 6 need work

First byte (TTFB)819 msmeasured from this server
Fully loaded1.29 sfirst byte + slowest asset
Requests9document + assets
Page weight103.5 KBcompressed transfer
HTML document21.6 KBgzip
ProtocolHTTP/3Tengine
Third-party82.0 KBother hosts

Where the first byte went

  • DNS lookup 71 ms 9%
  • TCP connect 234 ms 29%
  • Server wait 514 ms 63%

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 77% of 4,999 pages tested here819 ms against a median of 448 ms
Page weightlighter than 87% of 4,999 pages tested here103.5 KB against a median of 650.5 KB
Fully loadedfaster than 84% of 4,999 pages tested here1.29 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 819 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 103.5 KB over 9 request(s), which is lean. Images files are 64% 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.
  • 79% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 6.88 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.014), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 513 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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of bj.58.com
Mobile 390 × 844 · 160.2 KB · page is 2576 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 paint6.88 sgood is under 2.5 s
Cumulative layout shift0.014under 0.1 is stable
Total blocking time513 mslong tasks during load
First contentful paint2.01 sfirst content on screen
Browser page weight1.94 MB117 request(s), scripts included
Largest contentful paint6.88 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.014
Goodgood under 0.1, poor over 0.25
Total blocking time513 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 3 requests
66.3 KB 64%
Css 3 requests
11.5 KB 11%
Javascript 2 requests
4.2 KB 4%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 819 ms. Of that, 514 ms was the server thinking and 305 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

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

Cache static assets

medium impact

4 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.

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.

Mobile viewport

medium impact

No 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.

Waterfall

Slowest requests

JAVASCRIPTj1.58cdn.com.cn/git/wuxianfe/pc-static/js/v7/hp/loadA_…
468 ms
IMAGESimg.58cdn.com.cn/logo/58/168_60/logo-wo.png
433 ms
IMAGESimg.58cdn.com.cn/logo/58/252_84/logo-o.png
423 ms
CSSc.58cdn.com.cn/ui7/css/easydialog.css
421 ms
CSSc.58cdn.com.cn/git/wuxianfe/pc-static/css/homePage_v2…
419 ms
CSSc.58cdn.com.cn/componentsLoader/dist/CompontsLoader_v…
419 ms
JAVASCRIPTj1.58cdn.com.cn/componentsLoader/dist/ComponentsLoader…
368 ms
IMAGESimg.58cdn.com.cn/ui6/index/daojia_hot_icon.png
351 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://j1.58cdn.com.cn/git/wuxianfe/pc-static/js/v7/hp/loadA_v20261012093615.js?_newtime=20261012 3rd partyjavascript200468 ms871 B
https://img.58cdn.com.cn/logo/58/168_60/logo-wo.png 3rd partyimages200433 ms4.2 KB
https://img.58cdn.com.cn/logo/58/252_84/logo-o.png?v=2 3rd partyimages200423 ms4.7 KB
https://c.58cdn.com.cn/ui7/css/easydialog.css 3rd partycss200421 ms660 B
https://c.58cdn.com.cn/git/wuxianfe/pc-static/css/homePage_v20261012093615.css?_newtime=20261012 3rd partycss200419 ms7.5 KB
https://c.58cdn.com.cn/componentsLoader/dist/CompontsLoader_v20260106110154.css?v=20170427144100 3rd partycss200419 ms3.4 KB
https://j1.58cdn.com.cn/componentsLoader/dist/ComponentsLoader_v20260106110154.js 3rd partyjavascript200368 ms3.3 KB
https://img.58cdn.com.cn/ui6/index/daojia_hot_icon.png 3rd partyimages200351 ms57.4 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.