25.3 sec in total
1.7 sec
23.2 sec
374 ms
Visit nealzhou.blog.163.com now to see the best up-to-date Nealzhou Blog 163 content for China and also check out these interesting facts you probably never knew about nealzhou.blog.163.com
Visit nealzhou.blog.163.comWe analyzed Nealzhou.blog.163.com page load time and found that the first response time was 1.7 sec and then it took 23.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
nealzhou.blog.163.com performance score
1721 ms
729 ms
760 ms
1218 ms
1316 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nealzhou.blog.163.com, 22% (10 requests) were made to B.bst.126.net and 17% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Gorgon.youdao.com.
Page size can be reduced by 655.6 kB (45%)
1.5 MB
813.3 kB
In fact, the total size of Nealzhou.blog.163.com main page is 1.5 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. 30% of websites need less resources to load. Images take 689.1 kB which makes up the majority of the site volume.
Potential reduce by 58.2 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.2 kB or 76% of the original size.
Potential reduce by 90.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. Obviously, Nealzhou Blog 163 needs image optimization as it can save up to 90.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 358.3 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 358.3 kB or 69% of the original size.
Potential reduce by 149.1 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. Nealzhou.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 82% of the original size.
Number of requests can be reduced by 23 (53%)
43
20
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nealzhou Blog 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
nealzhou.blog.163.com
1721 ms
c.css
729 ms
b.css
760 ms
6630486124049534452.jpg
1218 ms
6619553679932601879.jpg
1316 ms
6630133180817252049.jpg
552 ms
xcode.png
722 ms
1.0.0.js
1839 ms
pc.js
1595 ms
ph.js
1596 ms
6608462906143855897.jpg
1237 ms
5788814371032821584.jpg
1533 ms
icon.png
53 ms
lnkbar.png
51 ms
image.png
51 ms
arrow24.png
52 ms
newtopbaricon8.png
53 ms
5770518497547033176.jpg
943 ms
5775866522104552963.jpg
664 ms
crossdomain.html
988 ms
crossdomain.html
561 ms
request.s
19658 ms
analyse.png
820 ms
crossdomain.html
562 ms
analyse.png
531 ms
analytics.js
35 ms
collect
17 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2478 ms
blogPhotoAd
270 ms
close_01.png
9 ms
top_bg.png
10 ms
bottom_bg.png
12 ms
left_bg.png
10 ms
right_bg.png
11 ms
left_top.png
7 ms
right_top.png
8 ms
left_bottom.png
10 ms
right_bottom.png
11 ms
shadow.png
10 ms
SetupBeanNew.getCustomModulesData.dwr
1139 ms
SetupBeanNew.getResourceModulesData.dwr
1421 ms
r
545 ms
ad
547 ms
close2.png
87 ms
jquery-1.4.2.js
575 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
3442 ms
nealzhou.blog.163.com SEO score
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nealzhou.blog.163.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 Nealzhou.blog.163.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
nealzhou.blog.163.com
Open Graph description is not detected on the main page of Nealzhou Blog 163. 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: