22.8 sec in total
6.4 sec
15.5 sec
831 ms
Welcome to whbsjwcwh.blog.163.com homepage info - get ready to check Whbsjwcwh Blog 163 best content for China right away, or after learning these important things about whbsjwcwh.blog.163.com
Visit whbsjwcwh.blog.163.comWe analyzed Whbsjwcwh.blog.163.com page load time and found that the first response time was 6.4 sec and then it took 16.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whbsjwcwh.blog.163.com performance score
6443 ms
28 ms
3804 ms
516 ms
28 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whbsjwcwh.blog.163.com, 22% (23 requests) were made to Os.blog.163.com and 20% (21 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source Os.blog.163.com.
Page size can be reduced by 644.3 kB (54%)
1.2 MB
548.4 kB
In fact, the total size of Whbsjwcwh.blog.163.com main page is 1.2 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. 30% of websites need less resources to load. Javascripts take 522.3 kB which makes up the majority of the site volume.
Potential reduce by 120.2 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 120.2 kB or 82% of the original size.
Potential reduce by 13.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. Whbsjwcwh Blog 163 images are well optimized though.
Potential reduce by 358.7 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.7 kB or 69% of the original size.
Potential reduce by 152.0 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. Whbsjwcwh.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.
Number of requests can be reduced by 55 (53%)
104
49
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whbsjwcwh 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 17 to 1 for JavaScripts and as a result speed up the page load time.
whbsjwcwh.blog.163.com
6443 ms
c.css
28 ms
b.css
3804 ms
6630133180817252049.jpg
516 ms
xcode.png
28 ms
1.0.0.js
85 ms
5771362922476033220.jpg
1393 ms
icon.png
192 ms
5786281096241579454.jpg
470 ms
5786281096241579548.jpg
475 ms
5777273896986971857.jpg
576 ms
5777273896986971856.jpg
579 ms
5777273896986971858.jpg
578 ms
5771362922476033234.jpg
732 ms
5777273896986971859.jpg
753 ms
5777273896986971860.jpg
973 ms
5777273896986971861.jpg
974 ms
5777273896986971863.jpg
974 ms
5777273896986971862.jpg
996 ms
5777273896986971843.jpg
1017 ms
5786281096241579671.jpg
1129 ms
5786281096241579672.jpg
1136 ms
5771362922476033225.jpg
1131 ms
5786281096241579673.jpg
1183 ms
5777273896986971849.jpg
1249 ms
5786281096241579675.jpg
1411 ms
5786281096241579678.jpg
1416 ms
5786281096241579676.jpg
1418 ms
rssi.png
133 ms
blog_rec.png
135 ms
lnkbar.png
134 ms
image.png
132 ms
arrow24.png
137 ms
newtopbaricon8.png
134 ms
pc.js
141 ms
ph.js
219 ms
crossdomain.html
822 ms
crossdomain.html
524 ms
request.s
462 ms
analyse.png
498 ms
empty.png
117 ms
6598164880298755329.jpg
1555 ms
4844747299244603711.jpg
522 ms
ava.s
6116 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
532 ms
nb.css
39 ms
crossdomain.html
490 ms
ava.s
2532 ms
background.gif
28 ms
player_02.gif
30 ms
player_06.gif
37 ms
player_16.gif
34 ms
player_17.gif
34 ms
player_23.gif
32 ms
timeline_1.gif
36 ms
player_29.gif
34 ms
analyse.png
450 ms
analytics.js
16 ms
collect
14 ms
UserSpaceBean.getUserSpace.dwr
581 ms
HomeBeanNew.getFriends.dwr
932 ms
HomeBeanNew.getAccessStatistics.dwr
1295 ms
HomeBeanNew.getMonthStatistics.dwr
1212 ms
HomeBeanNew.getWeatherCityCode.dwr
2472 ms
NoteBeanNew.getNotesForPrev.dwr
4998 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1465 ms
29686824004232.js
168 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1620 ms
blogPhotoAd
245 ms
close_01.png
16 ms
top_bg.png
13 ms
bottom_bg.png
15 ms
left_bg.png
14 ms
right_bg.png
36 ms
left_top.png
20 ms
right_top.png
17 ms
left_bottom.png
17 ms
right_bottom.png
36 ms
shadow.png
27 ms
r
478 ms
ava.s
849 ms
ava.s
6951 ms
ava.s
2549 ms
ava.s
1169 ms
ava.s
1266 ms
ava.s
1580 ms
ava.s
1646 ms
ava.s
1987 ms
ava.s
3519 ms
ava.s
2030 ms
ava.s
4482 ms
ava.s
2436 ms
ava.s
2877 ms
ava.s
2945 ms
ava.s
3283 ms
ava.s
4950 ms
ava.s
3689 ms
ava.s
3914 ms
ava.s
4095 ms
ava.s
4318 ms
ad
526 ms
BgsBean.getBgsUserByUserId.dwr
882 ms
jquery-1.4.2.js
22 ms
close2.png
9 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
2342 ms
.gif
1454 ms
whbsjwcwh.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 Whbsjwcwh.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 Whbsjwcwh.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.
whbsjwcwh.blog.163.com
Open Graph description is not detected on the main page of Whbsjwcwh 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: