16.6 sec in total
1.5 sec
14.4 sec
618 ms
Visit wydzx2005.blog.163.com now to see the best up-to-date Wydzx 2005 Blog 163 content for China and also check out these interesting facts you probably never knew about wydzx2005.blog.163.com
Visit wydzx2005.blog.163.comWe analyzed Wydzx2005.blog.163.com page load time and found that the first response time was 1.5 sec and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wydzx2005.blog.163.com performance score
1545 ms
799 ms
794 ms
798 ms
1627 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wydzx2005.blog.163.com, 34% (36 requests) were made to Os.blog.163.com and 31% (33 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source Os.blog.163.com.
Page size can be reduced by 629.3 kB (57%)
1.1 MB
483.9 kB
In fact, the total size of Wydzx2005.blog.163.com main page is 1.1 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.7 kB which makes up the majority of the site volume.
Potential reduce by 110.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 110.6 kB or 81% of the original size.
Potential reduce by 10.8 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. Wydzx 2005 Blog 163 images are well optimized though.
Potential reduce by 358.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 358.5 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. Wydzx2005.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 51 (49%)
104
53
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wydzx 2005 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 16 to 1 for JavaScripts and as a result speed up the page load time.
wydzx2005.blog.163.com
1545 ms
c.css
799 ms
nb.css
794 ms
6630133180817252049.jpg
798 ms
1.0.0.js
1627 ms
pc.js
525 ms
ph.js
523 ms
xcode.png
428 ms
mode01_02.jpg
1284 ms
icon.png
62 ms
lnkbar.png
63 ms
image.png
63 ms
arrow24.png
63 ms
newtopbaricon8.png
64 ms
mode01_01.jpg
65 ms
mode01_15.gif
64 ms
mode01_12.gif
63 ms
mode01_07.jpg
1873 ms
mode01_10.jpg
64 ms
crossdomain.html
846 ms
crossdomain.html
559 ms
crossdomain.html
783 ms
request.s
1287 ms
analyse.png
478 ms
ava.s
873 ms
loftericon.png
338 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
546 ms
nb.css
20 ms
ava.s
1260 ms
background.gif
6 ms
player_02.gif
4 ms
player_06.gif
6 ms
player_16.gif
19 ms
player_17.gif
5 ms
player_23.gif
8 ms
timeline_1.gif
9 ms
player_29.gif
10 ms
analyse.png
436 ms
analytics.js
26 ms
collect
15 ms
HomeBeanNew.getFriends.dwr
943 ms
HomeBeanNew.getAccessStatistics.dwr
1126 ms
HomeBeanNew.getMonthStatistics.dwr
1256 ms
UserBeanNew.getVisitor.dwr
2615 ms
NoteBeanNew.getNotesForPrev.dwr
1828 ms
HomeBeanNew.getClassifyModuleData.dwr
1957 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
7361 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2127 ms
blogPhotoAd
244 ms
close_01.png
10 ms
top_bg.png
13 ms
bottom_bg.png
9 ms
left_bg.png
10 ms
right_bg.png
14 ms
left_top.png
10 ms
right_top.png
13 ms
left_bottom.png
14 ms
right_bottom.png
14 ms
shadow.png
10 ms
r
603 ms
ava.s
457 ms
ava.s
2225 ms
ava.s
689 ms
ava.s
1874 ms
ava.s
2759 ms
ava.s
1133 ms
ava.s
1487 ms
ava.s
1898 ms
ava.s
1824 ms
ava.s
2088 ms
ava.s
2176 ms
ava.s
3362 ms
ava.s
2334 ms
ava.s
2516 ms
ava.s
2525 ms
ava.s
4508 ms
ava.s
2777 ms
ava.s
2948 ms
ava.s
2965 ms
ava.s
7419 ms
BgsBean.getBgsUserByUserId.dwr
1208 ms
ad
692 ms
close2.png
25 ms
face56.gif
98 ms
face70.gif
110 ms
face51.gif
107 ms
face50.gif
109 ms
face50.gif
107 ms
face51.gif
108 ms
face73.gif
190 ms
ava.s
2194 ms
jquery-1.4.2.js
1150 ms
ava.s
1682 ms
ava.s
2931 ms
ava.s
2010 ms
ava.s
3953 ms
ava.s
2111 ms
ava.s
2484 ms
ava.s
6103 ms
ava.s
2954 ms
ava.s
3313 ms
ava.s
4151 ms
ava.s
3906 ms
ava.s
3787 ms
ava.s
7635 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
4177 ms
wydzx2005.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 Wydzx2005.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 Wydzx2005.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.
wydzx2005.blog.163.com
Open Graph description is not detected on the main page of Wydzx 2005 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: