24 sec in total
5.2 sec
15.3 sec
3.5 sec
Visit 2711082222.blog.163.com now to see the best up-to-date 2711082222 Blog 163 content for China and also check out these interesting facts you probably never knew about 2711082222.blog.163.com
Visit 2711082222.blog.163.comWe analyzed 2711082222.blog.163.com page load time and found that the first response time was 5.2 sec and then it took 18.8 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.
2711082222.blog.163.com performance score
5166 ms
46 ms
34 ms
1564 ms
69 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 2711082222.blog.163.com, 47% (36 requests) were made to B.bst.126.net and 13% (10 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (10.5 sec) relates to the external source Img.blog.csdn.net.
Page size can be reduced by 610.9 kB (65%)
942.5 kB
331.6 kB
In fact, the total size of 2711082222.blog.163.com main page is 942.5 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. 35% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.
Potential reduce by 94.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 94.1 kB or 79% 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. 2711082222 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 148.8 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. 2711082222.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.8 kB or 82% of the original size.
Number of requests can be reduced by 50 (67%)
75
25
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2711082222 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 16 to 1 for JavaScripts and as a result speed up the page load time.
2711082222.blog.163.com
5166 ms
c.css
46 ms
nb.css
34 ms
6630714822468849011.jpg
1564 ms
me_bg.jpg
69 ms
me_01.gif
284 ms
me_04.gif
115 ms
me_06.gif
106 ms
20150516172509485
10510 ms
me_07.gif
63 ms
icon.png
65 ms
6630133180817252049.jpg
986 ms
1.0.0.js
187 ms
pc.js
215 ms
ph.js
413 ms
lnkbar.png
102 ms
image.png
102 ms
arrow24.png
94 ms
newtopbaricon8.png
108 ms
me_10.gif
58 ms
me_13.gif
53 ms
me_12.gif
55 ms
xcode.png
56 ms
crossdomain.html
757 ms
crossdomain.html
948 ms
crossdomain.html
1869 ms
request.s
871 ms
analyse.png
792 ms
ava.s
1352 ms
loftericon.png
1227 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
869 ms
nb.css
159 ms
ava.s
963 ms
analyse.png
927 ms
background.gif
66 ms
player_02.gif
66 ms
player_06.gif
70 ms
player_16.gif
64 ms
player_17.gif
67 ms
stopping.gif
129 ms
player_23.gif
119 ms
timeline_1.gif
118 ms
player_29.gif
120 ms
analytics.js
96 ms
collect
75 ms
HomeBeanNew.getAccessStatistics.dwr
2000 ms
HomeBeanNew.getMonthStatistics.dwr
1057 ms
HomeBeanNew.getWeatherCityCode.dwr
1212 ms
NoteBeanNew.getNotesForPrev.dwr
1212 ms
MusicBeanNew.getPlayList.dwr
4150 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1718 ms
BlogBeanNew.getBlogClasses.dwr
1890 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1673 ms
blogPhotoAd
345 ms
close_01.png
64 ms
top_bg.png
31 ms
bottom_bg.png
33 ms
left_bg.png
28 ms
right_bg.png
30 ms
left_top.png
32 ms
right_top.png
61 ms
left_bottom.png
64 ms
right_bottom.png
63 ms
shadow.png
36 ms
r
1740 ms
.gif
405 ms
face0.gif
82 ms
face50.gif
81 ms
face79.gif
80 ms
face30.gif
81 ms
close2.png
19 ms
face73.gif
13 ms
BgsBean.getBgsUserByUserId.dwr
674 ms
ad
596 ms
jquery-1.4.2.js
36 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1692 ms
list_line.gif
52 ms
2711082222.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 2711082222.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 2711082222.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.
2711082222.blog.163.com
Open Graph description is not detected on the main page of 2711082222 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: