21.7 sec in total
3 sec
17.6 sec
1.1 sec
Visit qq8810829.blog.163.com now to see the best up-to-date Qq 8810829 Blog 163 content for China and also check out these interesting facts you probably never knew about qq8810829.blog.163.com
Visit qq8810829.blog.163.comWe analyzed Qq8810829.blog.163.com page load time and found that the first response time was 3 sec and then it took 18.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.
qq8810829.blog.163.com performance score
2979 ms
23 ms
20 ms
1523 ms
1715 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Qq8810829.blog.163.com, 29% (24 requests) were made to Os.blog.163.com and 24% (20 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (8.1 sec) relates to the external source Os.blog.163.com.
Page size can be reduced by 622.7 kB (63%)
993.7 kB
371.0 kB
In fact, the total size of Qq8810829.blog.163.com main page is 993.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. 50% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.
Potential reduce by 106.0 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 106.0 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. Qq 8810829 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. Qq8810829.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 33 (43%)
77
44
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qq 8810829 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 14 to 1 for JavaScripts and as a result speed up the page load time.
qq8810829.blog.163.com
2979 ms
c.css
23 ms
nb.css
20 ms
20071015_6d204db221af353d739bDas1DJbh0JlI.jpg
1523 ms
20071015_e6f6b0e94bfa97ba2c39JEgn1bcapstX.jpg
1715 ms
20071015_a22e78dc62212e9f835dMAVLtrWcnq3D.jpg
1898 ms
20071015_3356c07158ba739e02f6YAOTnkB9fFkO.jpg
2202 ms
ding-shang01.jpg
130 ms
icon.png
110 ms
daohang-di01.gif
110 ms
ding-shang02.jpg
115 ms
0001_neir_zhong.jpg
113 ms
0001_neir_zuo.jpg
111 ms
0001_neir_you.jpg
108 ms
0001_neirong_xiazuo.jpg
110 ms
0001_neirong_xiayou.jpg
111 ms
icon_copy.gif
2372 ms
0001_xia_01.jpg
34 ms
lnkbar.png
33 ms
6630133180817252049.jpg
1862 ms
1.0.0.js
103 ms
pc.js
29 ms
ph.js
32 ms
xcode.png
16 ms
image.png
7 ms
arrow24.png
7 ms
newtopbaricon8.png
11 ms
crossdomain.html
909 ms
crossdomain.html
3095 ms
crossdomain.html
3511 ms
request.s
915 ms
analyse.png
787 ms
ava.s
902 ms
loftericon.png
441 ms
ava.s
2342 ms
analyse.png
900 ms
analytics.js
18 ms
collect
15 ms
HomeBeanNew.getFriends.dwr
5527 ms
HomeBeanNew.getAccessStatistics.dwr
1412 ms
UserBeanNew.getVisitor.dwr
1495 ms
NoteBeanNew.getNotesForPrev.dwr
1962 ms
HomeBeanNew.getClassifyModuleData.dwr
3848 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
2323 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2313 ms
blogPhotoAd
408 ms
close_01.png
20 ms
top_bg.png
19 ms
bottom_bg.png
17 ms
left_bg.png
17 ms
right_bg.png
18 ms
left_top.png
16 ms
right_top.png
21 ms
left_bottom.png
21 ms
right_bottom.png
20 ms
shadow.png
16 ms
r
1680 ms
BgsBean.getBgsUserByUserId.dwr
1048 ms
ava.s
936 ms
ava.s
2228 ms
ava.s
2654 ms
ava.s
5673 ms
ava.s
1315 ms
ava.s
1397 ms
ava.s
2006 ms
ava.s
3470 ms
ava.s
1984 ms
ava.s
4921 ms
ava.s
2687 ms
ava.s
6103 ms
ava.s
3547 ms
ava.s
3336 ms
ava.s
6140 ms
close2.png
3 ms
ad
768 ms
jquery-1.4.2.js
44 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
2847 ms
ava.s
1572 ms
ava.s
1896 ms
ava.s
472 ms
ava.s
962 ms
ava.s
1411 ms
ava.s
8069 ms
ava.s
3562 ms
qq8810829.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 Qq8810829.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 Qq8810829.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.
qq8810829.blog.163.com
Open Graph description is not detected on the main page of Qq 8810829 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: