Tools & Wizards About Us
faye-boony.blog.163.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

24.5 sec in total

First Response

1.7 sec

Resources Loaded

22.1 sec

Page Rendered

699 ms

faye-boony.blog.163.com screenshot

About Website

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

Visit faye-boony.blog.163.com

Key Findings

We analyzed Faye-boony.blog.163.com page load time and found that the first response time was 1.7 sec and then it took 22.8 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

faye-boony.blog.163.com performance score

0

Network Requests Diagram

faye-boony.blog.163.com

1662 ms

c.css

120 ms

b.css

869 ms

6630133180817252049.jpg

7568 ms

xcode.png

62 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Faye-boony.blog.163.com, 18% (10 requests) were made to B.bst.126.net and 16% (9 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Gorgon.youdao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 591.8 kB (67%)

Content Size

887.3 kB

After Optimization

295.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faye-boony.blog.163.com main page is 887.3 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. 30% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 74.4 kB

  • Original 96.7 kB
  • After minification 96.6 kB
  • After compression 22.2 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 74.4 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 9.2 kB

  • Original 86.4 kB
  • After minification 77.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. Obviously, Faye Boony Blog 163 needs image optimization as it can save up to 9.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 358.5 kB

  • Original 521.7 kB
  • After minification 521.6 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 358.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.6 kB

  • Original 182.6 kB
  • After minification 178.7 kB
  • After compression 33.0 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. Faye-boony.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.

Requests Breakdown

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

Requests Now

54

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faye Boony 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.

Network Requests Diagram

faye-boony.blog.163.com

faye-boony.blog.163.com

1662 ms

c.css

c.css

120 ms

b.css

b.css

869 ms

6630133180817252049.jpg

6630133180817252049.jpg

7568 ms

xcode.png

xcode.png

62 ms

1.0.0.js

1.0.0.js

103 ms

pc.js

pc.js

75 ms

ph.js

ph.js

73 ms

5721260376621467737.jpg

5721260376621467737.jpg

728 ms

icon.png

icon.png

142 ms

5728860200992661402.jpg

5728860200992661402.jpg

716 ms

5728860200992661401.jpg

5728860200992661401.jpg

825 ms

5728860200992661452.jpg

5728860200992661452.jpg

1904 ms

5728860200992661398.jpg

5728860200992661398.jpg

887 ms

5728860200992661426.jpg

5728860200992661426.jpg

1795 ms

5728860200992661396.jpg

5728860200992661396.jpg

1074 ms

5728860200992661397.jpg

5728860200992661397.jpg

1075 ms

5728860200992661399.jpg

5728860200992661399.jpg

1584 ms

lnkbar.png

lnkbar.png

131 ms

image.png

image.png

132 ms

arrow24.png

arrow24.png

132 ms

newtopbaricon8.png

newtopbaricon8.png

129 ms

crossdomain.html

crossdomain.html

800 ms

crossdomain.html

crossdomain.html

1093 ms

crossdomain.html

crossdomain.html

871 ms

request.s

request.s

19736 ms

analyse.png

analyse.png

936 ms

ava.s

ava.s

947 ms

loftericon.png

loftericon.png

439 ms

analyse.png

analyse.png

904 ms

analytics.js

analytics.js

69 ms

collect

collect

63 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

815 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1137 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1148 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1221 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1438 ms

blogPhotoAd

blogPhotoAd

457 ms

close_01.png

close_01.png

14 ms

top_bg.png

top_bg.png

20 ms

bottom_bg.png

bottom_bg.png

19 ms

left_bg.png

left_bg.png

19 ms

right_bg.png

right_bg.png

19 ms

left_top.png

left_top.png

23 ms

right_top.png

right_top.png

29 ms

left_bottom.png

left_bottom.png

29 ms

right_bottom.png

right_bottom.png

29 ms

shadow.png

shadow.png

12 ms

r

r

686 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

2026 ms

ava.s

ava.s

447 ms

ava.s

ava.s

877 ms

ad

ad

1082 ms

close2.png

close2.png

6 ms

jquery-1.4.2.js

jquery-1.4.2.js

21 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1616 ms

SEO Factors

faye-boony.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 Faye-boony.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 Faye-boony.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

faye-boony.blog.163.com

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