23.8 sec in total
1.4 sec
22 sec
361 ms
Visit lxsxb116.blog.163.com now to see the best up-to-date Lxsxb 116 Blog 163 content for China and also check out these interesting facts you probably never knew about lxsxb116.blog.163.com
Visit lxsxb116.blog.163.comWe analyzed Lxsxb116.blog.163.com page load time and found that the first response time was 1.4 sec and then it took 22.4 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 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lxsxb116.blog.163.com performance score
1372 ms
378 ms
891 ms
804 ms
46 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Lxsxb116.blog.163.com, 25% (17 requests) were made to Os.blog.163.com and 16% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 600.9 kB (59%)
1.0 MB
422.5 kB
In fact, the total size of Lxsxb116.blog.163.com 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. 40% of websites need less resources to load. Javascripts take 521.3 kB which makes up the majority of the site volume.
Potential reduce by 81.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 81.2 kB or 80% of the original size.
Potential reduce by 12.2 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. Lxsxb 116 Blog 163 images are well optimized though.
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.2 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. Lxsxb116.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.2 kB or 82% of the original size.
Number of requests can be reduced by 26 (43%)
60
34
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lxsxb 116 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 10 to 1 for JavaScripts and as a result speed up the page load time.
lxsxb116.blog.163.com
1372 ms
c.css
378 ms
b.css
891 ms
6630133180817252049.jpg
804 ms
xcode.png
46 ms
1.0.0.js
92 ms
pc.js
41 ms
ph.js
40 ms
5723230701457918235.jpg
20148 ms
blog_rec.png
93 ms
5753348523965946470.jpg
20124 ms
5753348523965946276.jpg
20124 ms
5715630877086733794.jpg
20124 ms
5762355723220690754.jpg
20124 ms
5753348523965946274.jpg
20124 ms
icon.png
72 ms
lnkbar.png
72 ms
image.png
74 ms
arrow24.png
75 ms
newtopbaricon8.png
74 ms
crossdomain.html
784 ms
crossdomain.html
502 ms
crossdomain.html
727 ms
request.s
1670 ms
analyse.png
777 ms
empty.png
41 ms
3756565039281200877.jpg
3613 ms
ava.s
3998 ms
loftericon.png
375 ms
4876272496635848328.jpg
5028 ms
analyse.png
726 ms
analytics.js
16 ms
collect
16 ms
HomeBeanNew.getAccessStatistics.dwr
2129 ms
UserBeanNew.getVisitor.dwr
1128 ms
BlogBeanNew.getBlogClasses.dwr
2441 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1064 ms
blogPhotoAd
391 ms
close_01.png
10 ms
top_bg.png
16 ms
bottom_bg.png
17 ms
left_bg.png
17 ms
right_bg.png
26 ms
left_top.png
25 ms
right_top.png
24 ms
left_bottom.png
23 ms
right_bottom.png
25 ms
shadow.png
12 ms
r
715 ms
ava.s
646 ms
ava.s
710 ms
ava.s
2579 ms
ava.s
2645 ms
ava.s
1305 ms
ava.s
964 ms
ava.s
1065 ms
ava.s
1306 ms
ava.s
1422 ms
ava.s
1730 ms
ava.s
1649 ms
ava.s
1777 ms
ava.s
1973 ms
ava.s
2631 ms
ava.s
2170 ms
ad
1014 ms
close2.png
5 ms
jquery-1.4.2.js
286 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
1390 ms
lxsxb116.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 Lxsxb116.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 Lxsxb116.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.
lxsxb116.blog.163.com
Open Graph description is not detected on the main page of Lxsxb 116 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: