www.ifeng.com speed test — 20 Oct 2026

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

https://www.ifeng.com/

20 October 2026 at 13:17 UTC · Free test · report pt_eec45c391d79
Grade
B
83/100
Performance87/100
Structure77/100

9 audit(s) passed, 7 need work

First byte (TTFB)413 msmeasured from this server
Fully loaded3.47 sfirst byte + slowest asset
Requests25document + assets
Page weight446.5 KBcompressed transfer
HTML document79.5 KBgzip
ProtocolHTTP/2openresty/1.27.1.2
Third-party361.8 KBother hosts

Where the first byte went

  • DNS lookup 152 ms 37%
  • TCP connect 52 ms 13%
  • Server wait 209 ms 51%

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 bytefaster than 54% of 4,999 pages tested here413 ms against a median of 449 ms
Page weightlighter than 62% of 4,999 pages tested here446.5 KB against a median of 650.5 KB
Fully loadedslower than 86% of 4,999 pages tested here3.47 s against a median of 1.84 s
Requestssends fewer requests than 74% of 4,999 pages tested here25 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 arrived in 413 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 446.5 KB over 25 request(s). Javascript files are 48% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • 81% 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

Javascript 7 requests
213.5 KB 48%
Images 16 requests
144.1 KB 32%
Css 1 request
9.4 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 413 ms. Of that, 209 ms was the server thinking and 204 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 (2 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.

Cache static assets

medium impact

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

Third-party weight

medium impact

5 third-party host(s) serve 361.8 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.

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

IMAGESp0.ifengimg.com/ifeng/index/20150921/ifengLogo.png
3.05 s
IMAGESy0.ifengimg.com/index/favicon.ico
2.07 s
IMAGESy1.ifengimg.com/index/72x72_2520ifeng.png
2.06 s
IMAGESwww.ifeng.com/http%3A%2F%2Fp0.ifengimg.com%2Fa%2F201…
1.60 s
IMAGESx0.ifengimg.com/ucms/2023_13/BD45EC3BD0E4E602FB97E9999…
1.48 s
IMAGESx0.ifengimg.com/ucms/2021_51/BF272305A6C6DA0B63CECBF04…
1.47 s
IMAGESx0.ifengimg.com/ucms/2022_42/2E489749A84FE79BC08DE4E96…
1.47 s
IMAGESx0.ifengimg.com/ucms/2020_52/50257546363BACF93320824F9…
1.47 s
IMAGESx0.ifengimg.com/ucms/2020_52/05C1B236228FC0496C7073E3C…
1.47 s
IMAGESx0.ifengimg.com/ucms/2024_32/547B3B502317AF80C8443F561…
1.47 s

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://p0.ifengimg.com/ifeng/index/20150921/ifengLogo.png 3rd partyimages2003.05 s9.5 KB
https://y0.ifengimg.com/index/favicon.ico 3rd partyimages2002.07 s3.9 KB
https://y1.ifengimg.com/index/72x72_2520ifeng.png 3rd partyimages2002.06 s3.5 KB
https://www.ifeng.com/http%3A%2F%2Fp0.ifengimg.com%2Fa%2F2016%2F0121%2Fghs.jpgimages2001.60 s5.1 KB
https://x0.ifengimg.com/ucms/2023_13/BD45EC3BD0E4E602FB97E9999E73B9C93A225A68_size15_w240_h40.jpg 3rd partyimages2001.48 s8.9 KB
https://x0.ifengimg.com/ucms/2021_51/BF272305A6C6DA0B63CECBF0460A5B4B001345E3_size1_w22_h24.png 3rd partyimages2001.47 s727 B
https://x0.ifengimg.com/ucms/2022_42/2E489749A84FE79BC08DE4E96911DF5582BCF05C_size16_w240_h40.jpg 3rd partyimages2001.47 s9.4 KB
https://x0.ifengimg.com/ucms/2020_52/50257546363BACF93320824F924F8FA41D53F209_size16_w240_h40.jpg 3rd partyimages2001.47 s15.9 KB
https://x0.ifengimg.com/ucms/2020_52/05C1B236228FC0496C7073E3CE753021AB2DD8C3_size16_w240_h40.jpg 3rd partyimages2001.47 s16.0 KB
https://x0.ifengimg.com/ucms/2024_32/547B3B502317AF80C8443F561BD7850658FE5697_size11_w388_h32.jpg 3rd partyimages2001.47 s11.0 KB
https://x0.ifengimg.com/ucms/2021_30/96502FB0B2136C2DB6F766E95A5E35DDDC2764D1_size6_w360_h60.jpg 3rd partyimages2001.46 s5.6 KB
https://x2.ifengimg.com/fe/shank/indexPC/pc_index.e705bc6f43.js 3rd partyjavascript2001.43 s67.6 KB
https://x0.ifengimg.com/cmpp/96e88c74a1c1f75f/2021/1/72c72997f229a94.png 3rd partyimages2001.42 s908 B
https://x2.ifengimg.com/fe/custom/dll/core-js.3.32.2.js 3rd partyjavascript2001.42 s71.8 KB
https://x0.ifengimg.com/feprod/c/m/mobile_inice_v202.js 3rd partyjavascript2001.42 s21.6 KB
https://x2.ifengimg.com/fe/shank/channel/errorupload-bdf4352595a.min.js 3rd partyjavascript2001.42 s4.9 KB
https://x2.ifengimg.com/fe/custom/dll/react.17.0.2.js 3rd partyjavascript2001.41 s42.3 KB
https://x0.ifengimg.com/ucms/2020_52/379CD20470FA3ED0BEE07CBE7BBCFAB32CAD7C9F_size15_w186_h52.jpg 3rd partyimages2001.41 s14.5 KB
https://x2.ifengimg.com/fe/shank/indexPC/pc_index.b3bd929b92.css 3rd partycss2001.41 s9.4 KB
https://x0.ifengimg.com/ucms/2026_37/63BC3A903B6D8477942ED3FB864DFB3A68CCDECE_size77_w780_h106.jpg 3rd partyimages2001.41 s38.1 KB
https://x0.ifengimg.com/fe/shank/content/2019/0418/fa.min.js 3rd partyjavascript2001.41 s4.4 KB
https://x0.ifengimg.com/fe/custom/89c4a615c3d00302ec9a24e714427b46_staytime.js 3rd partyjavascript2001.41 s845 B
https://x0.ifengimg.com/feprod/c/2023_1_17/16_21_21/1.png 3rd partyimages2001.41 s796 B
https://x0.ifengimg.com/ucms/2021_51/1B231E86976F1E8BC0E1C0BAB2ECC39AED93073A_size0_w8_h34.png 3rd partyimages2001.41 s217 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.