74.5 sec in total
13 sec
57.8 sec
3.7 sec
Click here to check amazing 360 Zdm content for China. Otherwise, check out these important facts you probably never knew about 360zdm.com
360值得买 什么值得买
Visit 360zdm.comWe analyzed 360zdm.com page load time and found that the first response time was 13 sec and then it took 61.5 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 were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
360zdm.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value29.9 s
0/100
25%
Value14.3 s
1/100
10%
Value570 ms
52/100
30%
Value0.362
30/100
15%
Value8.9 s
34/100
10%
13008 ms
599 ms
7771 ms
1273 ms
1269 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 360zdm.com, 38% (33 requests) were made to Img.alicdn.com and 22% (19 requests) were made to Cdn.360zdm.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Js.users.51.la.
Page size can be reduced by 270.5 kB (8%)
3.2 MB
3.0 MB
In fact, the total size of 360zdm.com main page is 3.2 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. 65% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 111.5 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 111.5 kB or 81% of the original size.
Potential reduce by 20.0 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 Zdm images are well optimized though.
Potential reduce by 117.4 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 117.4 kB or 55% of the original size.
Potential reduce by 21.6 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. 360zdm.com needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 78% of the original size.
Number of requests can be reduced by 20 (24%)
85
65
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 360 Zdm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.360zdm.com
13008 ms
uaredirect.js
599 ms
wp-emoji-release.min.js
7771 ms
pagenavi-css.css
1273 ms
style.css
1269 ms
red.css
1066 ms
css
1397 ms
jquery.js
454 ms
jquery-migrate.min.js
4214 ms
jquery.cycle.all.min.js
465 ms
aa962d9agw1eikb0d6c4qj201e0got8s.jpg
135 ms
TB2MOf6lpXXXXaUXpXXXXXXXXXX_!!684765009.jpg_430x430q90.jpg
136 ms
TB152LQHpXXXXaXXXXXXXXXXXXX_!!0-item_pic.jpg_400x400.jpg
452 ms
56612d46Nb6ca91b9.jpg
187 ms
56710c37Ncfb4532d.jpg
638 ms
539e58d9N9337c277.jpg
123 ms
56e22d78Ndb78e097.jpg
155 ms
56775d40N9286fa0b.jpg
417 ms
TB1EKoVLVXXXXXnXXXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
112 ms
TB1jqlAMpXXXXanXVXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
121 ms
TB2LUVQgpXXXXXJXpXXXXXXXXXX_!!1795591687.jpg_430x430q90.jpg
110 ms
TB18llLGXXXXXX3XVXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
113 ms
TB1ElMyLXXXXXcUXXXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
118 ms
TB2PgG8lFXXXXcxXpXXXXXXXXXX_!!2453518476.jpg_430x430q90.jpg
116 ms
TB17qAKLVXXXXapXpXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
127 ms
TB2.I3NlVXXXXcaXXXXXXXXXXXX_!!1891886484.jpg_430x430q90.jpg
122 ms
TB2VYnqjVXXXXbBXXXXXXXXXXXX_!!1637033965.jpg_430x430q90.jpg
128 ms
TB2CV5QmFXXXXcjXpXXXXXXXXXX_!!2047620906.jpg_430x430q90.jpg
139 ms
TB1CRkkLVXXXXX6XXXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
123 ms
TB2xPHchpXXXXbYXXXXXXXXXXXX_!!715463997.jpg_430x430q90.jpg
134 ms
TB1OoYcMXXXXXX5XFXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
135 ms
TB2SlcukFXXXXb_XpXXXXXXXXXX_!!2129241756.jpg_430x430q90.jpg
138 ms
TB1QbG9JVXXXXXNXFXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
141 ms
TB1al1eIVXXXXXcXXXXRS14.VXX_112347.jpg_430x430q90.jpg
136 ms
TB1AUzXMXXXXXXhaXXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
151 ms
568e0c13N50ab6310.jpg
127 ms
hot.png
854 ms
logo.png
851 ms
button.png
567 ms
tmall.gif
877 ms
background.png
645 ms
sprite.png
635 ms
554c50e9Nc0ba04e7.jpg
204 ms
TB2CJkWkVXXXXXvXXXXXXXXXXXX_!!2225088352.jpg_430x430q90.jpg
10 ms
TB1QBzuMXXXXXalXFXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
20 ms
TB27FjglVXXXXbiXpXXXXXXXXXX_!!2211162069.jpg_430x430q90.jpg
12 ms
TB2ViuOkVXXXXbKXXXXXXXXXXXX_!!1663047112.jpg_430x430q90.jpg
36 ms
TB1rZrfKVXXXXXuapXXXXXXXXXX_!!0-item_pic.jpg_400x400.jpg
99 ms
562dcbf1Ne61fc28c.jpg
59 ms
56e2a6fcNbd39ac27.jpg
500 ms
56c4205cNf34570ca.jpg
57 ms
TB2ODdOkXXXXXcOXXXXXXXXXXXX_!!601090207.jpg_430x430q90.jpg
19 ms
TB2T_bEmFXXXXb8XXXXXXXXXXXX_!!642152705.jpg_430x430q90.jpg
18 ms
TB11HhLMXXXXXXkapXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
28 ms
TB15QPfMXXXXXXQapXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
22 ms
TB10XXiMXXXXXX4XVXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
25 ms
TB1moRqLVXXXXcjXpXXXXXXXXXX_!!0-item_pic.jpg_430x430q90.jpg
28 ms
TB2IC.xmpXXXXcmXpXXXXXXXXXX_!!529782397.jpg_430x430q90.jpg
32 ms
TB2JNVMkpXXXXcLXXXXXXXXXXXX_!!1991854762.jpg_430x430q90.jpg
27 ms
TB2sGYIfFXXXXXNXpXXXXXXXXXX_!!2057657476.jpg_430x430q90.jpg
30 ms
TB2xQAEmXXXXXXJXpXXXXXXXXXX_!!928597170.jpg_430x430q90.jpg
31 ms
TB2.Eb5epXXXXbbXXXXXXXXXXXX_!!2456878545.jpg_430x430q90.jpg
24 ms
5667e02aN4d39246b.jpg
1478 ms
87a94540gw1f2pkb0o6hrj20c70c80vh.jpg
23 ms
pushIcon.png
553 ms
aa962d9agw1eojnoii975j2076076mxm.jpg
35 ms
search.gif
674 ms
sidebar_arrow.png
1597 ms
aa962d9agw1efcojx679wj207n02nmx6.jpg
449 ms
wp-embed.min.js
13 ms
kaixin.png
845 ms
renren.png
628 ms
13134857.js
20289 ms
scroll.png
900 ms
share.js
1218 ms
tkapi.js
258 ms
main.js
39 ms
plugin.js
26 ms
load
19652 ms
share_api.js
386 ms
share_view.js
766 ms
tangram.js
3123 ms
api_base.js
768 ms
view_base.js
432 ms
logger.js
390 ms
partners.js
343 ms
share_style1_16.css
377 ms
icons_1_16.png
816 ms
360zdm.com 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
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.
360zdm.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
360zdm.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 360zdm.com 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 360zdm.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.
360zdm.com
Open Graph description is not detected on the main page of 360 Zdm. 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: