Tools & Wizards About Us
zhangxiaozhou163.blog.163.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zhangxiaozhou163.blog.163.com

张晓舟 出神 - 张晓舟 - 网易博客

Page Load Speed

19.7 sec in total

First Response

1.9 sec

Resources Loaded

17.4 sec

Page Rendered

364 ms

zhangxiaozhou163.blog.163.com screenshot

About Website

Visit zhangxiaozhou163.blog.163.com now to see the best up-to-date Zhangxiaozhou 163 Blog content for China and also check out these interesting facts you probably never knew about zhangxiaozhou163.blog.163.com

背着贝尔去减肥,斯科拉里下一个任务：迭戈科斯塔,但愿鸟巢不是内马尔个人秀,巴萨式惨败,再见，曼彻斯特先生,巴萨如此无助，拜仁还会进步,巴西，请远离巴萨,梅西能否既巴萨，又皇马,坏孩子,巴萨史诗性逆转了全世界媒体,张晓舟的网易博客,

Visit zhangxiaozhou163.blog.163.com

Key Findings

We analyzed Zhangxiaozhou163.blog.163.com page load time and found that the first response time was 1.9 sec and then it took 17.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

zhangxiaozhou163.blog.163.com performance score

0

Network Requests Diagram

zhangxiaozhou163.blog.163.com

1935 ms

c.css

9 ms

b.css

765 ms

6630133180817252049.jpg

1248 ms

xcode.png

5 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Zhangxiaozhou163.blog.163.com, 27% (20 requests) were made to Os.blog.163.com and 15% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (12.6 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 570.8 kB (56%)

Content Size

1.0 MB

After Optimization

445.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zhangxiaozhou163.blog.163.com main page is 1.0 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 489.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 84.8 kB

  • Original 108.2 kB
  • After minification 108.1 kB
  • After compression 23.4 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 84.8 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 10.3 kB

  • Original 236.4 kB
  • After minification 226.2 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. Zhangxiaozhou 163 Blog images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 326.7 kB

  • Original 489.8 kB
  • After minification 489.8 kB
  • After compression 163.1 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 326.7 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 149.1 kB

  • Original 182.0 kB
  • After minification 178.1 kB
  • After compression 32.9 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. Zhangxiaozhou163.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (46%)

Requests Now

71

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zhangxiaozhou 163 Blog. 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 as a result speed up the page load time.

Network Requests Diagram

zhangxiaozhou163.blog.163.com

zhangxiaozhou163.blog.163.com

1935 ms

c.css

c.css

9 ms

b.css

b.css

765 ms

6630133180817252049.jpg

6630133180817252049.jpg

1248 ms

xcode.png

xcode.png

5 ms

1.0.0.js

1.0.0.js

74 ms

pc.js

pc.js

19 ms

ph.js

ph.js

18 ms

5771925872430547143.jpg

5771925872430547143.jpg

7263 ms

blog_rec.png

blog_rec.png

93 ms

4570309196867757346.jpg

4570309196867757346.jpg

5278 ms

5776147997081221501.jpg

5776147997081221501.jpg

7331 ms

5771925872430547144.jpg

5771925872430547144.jpg

4311 ms

5776147997081221517.jpg

5776147997081221517.jpg

2309 ms

5776147997081221502.jpg

5776147997081221502.jpg

2930 ms

icon.png

icon.png

85 ms

lnkbar.png

lnkbar.png

86 ms

image.png

image.png

87 ms

arrow24.png

arrow24.png

85 ms

newtopbaricon8.png

newtopbaricon8.png

86 ms

crossdomain.html

crossdomain.html

901 ms

crossdomain.html

crossdomain.html

3158 ms

crossdomain.html

crossdomain.html

1120 ms

request.s

request.s

629 ms

analyse.png

analyse.png

1336 ms

ava.s

ava.s

381 ms

loftericon.png

loftericon.png

436 ms

ava.s

ava.s

2328 ms

analyse.png

analyse.png

1339 ms

analytics.js

analytics.js

9 ms

collect

collect

15 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

951 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

983 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1362 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1434 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1368 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1867 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1536 ms

blogPhotoAd

blogPhotoAd

656 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

13 ms

bottom_bg.png

bottom_bg.png

12 ms

left_bg.png

left_bg.png

11 ms

right_bg.png

right_bg.png

12 ms

left_top.png

left_top.png

14 ms

right_top.png

right_top.png

16 ms

left_bottom.png

left_bottom.png

15 ms

right_bottom.png

right_bottom.png

14 ms

shadow.png

shadow.png

12 ms

ava.s

ava.s

479 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1255 ms

r

r

1197 ms

ava.s

ava.s

535 ms

ava.s

ava.s

454 ms

ava.s

ava.s

1094 ms

ava.s

ava.s

1214 ms

ava.s

ava.s

1016 ms

ava.s

ava.s

2913 ms

ava.s

ava.s

1034 ms

ava.s

ava.s

1494 ms

ava.s

ava.s

12631 ms

ava.s

ava.s

1823 ms

ava.s

ava.s

1602 ms

ava.s

ava.s

2013 ms

ava.s

ava.s

3747 ms

ava.s

ava.s

7545 ms

ava.s

ava.s

3577 ms

ava.s

ava.s

2502 ms

face50.gif

face50.gif

6 ms

close2.png

close2.png

4 ms

ad

ad

1205 ms

jquery-1.4.2.js

jquery-1.4.2.js

7 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

978 ms

SEO Factors

zhangxiaozhou163.blog.163.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zhangxiaozhou163.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 Zhangxiaozhou163.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.

Social Sharing Optimization

zhangxiaozhou163.blog.163.com

Open Graph description is not detected on the main page of Zhangxiaozhou 163 Blog. 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: