16.2 sec in total
1.9 sec
13.7 sec
510 ms
Welcome to qianxunhubei.blog.163.com homepage info - get ready to check Qianxunhubei Blog 163 best content for China right away, or after learning these important things about qianxunhubei.blog.163.com
Visit qianxunhubei.blog.163.comWe analyzed Qianxunhubei.blog.163.com page load time and found that the first response time was 1.9 sec and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
qianxunhubei.blog.163.com performance score
1949 ms
9 ms
653 ms
2953 ms
1373 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Qianxunhubei.blog.163.com, 13% (10 requests) were made to Img0.ph.126.net and 13% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 601.6 kB (38%)
1.6 MB
965.4 kB
In fact, the total size of Qianxunhubei.blog.163.com main page is 1.6 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 755.4 kB which makes up the majority of the site volume.
Potential reduce by 83.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 83.8 kB or 78% of the original size.
Potential reduce by 10.1 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. Qianxunhubei Blog 163 images are well optimized though.
Potential reduce by 358.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 358.4 kB or 69% of the original size.
Potential reduce by 149.3 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. Qianxunhubei.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.3 kB or 82% of the original size.
Number of requests can be reduced by 25 (34%)
74
49
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qianxunhubei 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 as a result speed up the page load time.
qianxunhubei.blog.163.com
1949 ms
c.css
9 ms
b.css
653 ms
6598245144587341366.jpg
2953 ms
6597852618936443172.jpg
1373 ms
6597365535284812183.jpg
2867 ms
6630133180817252049.jpg
4061 ms
xcode.png
7 ms
1.0.0.js
386 ms
pc.js
207 ms
ph.js
8 ms
6597241290472398276.jpg
1700 ms
2866822637815247240.jpg
4796 ms
6597183016354734431.jpg
2922 ms
2561985238037241088.jpg
1149 ms
icon.png
37 ms
lnkbar.png
35 ms
image.png
35 ms
arrow24.png
36 ms
newtopbaricon8.png
37 ms
1204431425361759529.jpg
6367 ms
5776147997081614507.jpg
2972 ms
5776147997081614509.jpg
3352 ms
2561985238037241089.jpg
2172 ms
5773614722291213731.jpg
2757 ms
5784873721358788345.jpg
4991 ms
crossdomain.html
831 ms
crossdomain.html
1254 ms
crossdomain.html
2134 ms
request.s
705 ms
analyse.png
1308 ms
ava.s
681 ms
loftericon.png
406 ms
ava.s
734 ms
analyse.png
1249 ms
analytics.js
6 ms
collect
13 ms
SetupBeanNew.getCustomModulesData.dwr
855 ms
NoteBeanNew.getNotesForPrev.dwr
1292 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1319 ms
blogPhotoAd
632 ms
close_01.png
7 ms
top_bg.png
7 ms
bottom_bg.png
6 ms
left_bg.png
9 ms
right_bg.png
10 ms
left_top.png
9 ms
right_top.png
6 ms
left_bottom.png
11 ms
right_bottom.png
10 ms
shadow.png
7 ms
LikePictureBean.getLatestLikePictureList.dwr
1372 ms
r
1230 ms
6631219498308725113.jpg
71 ms
6631442699169762713.jpg
145 ms
6598113203251074374.jpg
137 ms
6631383325540968554.jpg
139 ms
1995094635025781060.jpg
143 ms
4852628598592258480.jpg
72 ms
6631449296239086769.jpg
138 ms
6631293165587386729.jpg
140 ms
6630876450678543211.jpg
139 ms
6598062625715957653.jpg
140 ms
6597886703797967005.jpg
143 ms
6598241846111879970.jpg
70 ms
6630447641140460538.jpg
71 ms
6631295364608010057.jpg
146 ms
6598248443180999703.jpg
144 ms
6597993356425756452.jpg
144 ms
6631309658262534861.jpg
145 ms
1413004383187776876.jpg
142 ms
close2.png
4 ms
ad
5873 ms
jquery-1.4.2.js
8 ms
0316ykt-300-250.jpg
2092 ms
qianxunhubei.blog.163.com SEO score
JA
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qianxunhubei.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Qianxunhubei.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.
qianxunhubei.blog.163.com
Open Graph description is not detected on the main page of Qianxunhubei 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: