10.3 sec in total
2.3 sec
7.5 sec
528 ms
Click here to check amazing Zhedahht Blog 163 content for China. Otherwise, check out these important facts you probably never knew about zhedahht.blog.163.com
程序员面试题精选100题(73)-最多转机K次的最便宜航线[算法],程序员面试题精选100题(66)-开密码锁[算法],程序员面试题精选100题(61)-数对之差的最大值[算法],程序员面试题精选100题(60)-判断二叉树是不是平衡[数据结构],程序员面试题精选100题(59)-字符串的组合[算法],程序员面试题精选100题(57)-O(n)时间的排序[算法],程序员面试题精选100题(56)-...
Visit zhedahht.blog.163.comWe analyzed Zhedahht.blog.163.com page load time and found that the first response time was 2.3 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
zhedahht.blog.163.com performance score
2310 ms
83 ms
72 ms
781 ms
105 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Zhedahht.blog.163.com, 31% (20 requests) were made to B.bst.126.net and 13% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Os.blog.163.com.
Page size can be reduced by 783.5 kB (63%)
1.2 MB
453.0 kB
In fact, the total size of Zhedahht.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. 40% of websites need less resources to load. Javascripts take 643.4 kB which makes up the majority of the site volume.
Potential reduce by 80.9 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 80.9 kB or 81% of the original size.
Potential reduce by 89.0 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. Obviously, Zhedahht Blog 163 needs image optimization as it can save up to 89.0 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 436.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 436.4 kB or 68% of the original size.
Potential reduce by 177.2 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. Zhedahht.blog.163.com needs all CSS files to be minified and compressed as it can save up to 177.2 kB or 82% of the original size.
Number of requests can be reduced by 33 (52%)
63
30
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zhedahht 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 from 4 to 1 for CSS and as a result speed up the page load time.
zhedahht.blog.163.com
2310 ms
c.css
83 ms
nb.css
72 ms
6630133180817252049.jpg
781 ms
xcode.png
105 ms
icon.png
31 ms
lnkbar.png
44 ms
image.png
44 ms
arrow24.png
42 ms
newtopbaricon8.png
78 ms
top.jpg
63 ms
menu_bt.jpg
31 ms
bg_m01.jpg
56 ms
bg_l01.jpg
55 ms
bg_r01.jpg
237 ms
bg_l02.jpg
89 ms
bg_r02.jpg
103 ms
bg_m02.jpg
90 ms
down.jpg
90 ms
pc.js
55 ms
ph.js
58 ms
1.0.0.js
122 ms
crossdomain.html
725 ms
crossdomain.html
1114 ms
crossdomain.html
2693 ms
request.s
790 ms
analyse.png
821 ms
ava.s
2940 ms
loftericon.png
1474 ms
analyse.png
905 ms
analytics.js
162 ms
collect
81 ms
SetupBeanNew.getCustomModulesData.dwr
680 ms
SetupBeanNew.getResourceModulesData.dwr
1055 ms
HomeBeanNew.getAccessStatistics.dwr
1305 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1330 ms
blogPhotoAd
355 ms
close_01.png
10 ms
top_bg.png
14 ms
bottom_bg.png
15 ms
left_bg.png
16 ms
right_bg.png
17 ms
left_top.png
16 ms
right_top.png
17 ms
left_bottom.png
18 ms
right_bottom.png
20 ms
shadow.png
16 ms
index.php
964 ms
r
815 ms
BgsBean.getBgsUserByUserId.dwr
705 ms
weiboShow.css
29 ms
skin_default.css
24 ms
gaea_1_19.js
34 ms
show.js
1745 ms
suda.js
1021 ms
1
1283 ms
btns_bg.png
11 ms
icon_follow.png
10 ms
ad
920 ms
close2.png
10 ms
jquery-1.4.2.js
55 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1321 ms
bg_trans.png
22 ms
icon_tips.png
16 ms
zhedahht.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 Zhedahht.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 Zhedahht.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.
zhedahht.blog.163.com
Open Graph description is not detected on the main page of Zhedahht 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: