29.1 sec in total
3.8 sec
24.8 sec
579 ms
Welcome to xujinxi2012.blog.163.com homepage info - get ready to check Xujinxi 2012 Blog 163 best content for China right away, or after learning these important things about xujinxi2012.blog.163.com
Visit xujinxi2012.blog.163.comWe analyzed Xujinxi2012.blog.163.com page load time and found that the first response time was 3.8 sec and then it took 25.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 were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
xujinxi2012.blog.163.com performance score
3764 ms
92 ms
854 ms
7228 ms
104 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Xujinxi2012.blog.163.com, 22% (19 requests) were made to B.bst.126.net and 21% (18 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 604.2 kB (32%)
1.9 MB
1.3 MB
In fact, the total size of Xujinxi2012.blog.163.com main page is 1.9 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.9 kB or 80% of the original size.
Potential reduce by 9.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. Xujinxi 2012 Blog 163 images are well optimized though.
Potential reduce by 358.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 358.5 kB or 69% of the original size.
Potential reduce by 149.5 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. Xujinxi2012.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 82% of the original size.
Number of requests can be reduced by 39 (49%)
79
40
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xujinxi 2012 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 13 to 1 for JavaScripts and as a result speed up the page load time.
xujinxi2012.blog.163.com
3764 ms
c.css
92 ms
b.css
854 ms
6630133180817252049.jpg
7228 ms
xcode.png
104 ms
1.0.0.js
126 ms
pc.js
60 ms
ph.js
78 ms
5791347645821826538.jpg
19535 ms
blog_rec.png
108 ms
5790503220891695213.jpg
15440 ms
5790503220891695211.jpg
8123 ms
5772207347405524628.jpg
1967 ms
5790503220891695217.jpg
1905 ms
5791347645821826575.jpg
1938 ms
5772207347405524812.jpg
7564 ms
icon.png
75 ms
lnkbar.png
77 ms
image.png
79 ms
arrow24.png
78 ms
newtopbaricon8.png
76 ms
crossdomain.html
1421 ms
crossdomain.html
3140 ms
crossdomain.html
726 ms
request.s
2073 ms
analyse.png
947 ms
empty.png
55 ms
ava.s
939 ms
loftericon.png
473 ms
ava.s
1328 ms
4542443174173730786.jpg
6476 ms
5130725875499018954.jpg
20054 ms
5788814371831477677.jpg
20278 ms
4847843523904791063.jpg
20281 ms
5791066171645162584.jpg
20282 ms
3723350991945731648.jpg
20285 ms
analyse.png
1145 ms
analytics.js
106 ms
collect
48 ms
blogPhotoAd
477 ms
close_01.png
77 ms
top_bg.png
136 ms
bottom_bg.png
141 ms
left_bg.png
141 ms
right_bg.png
141 ms
left_top.png
141 ms
right_top.png
140 ms
left_bottom.png
173 ms
right_bottom.png
171 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1394 ms
shadow.png
71 ms
HomeBeanNew.getFriends.dwr
2850 ms
HomeBeanNew.getAccessStatistics.dwr
1302 ms
UserBeanNew.getVisitor.dwr
1304 ms
NoteBeanNew.getNotesForPrev.dwr
1549 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
4937 ms
r
2462 ms
BgsBean.getBgsUserByUserId.dwr
882 ms
ava.s
816 ms
ava.s
369 ms
ava.s
743 ms
ava.s
747 ms
ava.s
2601 ms
ava.s
764 ms
ava.s
2993 ms
ava.s
1113 ms
ava.s
1113 ms
ava.s
1129 ms
ava.s
1255 ms
ava.s
1494 ms
ava.s
1496 ms
ava.s
1536 ms
ava.s
1713 ms
close2.png
21 ms
face50.gif
21 ms
face51.gif
20 ms
face50.gif
26 ms
face81.gif
27 ms
face80.gif
24 ms
face66.gif
25 ms
face71.gif
27 ms
face58.gif
30 ms
ad
1102 ms
jquery-1.4.2.js
135 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
1499 ms
xujinxi2012.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 Xujinxi2012.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 Xujinxi2012.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.
xujinxi2012.blog.163.com
Open Graph description is not detected on the main page of Xujinxi 2012 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: