18.8 sec in total
1.4 sec
16.8 sec
571 ms
Welcome to znzs.com homepage info - get ready to check Znzs best content for China right away, or after learning these important things about znzs.com
WearADay, 智能助手, 谷歌加速器, 智能手表, 表盘商店, 应用商店, Android Wear, Watch, Moto360, Moto360 二代, HUAWEI Watch, Apple Watch, LG Watch, 最新最酷的智能穿戴社区
Visit znzs.comWe analyzed Znzs.com page load time and found that the first response time was 1.4 sec and then it took 17.3 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.
znzs.com performance score
1410 ms
1159 ms
1158 ms
1987 ms
1561 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 31% of them (34 requests) were addressed to the original Znzs.com, 18% (20 requests) were made to Img.wearaday.com and 11% (12 requests) were made to Pic.wearaday.com. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Static.anquan.org.
Page size can be reduced by 414.6 kB (16%)
2.7 MB
2.3 MB
In fact, the total size of Znzs.com main page is 2.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. 45% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 77.9 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 77.9 kB or 82% of the original size.
Potential reduce by 71.8 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. Znzs images are well optimized though.
Potential reduce by 236.2 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 236.2 kB or 74% of the original size.
Potential reduce by 28.7 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. Znzs.com needs all CSS files to be minified and compressed as it can save up to 28.7 kB or 82% of the original size.
Number of requests can be reduced by 23 (22%)
106
83
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Znzs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
znzs.com
1410 ms
global
1159 ms
modernizr
1158 ms
stat.php
1987 ms
jquery
1561 ms
jquery.signalR-2.2.0.js
1579 ms
hubs
775 ms
core
1940 ms
jssor.slider.min.js
1570 ms
aq_auth.js
7527 ms
logo.png
394 ms
ico-user.png
400 ms
ico-search.png
801 ms
banner.jpg
4244 ms
bg-card.png
1137 ms
wd-desc.png
1529 ms
ico-news.png
1160 ms
qr-weixin.jpg
1194 ms
placeholder.png
1508 ms
GetAppQR
1535 ms
bg-activation.png
1568 ms
index.php
3807 ms
bg-watchface.png
1577 ms
ico-card.png
1883 ms
bg-app.png
1940 ms
fb-logo.png
1941 ms
stat.htm
169 ms
core.php
1761 ms
9.gif
2069 ms
ico-wechat.png
390 ms
ico-qq.png
390 ms
ico-weibo.png
391 ms
weiboShow.css
2008 ms
skin05.css
2012 ms
gaea_1_19.js
503 ms
show.js
473 ms
suda.js
474 ms
app.gif
1231 ms
1
550 ms
005SN5UQjw1f21ba6mfh8j30zk0npdk0.jpg
279 ms
005SN5UQjw1f20yaghbxpj30go0b3wf8.jpg
54 ms
005SN5UQjw1f20ugj9vcmj30go0audgf.jpg
291 ms
005SN5UQjw1f1yufny69pj30b406uaaq.jpg
230 ms
005SN5UQjw1f200zp0st9j30qo0hsdkt.jpg
285 ms
005SN5UQjw1f1zp3prdijg309z05me83.gif
285 ms
005SN5UQjw1f1ynm8diufj30hs0e4wez.jpg
308 ms
60718250jw1f20yex09jlj21kw11wgtb.jpg
272 ms
005SN5UQjw1f1zni19np2j30qo0hstcm.jpg
259 ms
005SN5UQjw1f201qa1v0nj30c80i9wex.jpg
271 ms
005SN5UQjw1f200osyg9lj30c80c8mxk.jpg
270 ms
005SN5UQjw1f1zw865t19j30zk0qojv5.jpg
282 ms
005SN5UQjw1f1zsszk7jcj30c80c23z5.jpg
296 ms
005SN5UQjw1f1zmba0bkcj30go0ay0th.jpg
295 ms
wb_logo16_a.png
42 ms
icon_user.png
42 ms
btns_bg.png
42 ms
icon_follow.png
42 ms
005SN5UQjw1f20r6fdc3tj30zk0qotgn.jpg
45 ms
005SN5UQjw1f1zn56jtcug30m80cie84.gif
45 ms
005SN5UQjw1f1ypndk2nuj30m80ettc6.jpg
45 ms
005SN5UQjw1f1yp99t0hsg30ak05xb2a.gif
42 ms
005SN5UQjw1f1yuk5vsrdj30cd0g83zf.jpg
43 ms
005SN5UQjw1f1yu4sh2z6j30go07p3yq.jpg
41 ms
bg_trans.png
13 ms
icon_tips.png
14 ms
a.gif
1102 ms
tmp.gif
4303 ms
GetBoardData
405 ms
GetHotAndRecommend
497 ms
GetNVHomeData
874 ms
1928 ms
10b22947feab45b0bca0d3e1fa3da8de.png
1084 ms
28402ae4ec36454c9f9fcd58c55f1bf2.png
1473 ms
66e25e9f59e64273bb67d730e0a95d92.png
1474 ms
538b4a838663425881df1576d57c48a0.png
1079 ms
bg-theme.png
443 ms
3658dea0a146409981092cb9357b26b0.png
1497 ms
comm.jpg
1843 ms
af7a4378367d4c029178b3993f3e9dd3.jpg
1969 ms
94e83f6503a947689a6f931c6adb7c05.png
787 ms
e728d72d092d45d2b9a540479db325d2.jpg
5429 ms
a46e45ff236a4531b203ad4d01e39b24.jpg
6882 ms
09be0e20bf024a23b75436d511479ee6.png
1181 ms
e9a4cec3ab2342f489068d8c35f80fb6.jpg
2125 ms
865b9d60d4ff4b608f94efe3d3a96a05.jpg
1731 ms
5fa20f4b629a4507951671ffa0bb5d98.jpg
3174 ms
e8f93a2bdd0047cbb2ee6c55307045d8.jpg
5942 ms
aa8da7843c3b4e148b157256c9b74aed.jpg
2772 ms
525c6e923dfc4f2b8a487e2e1820aaaa.jpg
2531 ms
c77b2a59b1c94a28a0e115ce2ecb495b.jpg
3335 ms
3f4effc9c95d4d209bfd47299456dcd1.jpg
3175 ms
62bbce48399a4de69ef03cca94781281.jpg
3571 ms
5266175487904fbfb1ea194229519cf6.jpg
3572 ms
907eab40c80a4ba98a075d2979fbf780.jpg
3730 ms
f2997405d34543df8f86e0527a819753.png
1841 ms
6d410a752fcb434f8605cfbc92e12ce4.png
1513 ms
290558d890c24774b305a76cb7d3d6ba.png
1515 ms
e38304b87e754448bba599f1810ab2ec.png
1946 ms
786510a3481f4bc1821ad04be70c2fd7.png
1095 ms
bd66a942f85e49c5b9b85fd3e6ad7a4f.png
3635 ms
a28c4b23947146848840e8f5932aaf3e.png
2645 ms
c1491e29146d4994b78b624898065350.png
3219 ms
8b83ff4973464685bb3f23d279eae619.png
3632 ms
079ec3c8cc5547249116cb69188b32cb.png
2241 ms
786de86bbb4048b18159b887d1fde58c.png
3638 ms
ico-view.png
390 ms
ico-comm.png
410 ms
iconfont.woff
423 ms
hy_83x30.png
864 ms
znzs.com SEO score
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Znzs.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Znzs.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.
znzs.com
Open Graph description is not detected on the main page of Znzs. 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: