30.8 sec in total
2.1 sec
28.4 sec
302 ms
Visit 360.cn now to see the best up-to-date 360 content for China and also check out these interesting facts you probably never knew about 360.cn
360免费安全软件平台和智能硬件家居平台,免费安全软件平台为用户提供360安全卫士,360免费杀毒软件,360企业杀毒软件,360安全浏览器等安全软件,智能硬件家居平台包含360手机,智能摄像机,儿童智能手表,行车记录仪,智能路由器,超级充电器等智能硬件
Visit 360.cnWe analyzed 360.cn page load time and found that the first response time was 2.1 sec and then it took 28.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
360.cn performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value11.6 s
0/100
25%
Value7.9 s
22/100
10%
Value30 ms
100/100
30%
Value0.061
97/100
15%
Value10.1 s
26/100
10%
2111 ms
5542 ms
446 ms
345 ms
488 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 360.cn, 12% (20 requests) were made to P5.qhimg.com and 9% (16 requests) were made to P3.qhimg.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Index.360.cn.
Page size can be reduced by 1.8 MB (30%)
5.9 MB
4.1 MB
In fact, the total size of 360.cn main page is 5.9 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. 55% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 99.0 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. This page needs HTML code to be minified as it can gain 41.0 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 99.0 kB or 86% of the original size.
Potential reduce by 126.5 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. 360 images are well optimized though.
Potential reduce by 856.9 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 856.9 kB or 71% of the original size.
Potential reduce by 701.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. 360.cn needs all CSS files to be minified and compressed as it can save up to 701.4 kB or 83% of the original size.
Number of requests can be reduced by 25 (15%)
166
141
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 360. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
360.cn
2111 ms
www.360.com
5542 ms
87d89869a5f814a7.js
446 ms
t01b7cb83f41d31a8bf.png
345 ms
t0139a3cf9218887d3d.png
488 ms
p_weishi.png
351 ms
p_sd.png
439 ms
p_BSFree.png
437 ms
p_se.png
456 ms
p_FreeAP.png
333 ms
t011b28addd8836b27c.png
454 ms
t0133f12a04de03714d.png
3194 ms
t019de0dc44461f7014.png
3700 ms
t01c5bfd5968d038a63.png
4742 ms
t0138564074793584d7.png
2304 ms
t01499f9646e1e491ae.png
3416 ms
t0176919631a43c2947.png
332 ms
t014c94158a450b676d.jpg
480 ms
t0113fd57fbb3e42128.png
3687 ms
t01b792441769dbca78.png
3687 ms
t01c19a74efd704fac7.png
3688 ms
t0173d714f288c25f40.png
3689 ms
t01d0899e64eb0c2fcc.png
3690 ms
t01c66a355347d72ec4.png
3695 ms
p_etzm.png
468 ms
t01ed9966da50723860.png
466 ms
t0191be494f52bc3282.jpg
466 ms
qijian.png
468 ms
t013e5022f15377cb2a.png
470 ms
t0151c7660adf1a40d2.jpg
519 ms
t0181febd1456a12478.jpg
516 ms
p_Drv.png
328 ms
t01ee932c4b7d0b6d2e.png
370 ms
t012bcf75f2d6d9be2c.png
371 ms
t017769c919b5d179d2.jpg
368 ms
t01f4bb4a72e625b15e.jpg
360 ms
t0177b77e88153373e0.png
392 ms
t0167c1a687a2327e07.png
3168 ms
t0148544067be7fcaa3.png
3173 ms
t0139160967cf4ebbca.png
3175 ms
t01d0e3b41d88628a32.png
3183 ms
logo_56_2.png
408 ms
t0183bff0941fe4d0c6.jpg
409 ms
dianyuan.png
408 ms
t01da6c6e408cf349fa.png
4725 ms
t017d865e2942ac649e.png
4724 ms
p_zip.png
412 ms
p_aqzm.png
420 ms
p_ludashi.png
317 ms
t018bcca2d74748ed6a.png
315 ms
t01482282806bd0ddc5.png
315 ms
p_wangpan.png
428 ms
t01cb080b53d4f7027f.png
428 ms
p_safebox.png
427 ms
p_NmGame.png
431 ms
t01c5547a5c0d60c3ab.png
431 ms
t013811c7342a47c68c.png
3395 ms
t018da0363a6accda6f.png
3393 ms
p_compkill.png
418 ms
p_udisk.png
421 ms
MobileSafe_60.png
419 ms
etsb.png
421 ms
cdq.png
429 ms
xcjly.png
464 ms
ly.png
467 ms
t016544414e28cccaf9.png
466 ms
t01ca52fce5c3fdc29f.png
2280 ms
p_macweishi.png
305 ms
p_jiamiyou.png
299 ms
p_SRInst.png
302 ms
t017c013d7bc3d03d48.jpg
304 ms
t0107875c263316b3aa.jpg
310 ms
qingnian.png
308 ms
t01091bbd26575fe90e.jpg
309 ms
t01d2f5c9ba507a2bf9.png
33 ms
t016af0da90d950e31c.jpg
33 ms
t01f4935a14c479510a.jpg
107 ms
t017a45edcae5786988.png
37 ms
t016e3cf027a21a93b0.jpg
59 ms
t01d1be708d9555bd65.png
36 ms
t0188b053cccd4e95c4.jpg
70 ms
t01628f9e508f7025f8.jpg
140 ms
t01f1d8a98532f0601b.jpg
34 ms
t0133826bfc3d22fec3.jpg
208 ms
t0194a486485a585b9f.jpg
77 ms
t01fee0b991d10bf9a8.jpg
43 ms
t015463151574a6e04f.jpg
42 ms
t0135f14196f0c47da6.png
46 ms
t01ee5ea1e88c0984a7.jpg
149 ms
t010f8e9964bdb41c9a.jpg
78 ms
t01bb3f7c4a33b28d1e.jpg
75 ms
t0117b2e5fe4497236c.png
45 ms
t010fece94f56731621.png
44 ms
t019b3967d4e0fa32bf.png
47 ms
t010421cee3fc544ee5.jpg
77 ms
t01631a0f0c20f504f4.png
47 ms
t01a8c43b52a58369d8.jpg
162 ms
t017db5f348ce54f090.jpg
119 ms
t013e79e7a1b2aa404d.jpg
161 ms
t01caf28e8ec17485f4.jpg
116 ms
t01b6ba8c3ce054a796.jpg
79 ms
t0161642070da2af204.png
333 ms
t01065af3b476be2142.png
76 ms
t018e1bdf2122a4b64b.png
57 ms
t01d42a9f3b7887e90f.jpg
48 ms
t0150e553b0b1fc2377.png
57 ms
t017b3ff1e5f25f6143.png
56 ms
t0102378990a756a8b6.png
57 ms
t01a009f0594a97cfbf.png
83 ms
se_60.png
81 ms
t01dee6ec22cf9e7c8b.png
83 ms
weishi_60.png
80 ms
t01c2c7d8f18653f248.png
81 ms
t019a07ddffc8e3b2fd.jpg
86 ms
t0100cbd1b5d8558029.jpg
85 ms
etws.jpg
81 ms
t0100138b1764c0dfa0.jpg
79 ms
t01f29964a87aaf5097.png
78 ms
monitor131227.js
290 ms
Cookie.js
76 ms
lightbox.js
299 ms
edbe71c75e89e143.js
301 ms
4d2a0452538a9fa4.js
314 ms
542de339a50753c0.js
459 ms
72a3b5b755877d15.js
458 ms
9aaee991daab9dcc.js
446 ms
bbd801bedd8a82de.js
471 ms
90ccefbc24f29572.js
446 ms
8396af6b4e58a430.js
314 ms
4d3ad4802a3dfb0b.js
469 ms
2b203330b8cf8eb0.js
485 ms
sd_60.png
29 ms
8bg.png
30 ms
t01ca5bb3d02e77c7c6.png
27 ms
t016fa111d084899c91.jpg
45 ms
t01b467cfa1d93defb7.png
33 ms
t01ebb90dc165c57217.png
57 ms
t0155e6251d1fee3d53.png
46 ms
1yy.png
56 ms
4wzws.png
54 ms
t010a0758ba3aca5997.png
57 ms
t018e7ec69777636f5d.jpg
33 ms
t0150ff6c01204823b6.png
53 ms
2syy.png
30 ms
t015bdd8786a398786e.jpg
51 ms
t01bf860bc7ad3378ab.jpg
42 ms
t0190a8f690db90e745.png
40 ms
t01a6167590c23071c4.png
41 ms
5wg.png
30 ms
6jgb.png
38 ms
t01f7e161c69cc793e9.jpg
52 ms
t01d0d0dce899c68f79.png
40 ms
7dj.png
38 ms
t01d8eda6e551cf2615.png
49 ms
t014f381009d3705b10.png
51 ms
9qs.png
48 ms
t01bd6e2aef2c04a9f5.png
36 ms
t014d854b1e4ece8990.png
48 ms
Box_60.png
49 ms
t010eb99c2c6986b4a1.png
36 ms
t01a0a772ce3c932cce.jpg
48 ms
jquery,qw.core.js
5 ms
hotword.js
1907 ms
js.login.360.cn
2046 ms
getPubInfo
20366 ms
index.php
1989 ms
1998 ms
haopv.gif
4275 ms
haouv.gif
4332 ms
360.cn accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
360.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
360.cn SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 360.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that 360.cn 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.
360.cn
Open Graph description is not detected on the main page of 360. 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: