27.5 sec in total
2.4 sec
24.8 sec
304 ms
Visit cmt2012.blog.163.com now to see the best up-to-date Cmt 2012 Blog 163 content for China and also check out these interesting facts you probably never knew about cmt2012.blog.163.com
Visit cmt2012.blog.163.comWe analyzed Cmt2012.blog.163.com page load time and found that the first response time was 2.4 sec and then it took 25.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 were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
cmt2012.blog.163.com performance score
2397 ms
116 ms
777 ms
1888 ms
136 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cmt2012.blog.163.com, 15% (14 requests) were made to Img.bimg.126.net and 13% (12 requests) were made to Img.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 686.2 kB (33%)
2.1 MB
1.4 MB
In fact, the total size of Cmt2012.blog.163.com main page is 2.1 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 44.8 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 44.8 kB or 78% of the original size.
Potential reduce by 74.7 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. Cmt 2012 Blog 163 images are well optimized though.
Potential reduce by 388.2 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 388.2 kB or 68% of the original size.
Potential reduce by 178.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. Cmt2012.blog.163.com needs all CSS files to be minified and compressed as it can save up to 178.5 kB or 82% of the original size.
Number of requests can be reduced by 40 (45%)
89
49
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cmt 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cmt2012.blog.163.com
2397 ms
c.css
116 ms
b.css
777 ms
6630133180817252049.jpg
1888 ms
xcode.png
136 ms
1.0.0.js
134 ms
pc.js
162 ms
ph.js
139 ms
5735052650480244034.jpg
19584 ms
icon.png
53 ms
5744341324711680744.jpg
19578 ms
5756726223686914307.jpg
2453 ms
3736017365881523630.jpg
687 ms
5756726223686914311.jpg
749 ms
5744341324711680992.jpg
711 ms
5756726223686914313.jpg
1102 ms
5735052650480244041.jpg
4019 ms
5756726223686914315.jpg
1186 ms
5756726223686914317.jpg
1560 ms
5756726223686914319.jpg
2517 ms
5756726223686914323.jpg
2008 ms
5756726223686914321.jpg
17728 ms
5756726223686914305.jpg
3384 ms
lnkbar.png
157 ms
image.png
156 ms
arrow24.png
155 ms
newtopbaricon8.png
155 ms
crossdomain.html
728 ms
crossdomain.html
944 ms
request.s
749 ms
analyse.png
982 ms
crossdomain.html
719 ms
analyse.png
989 ms
analytics.js
100 ms
collect
77 ms
SetupBeanNew.getCustomModulesData.dwr
745 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1336 ms
blogPhotoAd
491 ms
close_01.png
47 ms
top_bg.png
79 ms
bottom_bg.png
78 ms
left_bg.png
77 ms
right_bg.png
78 ms
left_top.png
79 ms
right_top.png
78 ms
left_bottom.png
105 ms
right_bottom.png
105 ms
shadow.png
44 ms
6619089686026528586.jpg
1330 ms
index.php
2003 ms
r
19506 ms
T1uUG.XjtkXXcb2gzo-77-19.gif
377 ms
T1FXHXXahjXXXAK3zo-77-18.gif
1058 ms
close2.png
28 ms
weiboShow.css
1631 ms
skin_default.css
1636 ms
gaea_1_19.js
114 ms
show.js
3062 ms
suda.js
5322 ms
0
505 ms
c7cea93cgw1f2o4cbjq6uj20qo0zk44u.jpg
870 ms
moon.gif
1222 ms
67c6f665gw1f2ndwkwcehj20qo0qogra.jpg
940 ms
b8a18fe9gw1f2o4g1jek7j20ku0kugna.jpg
1053 ms
97d03b8bgw1f2paxbv8wkj20m80m8ahy.jpg
843 ms
heart.gif
2633 ms
shame_org.gif
2774 ms
6c8f44e6jw1f2o9h8dmxbj20ku1rdgua.jpg
828 ms
97d03b8bgw1f2pa5uq2ptj20ku08pmza.jpg
733 ms
70783d84gw1f2oshjmllnj214f11pdsu.jpg
578 ms
6113b802jw1f2lsefnm6rj20qo0zkq5k.jpg
829 ms
97d03b8bgw1f2p9z58l4fj20j60eetb7.jpg
824 ms
97d03b8bgw1f2p9aob36zj20m80m8dj5.jpg
1024 ms
97d03b8bgw1f2p99yp9txj20m80xc45q.jpg
1123 ms
70783d84gw1f2osljbkk3j20m80rs455.jpg
905 ms
006dznEkjw1f2pbkkqpcxj30ku0rs0z3.jpg
1010 ms
97d03b8bgw1f2n9mkjbopj20c80c9my5.jpg
1011 ms
6837363egw1f2p5agr0v3j20ku0ozn23.jpg
1011 ms
wb_logo16_a.png
150 ms
icon_user.png
150 ms
btns_bg.png
151 ms
icon_follow.png
152 ms
love.gif
152 ms
m_org.gif
247 ms
mb_org.gif
249 ms
x_org.gif
249 ms
006dznEkjw1f2p448g7m0j30qo0yx799.jpg
820 ms
97d03b8bgw1f2na1yln7sj20i20i2753.jpg
817 ms
70783d84gw1f2os89g886j21kw18xtuj.jpg
818 ms
bg_trans.png
96 ms
icon_tips.png
83 ms
tmp.gif
1283 ms
a.gif
1141 ms
cmt2012.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 Cmt2012.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 Cmt2012.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.
cmt2012.blog.163.com
Open Graph description is not detected on the main page of Cmt 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: