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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

21 sec in total

First Response

4.9 sec

Resources Loaded

15.8 sec

Page Rendered

287 ms

yy52609.blog.163.com screenshot

About Website

Welcome to yy52609.blog.163.com homepage info - get ready to check Yy 52609 Blog 163 best content for China right away, or after learning these important things about yy52609.blog.163.com

Visit yy52609.blog.163.com

Key Findings

We analyzed Yy52609.blog.163.com page load time and found that the first response time was 4.9 sec and then it took 16.1 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

yy52609.blog.163.com performance score

0

Network Requests Diagram

yy52609.blog.163.com

4929 ms

c.css

330 ms

b.css

1973 ms

5748281974385706293.jpg

1283 ms

icon.png

64 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Yy52609.blog.163.com, 22% (12 requests) were made to B.bst.126.net and 17% (9 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (10.4 sec) relates to the external source Sanlikaida.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.4 kB (63%)

Content Size

955.4 kB

After Optimization

358.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 76.0 kB

  • Original 97.7 kB
  • After minification 97.7 kB
  • After compression 21.7 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.0 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 13.3 kB

  • Original 153.5 kB
  • After minification 140.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. Yy 52609 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.6 kB

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

CSS Optimization

-82%

Potential reduce by 149.5 kB

  • Original 182.5 kB
  • After minification 178.6 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. Yy52609.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (54%)

Requests Now

52

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

yy52609.blog.163.com

yy52609.blog.163.com

4929 ms

c.css

c.css

330 ms

b.css

b.css

1973 ms

5748281974385706293.jpg

5748281974385706293.jpg

1283 ms

icon.png

icon.png

64 ms

5748281974385706289.jpg

5748281974385706289.jpg

2798 ms

5748563449362416562.jpg

5748563449362416562.jpg

914 ms

5748281974385706311.jpg

5748281974385706311.jpg

1789 ms

5742652474851538371.jpg

5742652474851538371.jpg

1695 ms

rssi.png

rssi.png

60 ms

lnkbar.png

lnkbar.png

12 ms

6630133180817252049.jpg

6630133180817252049.jpg

1052 ms

xcode.png

xcode.png

10 ms

1.0.0.js

1.0.0.js

384 ms

pc.js

pc.js

13 ms

ph.js

ph.js

12 ms

image.png

image.png

10 ms

arrow24.png

arrow24.png

11 ms

newtopbaricon8.png

newtopbaricon8.png

12 ms

crossdomain.html

crossdomain.html

908 ms

crossdomain.html

crossdomain.html

823 ms

crossdomain.html

crossdomain.html

945 ms

request.s

request.s

702 ms

analyse.png

analyse.png

1042 ms

empty.png

empty.png

34 ms

2013422162416677.jpg

2013422162416677.jpg

10410 ms

ava.s

ava.s

6069 ms

loftericon.png

loftericon.png

469 ms

ava.s

ava.s

1019 ms

analyse.png

analyse.png

1081 ms

analytics.js

analytics.js

7 ms

collect

collect

15 ms

SetupBeanNew.getResourceModulesData.dwr

SetupBeanNew.getResourceModulesData.dwr

2392 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1404 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

2374 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

2330 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2344 ms

blogPhotoAd

blogPhotoAd

618 ms

close_01.png

close_01.png

11 ms

top_bg.png

top_bg.png

9 ms

bottom_bg.png

bottom_bg.png

10 ms

left_bg.png

left_bg.png

11 ms

right_bg.png

right_bg.png

11 ms

left_top.png

left_top.png

11 ms

right_top.png

right_top.png

21 ms

left_bottom.png

left_bottom.png

13 ms

right_bottom.png

right_bottom.png

21 ms

shadow.png

shadow.png

12 ms

r

r

1313 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

5169 ms

close2.png

close2.png

4 ms

face22.gif

face22.gif

4 ms

ad

ad

1035 ms

jquery-1.4.2.js

jquery-1.4.2.js

10 ms

SEO Factors

yy52609.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 Yy52609.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 Yy52609.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

yy52609.blog.163.com

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