31.6 sec in total
6.3 sec
24.3 sec
1.1 sec
Click here to check amazing Dxz 506 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about dxz506.blog.163.com
Visit dxz506.blog.163.comWe analyzed Dxz506.blog.163.com page load time and found that the first response time was 6.3 sec and then it took 25.4 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 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
dxz506.blog.163.com performance score
6263 ms
98 ms
1085 ms
19862 ms
159 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dxz506.blog.163.com, 39% (60 requests) were made to Os.blog.163.com and 23% (35 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 632.1 kB (49%)
1.3 MB
667.7 kB
In fact, the total size of Dxz506.blog.163.com main page is 1.3 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 521.3 kB which makes up the majority of the site volume.
Potential reduce by 113.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 113.0 kB or 80% 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. Dxz 506 Blog 163 images are well optimized though.
Potential reduce by 358.3 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.3 kB or 69% of the original size.
Potential reduce by 150.6 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. Dxz506.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.6 kB or 82% of the original size.
Number of requests can be reduced by 46 (31%)
147
101
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dxz 506 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 15 to 1 for JavaScripts and as a result speed up the page load time.
dxz506.blog.163.com
6263 ms
c.css
98 ms
b.css
1085 ms
5774459147219359392.jpg
19862 ms
icon.png
159 ms
5792473545728813558.jpg
19828 ms
5791629120798681638.jpg
19828 ms
5792473545728813445.jpg
19827 ms
5792473545728813447.jpg
19828 ms
5792473545728813446.jpg
19828 ms
lnkbar.png
126 ms
image.png
20 ms
6630133180817252049.jpg
866 ms
xcode.png
362 ms
1.0.0.js
170 ms
pc.js
377 ms
ph.js
377 ms
arrow24.png
32 ms
newtopbaricon8.png
39 ms
crossdomain.html
2584 ms
crossdomain.html
1853 ms
request.s
856 ms
analyse.png
850 ms
empty.png
94 ms
ava.s
967 ms
nb.css
56 ms
crossdomain.html
861 ms
ava.s
708 ms
background.gif
26 ms
player_02.gif
35 ms
player_06.gif
35 ms
player_16.gif
73 ms
player_17.gif
32 ms
stopping.gif
38 ms
player_23.gif
39 ms
timeline_1.gif
40 ms
player_29.gif
67 ms
analyse.png
811 ms
analytics.js
48 ms
collect
22 ms
blogPhotoAd
441 ms
close_01.png
37 ms
top_bg.png
39 ms
bottom_bg.png
37 ms
left_bg.png
35 ms
right_bg.png
36 ms
left_top.png
39 ms
right_top.png
52 ms
left_bottom.png
52 ms
right_bottom.png
53 ms
shadow.png
38 ms
r
877 ms
UserBeanNew.getVisitor.dwr
8821 ms
NoteBeanNew.getNotesForPrev.dwr
10747 ms
MusicBeanNew.getPlayList.dwr
1491 ms
HomeBeanNew.getClassifyModuleData.dwr
1187 ms
LikePictureBean.getLatestLikePictureList.dwr
812 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1344 ms
UserFollowBeanNew.getUserFollows.dwr
1592 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1876 ms
ad
828 ms
close2.png
59 ms
1058345912450189648.jpg
211 ms
6631343743122441876.jpg
215 ms
6631266777308717251.jpg
1780 ms
6630282714396709424.jpg
218 ms
6630375073373489861.jpg
207 ms
6631243687564905746.jpg
212 ms
6631283269982507975.jpg
211 ms
6599283083563855748.jpg
235 ms
6630722519050183814.jpg
274 ms
6597295166541916890.jpg
214 ms
6619580068212343089.jpg
205 ms
6608525578306413858.jpg
216 ms
6597988958378949843.jpg
215 ms
6631421808447566436.jpg
229 ms
6598245144646876332.jpg
271 ms
4860228422963402890.jpg
1772 ms
6598134093972461197.jpg
1786 ms
2019582957999224101.jpg
1788 ms
jquery-1.4.2.js
12 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
2310 ms
HomeBeanNew.getFriends.dwr
3619 ms
ava.s
503 ms
face22.gif
19 ms
face73.gif
21 ms
list_line.gif
38 ms
ava.s
1918 ms
ava.s
3718 ms
ava.s
768 ms
ava.s
782 ms
ava.s
849 ms
ava.s
1154 ms
ava.s
1198 ms
ava.s
2550 ms
ava.s
1874 ms
ava.s
3437 ms
ava.s
2059 ms
ava.s
2284 ms
ava.s
2339 ms
ava.s
2556 ms
ava.s
2667 ms
ava.s
2736 ms
ava.s
2980 ms
ava.s
3076 ms
ava.s
3061 ms
ava.s
3134 ms
ava.s
3417 ms
ava.s
380 ms
ava.s
2265 ms
ava.s
459 ms
ava.s
746 ms
ava.s
1873 ms
ava.s
776 ms
ava.s
832 ms
ava.s
1154 ms
ava.s
4033 ms
ava.s
1131 ms
ava.s
1207 ms
ava.s
1536 ms
ava.s
2799 ms
ava.s
1606 ms
ava.s
1944 ms
ava.s
1996 ms
ava.s
2345 ms
ava.s
2365 ms
ava.s
2392 ms
ava.s
2799 ms
ava.s
1044 ms
ava.s
406 ms
ava.s
762 ms
ava.s
367 ms
ava.s
6203 ms
ava.s
1654 ms
ava.s
1898 ms
ava.s
783 ms
ava.s
1125 ms
ava.s
1183 ms
ava.s
2009 ms
ava.s
1543 ms
ava.s
2636 ms
ava.s
1939 ms
ava.s
2476 ms
face51.gif
34 ms
face50.gif
30 ms
face50.gif
34 ms
face58.gif
32 ms
face82.gif
33 ms
face5.gif
31 ms
face20.gif
47 ms
face25.gif
46 ms
face1.gif
55 ms
face30.gif
53 ms
face39.gif
58 ms
dxz506.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 Dxz506.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 Dxz506.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.
dxz506.blog.163.com
Open Graph description is not detected on the main page of Dxz 506 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: