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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

40.4 sec in total

First Response

9.4 sec

Resources Loaded

30.4 sec

Page Rendered

563 ms

shh281.blog.163.com screenshot

About Website

Click here to check amazing Shh 281 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about shh281.blog.163.com

Visit shh281.blog.163.com

Key Findings

We analyzed Shh281.blog.163.com page load time and found that the first response time was 9.4 sec and then it took 30.9 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 were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

shh281.blog.163.com performance score

0

Network Requests Diagram

shh281.blog.163.com

9431 ms

c.css

26 ms

b.css

1928 ms

20130524110051994.jpg

12271 ms

20130524110507103.jpg

14204 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Shh281.blog.163.com, 28% (21 requests) were made to Img.bimg.126.net and 15% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Shh28.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 602.0 kB (59%)

Content Size

1.0 MB

After Optimization

414.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shh281.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. 35% of websites need less resources to load. Javascripts take 521.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 79.1 kB

  • Original 103.6 kB
  • After minification 103.6 kB
  • After compression 24.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 79.1 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 12.5 kB

  • Original 206.0 kB
  • After minification 193.5 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. Shh 281 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.3 kB

  • Original 521.3 kB
  • After minification 521.3 kB
  • After compression 163.0 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.3 kB or 69% 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. Shh281.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 39 (55%)

Requests Now

71

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shh281.blog.163.com

shh281.blog.163.com

9431 ms

c.css

c.css

26 ms

b.css

b.css

1928 ms

20130524110051994.jpg

20130524110051994.jpg

12271 ms

20130524110507103.jpg

20130524110507103.jpg

14204 ms

20130524111533504.jpg

20130524111533504.jpg

15143 ms

20130524112004676.jpg

20130524112004676.jpg

19848 ms

20130523113522677.jpg

20130523113522677.jpg

19848 ms

6630133180817252049.jpg

6630133180817252049.jpg

589 ms

xcode.png

xcode.png

14 ms

1.0.0.js

1.0.0.js

88 ms

pc.js

pc.js

19 ms

ph.js

ph.js

19 ms

5770799972522187428.jpg

5770799972522187428.jpg

462 ms

icon.png

icon.png

108 ms

5779244221823515636.jpg

5779244221823515636.jpg

456 ms

5779244221823515635.jpg

5779244221823515635.jpg

455 ms

5776992422009831185.jpg

5776992422009831185.jpg

482 ms

5776992422009831184.jpg

5776992422009831184.jpg

489 ms

5776992422009831186.jpg

5776992422009831186.jpg

537 ms

5780088646753648775.jpg

5780088646753648775.jpg

672 ms

5776992422009831187.jpg

5776992422009831187.jpg

681 ms

5776992422009831188.jpg

5776992422009831188.jpg

681 ms

5776992422009831189.jpg

5776992422009831189.jpg

722 ms

5776992422009831191.jpg

5776992422009831191.jpg

729 ms

5776992422009831190.jpg

5776992422009831190.jpg

801 ms

5791347645822068511.jpg

5791347645822068511.jpg

897 ms

5791347645822068509.jpg

5791347645822068509.jpg

905 ms

5791347645822068513.jpg

5791347645822068513.jpg

906 ms

5780933071683780524.jpg

5780933071683780524.jpg

959 ms

5791347645822068515.jpg

5791347645822068515.jpg

969 ms

5791347645822068517.jpg

5791347645822068517.jpg

1066 ms

5791347645822068546.jpg

5791347645822068546.jpg

1121 ms

5791347645822068549.jpg

5791347645822068549.jpg

1130 ms

5791347645822068547.jpg

5791347645822068547.jpg

1130 ms

lnkbar.png

lnkbar.png

97 ms

image.png

image.png

98 ms

arrow24.png

arrow24.png

97 ms

newtopbaricon8.png

newtopbaricon8.png

96 ms

crossdomain.html

crossdomain.html

942 ms

crossdomain.html

crossdomain.html

461 ms

crossdomain.html

crossdomain.html

468 ms

request.s

request.s

19773 ms

analyse.png

analyse.png

558 ms

ava.s

ava.s

10102 ms

loftericon.png

loftericon.png

5195 ms

ava.s

ava.s

1902 ms

analyse.png

analyse.png

548 ms

analytics.js

analytics.js

10 ms

collect

collect

16 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

527 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

884 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

2741 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

11513 ms

PhotoBlogBean.getHeadPic.dwr

PhotoBlogBean.getHeadPic.dwr

670 ms

blogPhotoAd

blogPhotoAd

278 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

10 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

12 ms

right_top.png

right_top.png

12 ms

left_bottom.png

left_bottom.png

9 ms

right_bottom.png

right_bottom.png

13 ms

shadow.png

shadow.png

10 ms

photoblog.png

photoblog.png

1372 ms

r

r

547 ms

ava.s

ava.s

588 ms

ava.s

ava.s

1094 ms

ad

ad

478 ms

close2.png

close2.png

6 ms

jquery-1.4.2.js

jquery-1.4.2.js

9 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1455 ms

face1.gif

face1.gif

5 ms

SEO Factors

shh281.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 Shh281.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 Shh281.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

shh281.blog.163.com

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