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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

39.7 sec in total

First Response

6.1 sec

Resources Loaded

32.4 sec

Page Rendered

1.2 sec

sst766.blog.163.com screenshot

About Website

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

Visit sst766.blog.163.com

Key Findings

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

Performance Metrics

sst766.blog.163.com performance score

0

Network Requests Diagram

sst766.blog.163.com

6082 ms

c.css

22 ms

b.css

967 ms

3996944669308206242.jpg

1147 ms

4859383998033558719.jpg

1283 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Sst766.blog.163.com, 44% (56 requests) were made to Os.blog.163.com and 11% (14 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 640.9 kB (14%)

Content Size

4.6 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sst766.blog.163.com main page is 4.6 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. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 163.9 kB

  • Original 195.0 kB
  • After minification 195.0 kB
  • After compression 31.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 163.9 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 9.3 kB

  • Original 3.7 MB
  • After minification 3.7 MB

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. Sst 766 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 318.6 kB

  • Original 460.0 kB
  • After minification 459.8 kB
  • After compression 141.4 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 318.6 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.0 kB

  • Original 181.8 kB
  • After minification 177.9 kB
  • After compression 32.8 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. Sst766.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

118

After Optimization

82

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sst766.blog.163.com

sst766.blog.163.com

6082 ms

c.css

c.css

22 ms

b.css

b.css

967 ms

3996944669308206242.jpg

3996944669308206242.jpg

1147 ms

4859383998033558719.jpg

4859383998033558719.jpg

1283 ms

5773333247313924360.jpg

5773333247313924360.jpg

637 ms

6631307459239718233.jpg

6631307459239718233.jpg

1719 ms

6631420708936701333.jpg

6631420708936701333.jpg

3573 ms

blog_rec.png

blog_rec.png

88 ms

6630198052002910542.jpg

6630198052002910542.jpg

2801 ms

3097913593695329283.jpg

3097913593695329283.jpg

2537 ms

icon.png

icon.png

8 ms

6598172576879001899.jpg

6598172576879001899.jpg

1648 ms

6608736684539439953.jpg

6608736684539439953.jpg

2206 ms

4909205068910871823.jpg

4909205068910871823.jpg

1251 ms

6631292066075949304.jpg

6631292066075949304.jpg

2208 ms

6631345942143195931.jpg

6631345942143195931.jpg

2675 ms

6630586179608537575.jpg

6630586179608537575.jpg

2114 ms

61080069964317409.jpg

61080069964317409.jpg

7807 ms

6619305190305718402.jpg

6619305190305718402.jpg

3734 ms

6619442629258656424.jpg

6619442629258656424.jpg

3485 ms

1113233532908387581.jpg

1113233532908387581.jpg

6113 ms

lnkbar.png

lnkbar.png

20 ms

6630133180817252049.jpg

6630133180817252049.jpg

539 ms

xcode.png

xcode.png

75 ms

1.0.0.js

1.0.0.js

121 ms

pc.js

pc.js

100 ms

ph.js

ph.js

100 ms

image.png

image.png

23 ms

arrow24.png

arrow24.png

26 ms

newtopbaricon8.png

newtopbaricon8.png

25 ms

crossdomain.html

crossdomain.html

800 ms

crossdomain.html

crossdomain.html

517 ms

crossdomain.html

crossdomain.html

526 ms

request.s

request.s

19660 ms

analyse.png

analyse.png

19656 ms

empty.png

empty.png

118 ms

ava.s

ava.s

2325 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

626 ms

BlogCircleBean.getUserShowCircles.dwr

BlogCircleBean.getUserShowCircles.dwr

1026 ms

loftericon.png

loftericon.png

676 ms

analyse.png

analyse.png

20392 ms

PhotoBlogBean.getHeadPic.dwr

PhotoBlogBean.getHeadPic.dwr

558 ms

analytics.js

analytics.js

18 ms

collect

collect

44 ms

SetupBeanNew.getResourceModulesData.dwr

SetupBeanNew.getResourceModulesData.dwr

859 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

2511 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1227 ms

HomeBeanNew.getMonthStatistics.dwr

HomeBeanNew.getMonthStatistics.dwr

1695 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

2062 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

10184 ms

BlogBeanNew.getRecentCommentsByOffset.dwr

BlogBeanNew.getRecentCommentsByOffset.dwr

2195 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

4070 ms

UserFollowBeanNew.getUserFollows.dwr

UserFollowBeanNew.getUserFollows.dwr

4330 ms

BlogBeanNew.getHostHotBlogs.dwr

BlogBeanNew.getHostHotBlogs.dwr

2875 ms

BlogBeanNew.getRecentBlogs.dwr

BlogBeanNew.getRecentBlogs.dwr

3001 ms

6598171477368262121.jpg

6598171477368262121.jpg

19584 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3005 ms

blogPhotoAd

blogPhotoAd

20185 ms

close_01.png

close_01.png

9 ms

top_bg.png

top_bg.png

20 ms

bottom_bg.png

bottom_bg.png

20 ms

left_bg.png

left_bg.png

29 ms

right_bg.png

right_bg.png

27 ms

left_top.png

left_top.png

26 ms

right_top.png

right_top.png

27 ms

left_bottom.png

left_bottom.png

26 ms

right_bottom.png

right_bottom.png

28 ms

shadow.png

shadow.png

25 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

2543 ms

ava.s

ava.s

483 ms

ava.s

ava.s

2164 ms

ava.s

ava.s

709 ms

ava.s

ava.s

721 ms

ava.s

ava.s

953 ms

ava.s

ava.s

950 ms

ava.s

ava.s

4328 ms

ava.s

ava.s

1053 ms

ava.s

ava.s

1079 ms

ava.s

ava.s

1433 ms

ava.s

ava.s

1430 ms

ava.s

ava.s

2862 ms

ava.s

ava.s

12065 ms

ava.s

ava.s

4341 ms

ava.s

ava.s

3235 ms

ava.s

ava.s

2097 ms

ava.s

ava.s

2439 ms

ava.s

ava.s

2799 ms

ava.s

ava.s

2801 ms

ava.s

ava.s

3141 ms

ava.s

ava.s

3150 ms

ava.s

ava.s

3302 ms

ava.s

ava.s

3488 ms

ava.s

ava.s

6583 ms

ava.s

ava.s

3777 ms

ava.s

ava.s

5126 ms

ava.s

ava.s

4251 ms

ava.s

ava.s

20181 ms

ava.s

ava.s

5845 ms

ava.s

ava.s

4722 ms

ava.s

ava.s

5203 ms

ava.s

ava.s

8212 ms

ava.s

ava.s

5687 ms

6598207761251978107.jpg

6598207761251978107.jpg

19580 ms

ava.s

ava.s

5063 ms

ava.s

ava.s

4454 ms

ava.s

ava.s

4933 ms

ava.s

ava.s

6236 ms

ava.s

ava.s

5430 ms

ava.s

ava.s

5535 ms

ava.s

ava.s

5908 ms

ava.s

ava.s

6015 ms

ava.s

ava.s

8374 ms

ava.s

ava.s

7717 ms

ava.s

ava.s

6602 ms

ava.s

ava.s

6685 ms

ava.s

ava.s

9389 ms

ava.s

ava.s

6886 ms

ava.s

ava.s

6886 ms

ava.s

ava.s

7211 ms

ava.s

ava.s

7290 ms

ava.s

ava.s

7185 ms

ava.s

ava.s

8429 ms

ava.s

ava.s

10047 ms

ava.s

ava.s

7572 ms

4876835446589260580.jpg

4876835446589260580.jpg

19580 ms

face57.gif

face57.gif

35 ms

face60.png

face60.png

8 ms

SEO Factors

sst766.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 Sst766.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 Sst766.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

sst766.blog.163.com

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