9.6 sec in total
1.5 sec
7.7 sec
361 ms
Click here to check amazing Zwenyuan 11 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about zwenyuan11.blog.163.com
从争先赛到谦让赛,恒港谁让谁?,玉面郎欲归还留的苦衷,当体奥也来打脸时,GOGOGO,未来国球是高俅,中国足球进入招才时代,抑或招财,周亮点亮的那颗恒星,卡佩罗,中超夕阳西下前的最后大牌,里皮防线,恒品还是港制?,冠军赛跑,恒港只有一个赛点,520终成G2大格局,亦夏的网易博客,一个老球迷眼里的中国足球生态地理,球迷、军迷、股迷、书迷,小老酒、小麻将、伪中产、老愤青。
Visit zwenyuan11.blog.163.comWe analyzed Zwenyuan11.blog.163.com page load time and found that the first response time was 1.5 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
zwenyuan11.blog.163.com performance score
1511 ms
7 ms
883 ms
3522 ms
8 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Zwenyuan11.blog.163.com, 25% (21 requests) were made to B.bst.126.net and 22% (19 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 612.5 kB (44%)
1.4 MB
791.8 kB
In fact, the total size of Zwenyuan11.blog.163.com main page is 1.4 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. Images take 584.4 kB which makes up the majority of the site volume.
Potential reduce by 91.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 91.1 kB or 79% 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. Zwenyuan 11 Blog 163 images are well optimized though.
Potential reduce by 358.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 358.4 kB or 69% of the original size.
Potential reduce by 149.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. Zwenyuan11.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 82% of the original size.
Number of requests can be reduced by 36 (43%)
83
47
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zwenyuan 11 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 12 to 1 for JavaScripts and as a result speed up the page load time.
zwenyuan11.blog.163.com
1511 ms
c.css
7 ms
b.css
883 ms
6630133180817252049.jpg
3522 ms
xcode.png
8 ms
1.0.0.js
427 ms
pc.js
8 ms
ph.js
10 ms
5788532896054823428.jpg
4338 ms
blog_rec.png
41 ms
icon.png
39 ms
goodbloghead.png
41 ms
lnkbar.png
41 ms
image.png
40 ms
arrow24.png
40 ms
newtopbaricon8.png
38 ms
5784310771404168363.jpg
5391 ms
5784310771404168389.jpg
3293 ms
5784310771404168390.jpg
1198 ms
5784310771404168418.jpg
1828 ms
5788532896054823143.jpg
1241 ms
5777273896986427793.jpg
1764 ms
5777273896986427838.jpg
1829 ms
5784310771404168453.jpg
4378 ms
5777273896986427620.jpg
2391 ms
crossdomain.html
715 ms
crossdomain.html
1389 ms
crossdomain.html
2250 ms
request.s
740 ms
analyse.png
1262 ms
ava.s
2128 ms
loftericon.png
324 ms
ava.s
738 ms
analyse.png
3160 ms
analytics.js
6 ms
collect
12 ms
HomeBeanNew.getAccessStatistics.dwr
772 ms
UserBeanNew.getVisitor.dwr
1002 ms
NoteBeanNew.getNotesForPrev.dwr
974 ms
HomeBeanNew.getClassifyModuleData.dwr
978 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
987 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
971 ms
blogPhotoAd
628 ms
close_01.png
6 ms
top_bg.png
6 ms
bottom_bg.png
8 ms
left_bg.png
6 ms
right_bg.png
7 ms
left_top.png
7 ms
right_top.png
7 ms
left_bottom.png
8 ms
right_bottom.png
7 ms
shadow.png
4 ms
face59.gif
19 ms
face49.gif
18 ms
face50.gif
19 ms
face50.gif
20 ms
face25.gif
20 ms
face72.gif
18 ms
face51.gif
21 ms
face39.gif
21 ms
face71.gif
21 ms
face66.gif
20 ms
face51.gif
21 ms
ava.s
400 ms
ava.s
744 ms
ava.s
1897 ms
ava.s
723 ms
ava.s
725 ms
ava.s
786 ms
ava.s
1087 ms
ava.s
1088 ms
ava.s
1653 ms
ava.s
1194 ms
ava.s
1446 ms
ava.s
1447 ms
ava.s
1567 ms
ava.s
1804 ms
ava.s
1812 ms
ava.s
1927 ms
r
1262 ms
close2.png
3 ms
ad
1306 ms
jquery-1.4.2.js
9 ms
0316ykt-300-250.jpg
1041 ms
zwenyuan11.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 Zwenyuan11.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 Zwenyuan11.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.
zwenyuan11.blog.163.com
Open Graph description is not detected on the main page of Zwenyuan 11 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: