42.5 sec in total
4.4 sec
37.7 sec
346 ms
Visit wnxingxing2010.blog.163.com now to see the best up-to-date Wnxingxing 2010 Blog 163 content for China and also check out these interesting facts you probably never knew about wnxingxing2010.blog.163.com
Visit wnxingxing2010.blog.163.comWe analyzed Wnxingxing2010.blog.163.com page load time and found that the first response time was 4.4 sec and then it took 38 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 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
wnxingxing2010.blog.163.com performance score
4426 ms
118 ms
12799 ms
4657 ms
198 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wnxingxing2010.blog.163.com, 28% (25 requests) were made to B.bst.126.net and 19% (17 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 688.2 kB (59%)
1.2 MB
484.7 kB
In fact, the total size of Wnxingxing2010.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 650.2 kB which makes up the majority of the site volume.
Potential reduce by 94.1 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 94.1 kB or 79% of the original size.
Potential reduce by 11.5 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. Wnxingxing 2010 Blog 163 images are well optimized though.
Potential reduce by 432.2 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 432.2 kB or 66% of the original size.
Potential reduce by 150.4 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. Wnxingxing2010.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.4 kB or 82% of the original size.
Number of requests can be reduced by 46 (56%)
82
36
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wnxingxing 2010 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 21 to 1 for JavaScripts and as a result speed up the page load time.
wnxingxing2010.blog.163.com
4426 ms
c.css
118 ms
b.css
12799 ms
6630133180817252049.jpg
4657 ms
xcode.png
198 ms
1.0.0.js
268 ms
pc.js
389 ms
ph.js
343 ms
5735334125456880022.jpg
20458 ms
icon.png
96 ms
5748000499408839014.jpg
20444 ms
5748000499408839012.jpg
20445 ms
5735334125456880023.jpg
20444 ms
5748000499408839013.jpg
20447 ms
lnkbar.png
230 ms
image.png
233 ms
arrow24.png
231 ms
newtopbaricon8.png
231 ms
crossdomain.html
2557 ms
crossdomain.html
4354 ms
crossdomain.html
997 ms
request.s
855 ms
analyse.png
947 ms
ava.s
976 ms
loftericon.png
767 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
807 ms
nb.css
51 ms
background.gif
37 ms
player_02.gif
95 ms
player_06.gif
95 ms
player_16.gif
99 ms
player_17.gif
98 ms
player_23.gif
102 ms
timeline_1.gif
147 ms
player_29.gif
168 ms
analyse.png
806 ms
analytics.js
44 ms
collect
29 ms
blogPhotoAd
518 ms
close_01.png
21 ms
top_bg.png
19 ms
bottom_bg.png
21 ms
left_bg.png
18 ms
right_bg.png
20 ms
left_top.png
20 ms
right_top.png
22 ms
left_bottom.png
23 ms
right_bottom.png
23 ms
shadow.png
20 ms
r
747 ms
HomeBeanNew.getFriends.dwr
2582 ms
HomeBeanNew.getAccessStatistics.dwr
1207 ms
HomeBeanNew.getMonthStatistics.dwr
2690 ms
HomeBeanNew.getWeatherCityCode.dwr
2649 ms
UserBeanNew.getVisitor.dwr
3126 ms
NoteBeanNew.getNotesForPrev.dwr
1216 ms
BlogBeanNew.getRecentCommentsByOffset.dwr
9780 ms
BlogBeanNew.getBlogClasses.dwr
11227 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
4833 ms
ad
800 ms
close2.png
36 ms
jquery-1.4.2.js
79 ms
SetupBeanNew.getCustomModulesData.dwr
2443 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
1847 ms
BgsBean.getBgsUserByUserId.dwr
2363 ms
face56.gif
79 ms
UserSpaceBean.getUserSpace.dwr
877 ms
.gif
84 ms
ava.s
1528 ms
ava.s
6634 ms
ava.s
6208 ms
ava.s
1036 ms
ava.s
1095 ms
ava.s
3977 ms
ava.s
1590 ms
ava.s
3964 ms
ava.s
2003 ms
ava.s
2125 ms
ava.s
2527 ms
ava.s
3956 ms
ava.s
4656 ms
ava.s
4502 ms
ava.s
14635 ms
237494519450841.js
1321 ms
-1.gif
41 ms
202310147068546.js
636 ms
empty.png
42 ms
6608570658282662127.jpg
14914 ms
face1.gif
48 ms
face25.gif
51 ms
wnxingxing2010.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 Wnxingxing2010.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 Wnxingxing2010.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.
wnxingxing2010.blog.163.com
Open Graph description is not detected on the main page of Wnxingxing 2010 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: