27 sec in total
2.2 sec
24.5 sec
366 ms
Click here to check amazing Nizd content for China. Otherwise, check out these important facts you probably never knew about nizd.net
Visit nizd.netWe analyzed Nizd.net page load time and found that the first response time was 2.2 sec and then it took 24.8 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.
nizd.net performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.8 s
56/100
25%
Value3.2 s
92/100
10%
Value120 ms
97/100
30%
Value0.032
100/100
15%
Value4.0 s
87/100
10%
2163 ms
219 ms
455 ms
1380 ms
658 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 17% of them (15 requests) were addressed to the original Nizd.net, 16% (14 requests) were made to Bdimg.share.baidu.com and 6% (5 requests) were made to Vip4.rwjfs.com. The less responsive or slowest element that took the longest time to load (10.4 sec) relates to the external source Nizd.duoshuo.com.
Page size can be reduced by 457.0 kB (44%)
1.0 MB
580.6 kB
In fact, the total size of Nizd.net main page is 1.0 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. Javascripts take 470.9 kB which makes up the majority of the site volume.
Potential reduce by 68.8 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 68.8 kB or 77% of the original size.
Potential reduce by 28.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. Nizd images are well optimized though.
Potential reduce by 252.6 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 252.6 kB or 54% of the original size.
Potential reduce by 107.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. Nizd.net needs all CSS files to be minified and compressed as it can save up to 107.6 kB or 82% of the original size.
Number of requests can be reduced by 60 (71%)
85
25
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nizd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.nizd.net
2163 ms
style.css
219 ms
cms.css
455 ms
embed.js
1380 ms
jquery.min.js
658 ms
scrollmonitor.js
444 ms
slides.js
493 ms
echo.min.js
497 ms
script.js
492 ms
flexisel.js
678 ms
cpv_fm_r.js
1210 ms
c.js
1412 ms
3dtag.js
706 ms
15636654.js
778 ms
wb.js
39 ms
superfish.js
779 ms
infinite_scroll.js
778 ms
005K2PVdjw1ewju1e7nrzj30j607kwgu.jpg
98 ms
loading.gif
258 ms
weixin.jpg
263 ms
zm.woff
241 ms
ir.ashx
4331 ms
embed.default.css
82 ms
embed.compat.js
227 ms
counts.json
10432 ms
rv1.ashx
1627 ms
tj.yule8.net
900 ms
ask
770 ms
ct
10060 ms
lm.jpg
1068 ms
icon_0.gif
735 ms
hm.js
651 ms
share.js
939 ms
loading1.gif
8 ms
bundle.js
14 ms
z_stat.php
1625 ms
client.js
11 ms
iframeWidget.js
12 ms
aj_relationship.php
1758 ms
qi
869 ms
hm.gif
246 ms
close.png
2415 ms
v2.ashx
3763 ms
logo.png
853 ms
share_api.js
314 ms
share_view.js
616 ms
select_api.js
3733 ms
select_view.js
2208 ms
image_api.js
741 ms
image_view.js
914 ms
tangram.js
3457 ms
api_base.js
901 ms
view_base.js
901 ms
stat.htm
674 ms
core.php
1216 ms
followbutton.php
710 ms
followButton.css
247 ms
sso.js
9 ms
followButton.js
8 ms
suda.js
9 ms
bg_flbtn.png
12 ms
b.gif
1653 ms
fx.htm
329 ms
Wno.html
26 ms
z_stat.php
1028 ms
z_stat.php
861 ms
logger.js
319 ms
stat.htm
161 ms
core.php
279 ms
core.php
859 ms
stat.htm
175 ms
9.gif
1683 ms
index
1746 ms
320X270.jpg
8439 ms
partners.js
369 ms
share_style0_16.css
439 ms
9.gif
1035 ms
icons_0_16.png
1036 ms
app.gif
3821 ms
g-106203.v-282329
1935 ms
app.gif
840 ms
statIwt_www_new-min.js
4768 ms
vasd_pv.js
34 ms
core-min.js
4761 ms
sogou_icon_wz_1.png
645 ms
fc.js
231 ms
co.js
217 ms
blank.gif
1752 ms
irt
2013 ms
nizd.net 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
<frame> or <iframe> elements do not have a title
nizd.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
nizd.net SEO score
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
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nizd.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Nizd.net 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.
nizd.net
Open Graph description is not detected on the main page of Nizd. 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: