14.7 sec in total
74 ms
13.1 sec
1.5 sec
Click here to check amazing Cn Engadget content for United States. Otherwise, check out these important facts you probably never knew about cn.engadget.com
最新科技新聞、產品評測,消費性電子產品消息不斷更新,豐富分析及評論,盡在Yahoo香港新聞
Visit cn.engadget.comWe analyzed Cn.engadget.com page load time and found that the first response time was 74 ms and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cn.engadget.com performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value2.2 s
94/100
25%
Value1.1 s
100/100
10%
Value0 ms
100/100
30%
Value0.026
100/100
15%
Value1.1 s
100/100
10%
74 ms
15 ms
23 ms
49 ms
48 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Cn.engadget.com, 23% (27 requests) were made to O.aolcdn.com and 8% (9 requests) were made to Blogsmithmedia.com. The less responsive or slowest element that took the longest time to load (10.9 sec) relates to the external source Rs.sinajs.cn.
Page size can be reduced by 1.3 MB (28%)
4.7 MB
3.4 MB
In fact, the total size of Cn.engadget.com main page is 4.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 58.1 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.1 kB or 76% of the original size.
Potential reduce by 90.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Cn Engadget images are well optimized though.
Potential reduce by 832.5 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 832.5 kB or 69% of the original size.
Potential reduce by 342.4 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Cn.engadget.com needs all CSS files to be minified and compressed as it can save up to 342.4 kB or 82% of the original size.
Number of requests can be reduced by 43 (37%)
115
72
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cn Engadget. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cn.engadget.com
74 ms
adsWrapperIntl.js
15 ms
23 ms
188467830.js
49 ms
style.css
48 ms
style_locale.css
108 ms
core.js
111 ms
wb.js
8 ms
adhads.css
18 ms
moatuacintl.js
123 ms
weibo.png
36 ms
embed.js
248 ms
analytics.js
18 ms
P4062011_thumbnail.jpg
17 ms
meilannote3_thumbnail.png
100 ms
meizu-pro-6_thumbnail.jpg
16 ms
xiaomi-transformers-lede_thumbnail.jpg
14 ms
P9050272_f_FB_thumbnail.jpg
14 ms
Outlook+iOS+icon1.jpg
102 ms
509819957.jpg
106 ms
stock-photo-jacksonville-fl-usa-june-a-dji-phantom-consumer-drone-flying-in-the-sky-with-a-gopro-288324377-ed.jpg
105 ms
12928301_930149533771394_453073751301243533_n.png
112 ms
flagship-5.jpg
102 ms
meizu-pro-6.jpg
101 ms
7D2D_Screen_Forest.jpg
110 ms
panasonic-fancy-airplane-seat-2016-04-07-01.jpg
107 ms
hermes.jpg
108 ms
goproomni.jpg
106 ms
jquery.js
95 ms
logincookie.js
97 ms
plugins.js
101 ms
eng.js
97 ms
eng_init.js
97 ms
adhads-min.js
103 ms
collect
79 ms
70 ms
x.gif
29 ms
cn.engadget.com
45 ms
beacon.min.js
35 ms
34 ms
30 ms
P9050272_f_FB_thumbnail.jpg
77 ms
WeiboShow.php
1400 ms
counts.json
2569 ms
mc.s2c.min.js
24 ms
Default_Size_16_1x1.gif
56 ms
AT221_768x90.gif
84 ms
Ad10711600St1Sz170Sq107364664V0Id2.jpg
112 ms
rd
35 ms
AT154_160x600_4.gif
101 ms
id
17 ms
s61352724793832
8 ms
34 ms
149 ms
4 ms
weiboShow.css
6 ms
skin_default.css
31 ms
gaea_1_19.js
9 ms
1
40 ms
6b18bcd9gw1f2o7ny6mvej20hi0b5q62.jpg
11 ms
6b18bcd9gw1f2nchn4rraj212w0lw0xy.jpg
36 ms
wb_logo16_a.png
3 ms
icon_user.png
2 ms
btns_bg.png
3 ms
icon_follow.png
4 ms
6b18bcd9gw1f2n2fan1gmj212w0gjn17.jpg
44 ms
6b18bcd9gw1f2hb6ifjhpj212w0ldgsv.jpg
45 ms
6b18bcd9gw1f2halz0bh6j20qo0f0gp9.jpg
45 ms
6b18bcd9jw1f2dt1z9quzj21kw0w0q9b.jpg
83 ms
1
40 ms
1
38 ms
1
35 ms
1
71 ms
suda.js
30 ms
1
54 ms
1
61 ms
1
57 ms
1
46 ms
1
96 ms
1
52 ms
1
45 ms
1
42 ms
1
43 ms
1
67 ms
0
47 ms
1
56 ms
6b18bcd9gw1f2n08diij3j212w0ibdj5.jpg
11 ms
6b18bcd9jw1f253xmsutvj218g0oiqea.jpg
12 ms
6b18bcd9jw1f252i0a86ij212w0m8dkm.jpg
29 ms
1
55 ms
1
46 ms
1
53 ms
6b18bcd9jw1f2dmoiep05j20uu0gjtew.jpg
29 ms
6b18bcd9jw1f252h6wyvxj212w0sagps.jpg
29 ms
6b18bcd9jw1f251i83n71j20vs0vs0u3.jpg
27 ms
6b18bcd9jw1f2fz6hbvudj20qo0ecafu.jpg
27 ms
6b18bcd9jw1f2aoo9iz1mj20ma0nfdjr.jpg
55 ms
6b18bcd9jw1f25215gmg7j20qo0f00up.jpg
47 ms
1
47 ms
6b18bcd9gw1f2h5k9ph01j212w0lewli.jpg
29 ms
6b18bcd9jw1f265go7zuzj20sg0e73zs.jpg
28 ms
6b18bcd9jw1f252nbgzfcj212w0hrjt6.jpg
41 ms
6b18bcd9jw1f251vq14o6j20ng0d6gnq.jpg
48 ms
show.js
9 ms
bg_trans.png
22 ms
icon_tips.png
25 ms
a.gif
1241 ms
tmp.gif
10907 ms
embed.default.css
77 ms
guid.html
114 ms
eutcode.html
163 ms
mc.s2c.css
8 ms
slf.js
38 ms
916f392e-1af6-43dd-bc12-239421d8b718.js
82 ms
slf.js
15 ms
r.js
20 ms
916f392e-1af6-43dd-bc12-239421d8b718
44 ms
d075f15f-fd25-4bce-aa68-8e676533c3b8.js
70 ms
9e865b16-bf55-4ffb-9f2a-70dadfc986c7.js
66 ms
cn.engadget.com accessibility score
cn.engadget.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
cn.engadget.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cn.engadget.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Cn.engadget.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
cn.engadget.com
Open Graph description is not detected on the main page of Cn Engadget. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: