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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fengxiang2013.blog.163.com

南方周末冯翔的博客 - 冯翔 - 网易博客

Page Load Speed

18 sec in total

First Response

2.5 sec

Resources Loaded

15.1 sec

Page Rendered

434 ms

fengxiang2013.blog.163.com screenshot

About Website

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

崔健老师,崔健老了吗？【图】,要写崔健，采访他本人其实最不重要,“这孩子从小就撒不了谎” ——崔健真唱篇,冯翔的网易博客,网易博客,

Visit fengxiang2013.blog.163.com

Key Findings

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

Performance Metrics

fengxiang2013.blog.163.com performance score

0

Network Requests Diagram

fengxiang2013.blog.163.com

2522 ms

c.css

1021 ms

b.css

2033 ms

6630133180817252049.jpg

1182 ms

xcode.png

11 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fengxiang2013.blog.163.com, 32% (21 requests) were made to Img.bimg.126.net and 17% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (11.1 sec) belongs to the original domain Fengxiang2013.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.5 kB (61%)

Content Size

930.2 kB

After Optimization

364.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fengxiang2013.blog.163.com main page is 930.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 489.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 76.8 kB

  • Original 98.8 kB
  • After minification 98.8 kB
  • After compression 22.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 76.8 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 10.3 kB

  • Original 156.3 kB
  • After minification 146.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. Fengxiang 2013 Blog 163 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 326.5 kB

  • Original 489.4 kB
  • After minification 489.4 kB
  • After compression 162.9 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.5 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 152.0 kB

  • Original 185.7 kB
  • After minification 181.6 kB
  • After compression 33.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. Fengxiang2013.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (56%)

Requests Now

64

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fengxiang 2013 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

fengxiang2013.blog.163.com

fengxiang2013.blog.163.com

2522 ms

c.css

c.css

1021 ms

b.css

b.css

2033 ms

6630133180817252049.jpg

6630133180817252049.jpg

1182 ms

xcode.png

xcode.png

11 ms

1.0.0.js

1.0.0.js

74 ms

pc.js

pc.js

9 ms

ph.js

ph.js

10 ms

5770799972522187428.jpg

5770799972522187428.jpg

1067 ms

blog_rec.png

blog_rec.png

59 ms

5779244221823515636.jpg

5779244221823515636.jpg

1103 ms

5779244221823515635.jpg

5779244221823515635.jpg

3153 ms

5791347645822068511.jpg

5791347645822068511.jpg

1654 ms

5791347645822068509.jpg

5791347645822068509.jpg

2083 ms

5791347645822068513.jpg

5791347645822068513.jpg

2093 ms

5780933071683780524.jpg

5780933071683780524.jpg

7078 ms

5791347645822068515.jpg

5791347645822068515.jpg

2197 ms

5791347645822068517.jpg

5791347645822068517.jpg

4248 ms

5791347645822068546.jpg

5791347645822068546.jpg

2631 ms

5791347645822068549.jpg

5791347645822068549.jpg

4135 ms

5791347645822068547.jpg

5791347645822068547.jpg

3158 ms

5776992422009831185.jpg

5776992422009831185.jpg

3679 ms

5776992422009831184.jpg

5776992422009831184.jpg

5097 ms

5776992422009831186.jpg

5776992422009831186.jpg

4201 ms

5780088646753648775.jpg

5780088646753648775.jpg

4662 ms

5776992422009831187.jpg

5776992422009831187.jpg

5987 ms

5776992422009831188.jpg

5776992422009831188.jpg

4773 ms

5776992422009831189.jpg

5776992422009831189.jpg

6371 ms

5776992422009831191.jpg

5776992422009831191.jpg

6701 ms

5776992422009831190.jpg

5776992422009831190.jpg

5624 ms

icon.png

icon.png

45 ms

lnkbar.png

lnkbar.png

45 ms

image.png

image.png

45 ms

arrow24.png

arrow24.png

46 ms

newtopbaricon8.png

newtopbaricon8.png

44 ms

crossdomain.html

crossdomain.html

3677 ms

crossdomain.html

crossdomain.html

8123 ms

crossdomain.html

crossdomain.html

1211 ms

request.s

request.s

727 ms

analyse.png

analyse.png

1252 ms

empty.png

empty.png

24 ms

20131023113440b06b4.jpg

20131023113440b06b4.jpg

1083 ms

ava.s

ava.s

475 ms

loftericon.png

loftericon.png

11062 ms

ava.s

ava.s

818 ms

analyse.png

analyse.png

1248 ms

analytics.js

analytics.js

4 ms

collect

collect

11 ms

blogPhotoAd

blogPhotoAd

628 ms

close_01.png

close_01.png

5 ms

top_bg.png

top_bg.png

13 ms

bottom_bg.png

bottom_bg.png

18 ms

left_bg.png

left_bg.png

16 ms

right_bg.png

right_bg.png

16 ms

left_top.png

left_top.png

14 ms

right_top.png

right_top.png

17 ms

left_bottom.png

left_bottom.png

16 ms

right_bottom.png

right_bottom.png

17 ms

shadow.png

shadow.png

16 ms

r

r

1218 ms

close2.png

close2.png

4 ms

ad

ad

1394 ms

jquery-1.4.2.js

jquery-1.4.2.js

8 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

3429 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

4790 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

5705 ms

SEO Factors

fengxiang2013.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 Fengxiang2013.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 Fengxiang2013.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

fengxiang2013.blog.163.com

Open Graph description is not detected on the main page of Fengxiang 2013 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: