37.8 sec in total
7.6 sec
29.8 sec
396 ms
Welcome to qy-0824.blog.163.com homepage info - get ready to check Qy 0824 Blog 163 best content for China right away, or after learning these important things about qy-0824.blog.163.com
Visit qy-0824.blog.163.comWe analyzed Qy-0824.blog.163.com page load time and found that the first response time was 7.6 sec and then it took 30.2 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. 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.
qy-0824.blog.163.com performance score
7632 ms
36 ms
28 ms
62 ms
212 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Qy-0824.blog.163.com, 35% (19 requests) were made to B.bst.126.net and 13% (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 551.7 kB (60%)
914.7 kB
363.0 kB
In fact, the total size of Qy-0824.blog.163.com main page is 914.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. 30% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 83.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 83.6 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. Qy 0824 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 148.4 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. Qy-0824.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.4 kB or 82% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qy 0824 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 9 to 1 for JavaScripts and as a result speed up the page load time.
qy-0824.blog.163.com
7632 ms
c.css
36 ms
nb.css
28 ms
bgtop.jpg
62 ms
topbg.jpg
212 ms
bg.gif
74 ms
bg2.jpg
138 ms
1bt.gif
78 ms
icon.png
40 ms
bottombg.jpg
37 ms
6630133180817252049.jpg
809 ms
lnkbar.png
35 ms
image.png
36 ms
arrow24.png
36 ms
newtopbaricon8.png
35 ms
xcode.png
32 ms
1.0.0.js
383 ms
pc.js
40 ms
ph.js
39 ms
crossdomain.html
816 ms
crossdomain.html
725 ms
request.s
688 ms
analyse.png
19724 ms
empty.png
60 ms
2050263730361464728.gif
3761 ms
2477261270047476889.gif
907 ms
1322087965627033256.gif
637 ms
1170935903133440103.png
19695 ms
1074671461098814200.gif
670 ms
ava.s
2729 ms
crossdomain.html
1360 ms
ava.s
2237 ms
analyse.png
20451 ms
analytics.js
24 ms
collect
39 ms
SetupBeanNew.getCustomModulesData.dwr
965 ms
HomeBeanNew.getAccessStatistics.dwr
1384 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1406 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1553 ms
blogPhotoAd
20254 ms
close_01.png
46 ms
top_bg.png
32 ms
bottom_bg.png
40 ms
left_bg.png
34 ms
right_bg.png
36 ms
left_top.png
57 ms
right_top.png
59 ms
left_bottom.png
60 ms
right_bottom.png
59 ms
shadow.png
34 ms
pt.gif
222 ms
pt2-zh.gif
221 ms
BgsBean.getBgsUserByUserId.dwr
2196 ms
face0.gif
34 ms
qy-0824.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 Qy-0824.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 Qy-0824.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.
qy-0824.blog.163.com
Open Graph description is not detected on the main page of Qy 0824 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: