26.9 sec in total
2.2 sec
24.6 sec
208 ms
Welcome to 7.blog.163.com homepage info - get ready to check 7 Blog 163 best content for China right away, or after learning these important things about 7.blog.163.com
Visit 7.blog.163.comWe analyzed 7.blog.163.com page load time and found that the first response time was 2.2 sec and then it took 24.8 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 were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
7.blog.163.com performance score
2177 ms
1089 ms
1047 ms
788 ms
1024 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original 7.blog.163.com, 41% (18 requests) were made to B.bst.126.net and 16% (7 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Lofter.com.
Page size can be reduced by 527.8 kB (65%)
806.4 kB
278.5 kB
In fact, the total size of 7.blog.163.com main page is 806.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. 20% of websites need less resources to load. Javascripts take 449.1 kB which makes up the majority of the site volume.
Potential reduce by 58.6 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 58.6 kB or 78% of the original size.
Potential reduce by 10.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. 7 Blog 163 images are well optimized though.
Potential reduce by 310.4 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.4 kB or 69% of the original size.
Potential reduce by 148.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. 7.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.5 kB or 82% of the original size.
Number of requests can be reduced by 20 (53%)
38
18
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 7 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 4 to 1 for JavaScripts and as a result speed up the page load time.
7.blog.163.com
2177 ms
c.css
1089 ms
nb.css
1047 ms
6630133180817252049.jpg
788 ms
1.0.0.js
1024 ms
xcode.png
682 ms
pc.js
325 ms
ph.js
325 ms
top_bg.jpg
85 ms
icon.png
76 ms
lnkbar.png
134 ms
image.png
132 ms
arrow24.png
121 ms
newtopbaricon8.png
122 ms
bg_tab.jpg
76 ms
tab_on.gif
125 ms
bg_titlebar.gif
121 ms
bg_titlebar_c_l.gif
126 ms
bg_titlebar_c_r.gif
123 ms
bg_bottom.gif
143 ms
crossdomain.html
19778 ms
crossdomain.html
770 ms
crossdomain.html
757 ms
request.s
2241 ms
analyse.png
19753 ms
ava.s
1499 ms
ava.s
1980 ms
loftericon.png
444 ms
analyse.png
20481 ms
analytics.js
68 ms
collect
54 ms
UserSpaceBean.getUserSpace.dwr
5080 ms
blogPhotoAd
20272 ms
close_01.png
55 ms
top_bg.png
54 ms
bottom_bg.png
50 ms
left_bg.png
51 ms
right_bg.png
53 ms
left_top.png
49 ms
right_top.png
55 ms
left_bottom.png
54 ms
right_bottom.png
52 ms
shadow.png
48 ms
sniff.png
3011 ms
7.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 7.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 7.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.
7.blog.163.com
Open Graph description is not detected on the main page of 7 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: