29.4 sec in total
3.1 sec
25.5 sec
782 ms
Visit xlsbj2011.blog.163.com now to see the best up-to-date Xlsbj 2011 Blog 163 content for China and also check out these interesting facts you probably never knew about xlsbj2011.blog.163.com
Visit xlsbj2011.blog.163.comWe analyzed Xlsbj2011.blog.163.com page load time and found that the first response time was 3.1 sec and then it took 26.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. 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.
xlsbj2011.blog.163.com performance score
3125 ms
13 ms
742 ms
635 ms
521 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Xlsbj2011.blog.163.com, 22% (17 requests) were made to Os.blog.163.com and 13% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source G.163.com.
Page size can be reduced by 582.8 kB (29%)
2.0 MB
1.5 MB
In fact, the total size of Xlsbj2011.blog.163.com main page is 2.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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 109.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 109.5 kB or 75% of the original size.
Potential reduce by 13.4 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. Xlsbj 2011 Blog 163 images are well optimized though.
Potential reduce by 310.5 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 310.5 kB or 69% of the original size.
Potential reduce by 149.4 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. Xlsbj2011.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.4 kB or 82% of the original size.
Number of requests can be reduced by 27 (38%)
72
45
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xlsbj 2011 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 11 to 1 for JavaScripts and as a result speed up the page load time.
xlsbj2011.blog.163.com
3125 ms
c.css
13 ms
b.css
742 ms
6631417410400970482.jpg
635 ms
6631312956796308705.jpg
521 ms
6631426206493912535.jpg
679 ms
6631229393912568000.jpg
880 ms
6631248085610173780.jpg
632 ms
6630690633213376935.jpg
647 ms
6630786290725004285.jpg
505 ms
6631448196725352377.jpg
1355 ms
6631328349957936799.jpg
324 ms
5748563449361943154.jpg
15626 ms
5733082325642873045.jpg
1833 ms
5755600323779715057.jpg
12753 ms
6631413012353171185.jpg
1898 ms
6630214544677737855.jpg
1971 ms
6631396519678690602.jpg
13561 ms
blog_rec.png
38 ms
6630133180817252049.jpg
1915 ms
xcode.png
62 ms
1.0.0.js
95 ms
pc.js
69 ms
ph.js
70 ms
5748563449361943152.jpg
9491 ms
6631387723585631692.jpg
3872 ms
icon.png
28 ms
rssi.png
46 ms
lnkbar.png
48 ms
image.png
51 ms
arrow24.png
50 ms
newtopbaricon8.png
46 ms
crossdomain.html
767 ms
crossdomain.html
1877 ms
crossdomain.html
2839 ms
request.s
2204 ms
analyse.png
1224 ms
ava.s
2855 ms
loftericon.png
415 ms
analyse.png
1411 ms
analytics.js
12 ms
collect
15 ms
SetupBeanNew.getCustomModulesData.dwr
788 ms
HomeBeanNew.getAccessStatistics.dwr
1066 ms
UserBeanNew.getVisitor.dwr
9363 ms
BlogBeanNew.getBlogClasses.dwr
9380 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1016 ms
blogPhotoAd
435 ms
close_01.png
6 ms
top_bg.png
11 ms
bottom_bg.png
15 ms
left_bg.png
11 ms
right_bg.png
12 ms
left_top.png
18 ms
right_top.png
16 ms
left_bottom.png
16 ms
right_bottom.png
14 ms
shadow.png
11 ms
r
20289 ms
BgsBean.getBgsUserByUserId.dwr
764 ms
close2.png
17 ms
ava.s
716 ms
ava.s
2485 ms
ava.s
2522 ms
ava.s
2500 ms
ava.s
2787 ms
ava.s
2832 ms
ava.s
1684 ms
ava.s
2054 ms
ava.s
2394 ms
ava.s
4418 ms
ava.s
3215 ms
ava.s
4986 ms
ava.s
2855 ms
ava.s
3758 ms
ava.s
4980 ms
xlsbj2011.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 Xlsbj2011.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 Xlsbj2011.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.
xlsbj2011.blog.163.com
Open Graph description is not detected on the main page of Xlsbj 2011 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: