21.5 sec in total
2.8 sec
17.8 sec
891 ms
Visit libo93122.blog.163.com now to see the best up-to-date Libo 93122 Blog 163 content for China and also check out these interesting facts you probably never knew about libo93122.blog.163.com
Visit libo93122.blog.163.comWe analyzed Libo93122.blog.163.com page load time and found that the first response time was 2.8 sec and then it took 18.7 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.
libo93122.blog.163.com performance score
2831 ms
24 ms
943 ms
2224 ms
213 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Libo93122.blog.163.com, 23% (19 requests) were made to Os.blog.163.com and 15% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Iad.g.163.com.
Page size can be reduced by 610.9 kB (66%)
919.7 kB
308.8 kB
In fact, the total size of Libo93122.blog.163.com main page is 919.7 kB. 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. Javascripts take 525.2 kB which makes up the majority of the site volume.
Potential reduce by 91.1 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 91.1 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. Libo 93122 Blog 163 images are well optimized though.
Potential reduce by 360.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 360.6 kB or 69% of the original size.
Potential reduce by 149.7 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. Libo93122.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.7 kB or 82% of the original size.
Number of requests can be reduced by 43 (54%)
80
37
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Libo 93122 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 17 to 1 for JavaScripts and as a result speed up the page load time.
libo93122.blog.163.com
2831 ms
c.css
24 ms
b.css
943 ms
6630133180817252049.jpg
2224 ms
xcode.png
213 ms
1.0.0.js
637 ms
5773614722290757688.jpg
770 ms
icon.png
84 ms
lnkbar.png
79 ms
image.png
80 ms
arrow24.png
89 ms
newtopbaricon8.png
88 ms
5780651596708532657.jpg
4370 ms
5780651596708532661.jpg
1964 ms
5780651596708532660.jpg
1124 ms
5780651596708532666.jpg
1487 ms
5780651596708532662.jpg
1758 ms
5780651596708532668.jpg
2777 ms
5780651596708532663.jpg
2110 ms
5780651596708532665.jpg
4908 ms
5780651596708532664.jpg
4481 ms
pc.js
40 ms
ph.js
97 ms
crossdomain.html
855 ms
crossdomain.html
2345 ms
crossdomain.html
916 ms
request.s
2105 ms
analyse.png
1878 ms
ava.s
459 ms
loftericon.png
377 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
2119 ms
BlogCircleBean.getUserShowCircles.dwr
1152 ms
ava.s
864 ms
analyse.png
1867 ms
analytics.js
47 ms
collect
34 ms
HomeBeanNew.getFriends.dwr
898 ms
HomeBeanNew.getAccessStatistics.dwr
1190 ms
NoteBeanNew.getNotesForPrev.dwr
1314 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1270 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3036 ms
blogPhotoAd
2181 ms
close_01.png
47 ms
top_bg.png
75 ms
bottom_bg.png
74 ms
left_bg.png
74 ms
right_bg.png
73 ms
left_top.png
74 ms
right_top.png
85 ms
left_bottom.png
89 ms
right_bottom.png
89 ms
shadow.png
33 ms
ava.s
456 ms
ava.s
500 ms
ava.s
846 ms
ava.s
840 ms
ava.s
918 ms
ava.s
911 ms
ava.s
1154 ms
ava.s
1285 ms
ava.s
1267 ms
ava.s
1337 ms
ava.s
1340 ms
ava.s
1686 ms
ava.s
1700 ms
ava.s
3306 ms
ava.s
1749 ms
ava.s
1779 ms
BgsBean.getBgsUserByUserId.dwr
876 ms
UserSpaceBean.getUserSpace.dwr
3490 ms
r
2296 ms
close2.png
19 ms
ad
5027 ms
AlbumBeanNew.getUserSpace.dwr
876 ms
sniff.png
1950 ms
124244815993229.js
836 ms
-1.gif
25 ms
124244815993228.js
502 ms
empty.png
24 ms
1737545031234965232.jpg
2048 ms
jquery-1.4.2.js
11 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
3835 ms
libo93122.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 Libo93122.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 Libo93122.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.
libo93122.blog.163.com
Open Graph description is not detected on the main page of Libo 93122 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: