25.6 sec in total
1.5 sec
23.6 sec
491 ms
Welcome to souvr11.blog.163.com homepage info - get ready to check Souvr 11 Blog 163 best content for China right away, or after learning these important things about souvr11.blog.163.com
Visit souvr11.blog.163.comWe analyzed Souvr11.blog.163.com page load time and found that the first response time was 1.5 sec and then it took 24.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
souvr11.blog.163.com performance score
1546 ms
28 ms
737 ms
1151 ms
3966 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 Souvr11.blog.163.com, 28% (21 requests) were made to Img.bimg.126.net and 16% (12 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source G.163.com.
Page size can be reduced by 551.2 kB (63%)
871.4 kB
320.3 kB
In fact, the total size of Souvr11.blog.163.com main page is 871.4 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. 25% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 79.4 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 79.4 kB or 79% of the original size.
Potential reduce by 9.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. Souvr 11 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 152.0 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. Souvr11.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.
Number of requests can be reduced by 40 (56%)
72
32
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Souvr 11 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.
souvr11.blog.163.com
1546 ms
c.css
28 ms
b.css
737 ms
S
1151 ms
6630133180817252049.jpg
3966 ms
xcode.png
21 ms
1.0.0.js
103 ms
pc.js
30 ms
ph.js
27 ms
5770799972522187428.jpg
626 ms
icon.png
103 ms
5779244221823515636.jpg
634 ms
5779244221823515635.jpg
825 ms
5791347645822068511.jpg
827 ms
5791347645822068509.jpg
1997 ms
5791347645822068513.jpg
891 ms
5780933071683780524.jpg
915 ms
5791347645822068515.jpg
2195 ms
5791347645822068517.jpg
2657 ms
5791347645822068546.jpg
1154 ms
5791347645822068549.jpg
1185 ms
5791347645822068547.jpg
1440 ms
5776992422009831185.jpg
2619 ms
5776992422009831184.jpg
1690 ms
5776992422009831186.jpg
1758 ms
5780088646753648775.jpg
2046 ms
5776992422009831187.jpg
2048 ms
5776992422009831188.jpg
2456 ms
5776992422009831189.jpg
2398 ms
5776992422009831191.jpg
2362 ms
5776992422009831190.jpg
2608 ms
lnkbar.png
90 ms
image.png
91 ms
arrow24.png
90 ms
newtopbaricon8.png
92 ms
crossdomain.html
786 ms
crossdomain.html
894 ms
crossdomain.html
815 ms
request.s
1832 ms
analyse.png
917 ms
ava.s
369 ms
loftericon.png
370 ms
ava.s
719 ms
analyse.png
954 ms
analytics.js
22 ms
collect
25 ms
HomeBeanNew.getFriends.dwr
848 ms
HomeBeanNew.getAccessStatistics.dwr
1064 ms
UserBeanNew.getVisitor.dwr
1080 ms
NoteBeanNew.getNotesForPrev.dwr
1069 ms
HomeBeanNew.getClassifyModuleData.dwr
1124 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
3000 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1673 ms
blogPhotoAd
488 ms
close_01.png
14 ms
top_bg.png
18 ms
bottom_bg.png
22 ms
left_bg.png
21 ms
right_bg.png
21 ms
left_top.png
18 ms
right_top.png
21 ms
left_bottom.png
24 ms
right_bottom.png
25 ms
shadow.png
12 ms
r
19554 ms
BgsBean.getBgsUserByUserId.dwr
770 ms
ava.s
354 ms
ava.s
5650 ms
ava.s
1065 ms
ava.s
3149 ms
ava.s
941 ms
ava.s
4568 ms
ava.s
1411 ms
ava.s
1796 ms
ava.s
1812 ms
close2.png
15 ms
souvr11.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 Souvr11.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 Souvr11.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.
souvr11.blog.163.com
Open Graph description is not detected on the main page of Souvr 11 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: