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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

32.6 sec in total

First Response

6 sec

Resources Loaded

25.8 sec

Page Rendered

844 ms

colimited.blog.163.com screenshot

About Website

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

Visit colimited.blog.163.com

Key Findings

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

Performance Metrics

colimited.blog.163.com performance score

0

Network Requests Diagram

colimited.blog.163.com

5977 ms

c.css

13 ms

b.css

977 ms

2513290067067697120.jpg

633 ms

3329567499511441710.jpg

20478 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Colimited.blog.163.com, 23% (23 requests) were made to Os.blog.163.com and 18% (18 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 621.1 kB (26%)

Content Size

2.4 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Colimited.blog.163.com main page is 2.4 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 147.0 kB

  • Original 190.5 kB
  • After minification 190.5 kB
  • After compression 43.6 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 147.0 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 16.5 kB

  • Original 1.6 MB
  • After minification 1.5 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. Colimited Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.5 kB

  • Original 449.0 kB
  • After minification 449.0 kB
  • After compression 138.6 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 310.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 147.1 kB

  • Original 179.1 kB
  • After minification 175.4 kB
  • After compression 32.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. Colimited.blog.163.com needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (37%)

Requests Now

93

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

colimited.blog.163.com

colimited.blog.163.com

5977 ms

c.css

c.css

13 ms

b.css

b.css

977 ms

2513290067067697120.jpg

2513290067067697120.jpg

633 ms

3329567499511441710.jpg

3329567499511441710.jpg

20478 ms

6631286568518811858.jpg

6631286568518811858.jpg

731 ms

54324670523300549.jpg

54324670523300549.jpg

728 ms

6630073807189304024.jpg

6630073807189304024.jpg

1021 ms

3365314821553932305.jpg

3365314821553932305.jpg

3894 ms

6598184671507677247.jpg

6598184671507677247.jpg

825 ms

6598268234391294346.jpg

6598268234391294346.jpg

706 ms

6598208860763111427.jpg

6598208860763111427.jpg

1228 ms

6631354738238348151.jpg

6631354738238348151.jpg

759 ms

6619204035236141892.jpg

6619204035236141892.jpg

847 ms

6619183144515208149.jpg

6619183144515208149.jpg

1007 ms

5722104801551596968.jpg

5722104801551596968.jpg

2261 ms

blog_rec.png

blog_rec.png

333 ms

5722104801551596966.jpg

5722104801551596966.jpg

1806 ms

goodbloghead.png

goodbloghead.png

84 ms

xcode.png

xcode.png

75 ms

1.0.0.js

1.0.0.js

136 ms

pc.js

pc.js

74 ms

ph.js

ph.js

74 ms

6630133180817252049.jpg

6630133180817252049.jpg

3266 ms

5722104801551596964.jpg

5722104801551596964.jpg

900 ms

1154328879508555412.jpg

1154328879508555412.jpg

323 ms

icon.png

icon.png

11 ms

rssi.png

rssi.png

14 ms

lnkbar.png

lnkbar.png

16 ms

image.png

image.png

19 ms

arrow24.png

arrow24.png

17 ms

newtopbaricon8.png

newtopbaricon8.png

17 ms

2791105869080952810.jpg

2791105869080952810.jpg

262 ms

6631245886582587828.jpg

6631245886582587828.jpg

238 ms

crossdomain.html

crossdomain.html

773 ms

crossdomain.html

crossdomain.html

1058 ms

crossdomain.html

crossdomain.html

1672 ms

request.s

request.s

2207 ms

analyse.png

analyse.png

20319 ms

ava.s

ava.s

1018 ms

ava.s

ava.s

744 ms

loftericon.png

loftericon.png

626 ms

analyse.png

analyse.png

20052 ms

SetupBeanNew.getResourceModulesData.dwr

SetupBeanNew.getResourceModulesData.dwr

826 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

1017 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

993 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

6295 ms

BlogBeanNew.getRecentCommentsByOffset.dwr

BlogBeanNew.getRecentCommentsByOffset.dwr

1309 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

3003 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

1550 ms

BlogBeanNew.getHostHotBlogs.dwr

BlogBeanNew.getHostHotBlogs.dwr

1673 ms

blogPhotoAd

blogPhotoAd

19845 ms

close_01.png

close_01.png

15 ms

top_bg.png

top_bg.png

38 ms

bottom_bg.png

bottom_bg.png

38 ms

left_bg.png

left_bg.png

38 ms

right_bg.png

right_bg.png

37 ms

left_top.png

left_top.png

38 ms

right_top.png

right_top.png

36 ms

left_bottom.png

left_bottom.png

41 ms

right_bottom.png

right_bottom.png

40 ms

shadow.png

shadow.png

10 ms

PhotoBlogBean.getHeadPic.dwr

PhotoBlogBean.getHeadPic.dwr

1082 ms

analytics.js

analytics.js

45 ms

collect

collect

25 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

651 ms

ava.s

ava.s

481 ms

ava.s

ava.s

377 ms

ava.s

ava.s

709 ms

ava.s

ava.s

3589 ms

ava.s

ava.s

723 ms

ava.s

ava.s

748 ms

ava.s

ava.s

757 ms

ava.s

ava.s

986 ms

ava.s

ava.s

2637 ms

ava.s

ava.s

1079 ms

ava.s

ava.s

1124 ms

ava.s

ava.s

1129 ms

ava.s

ava.s

2594 ms

ava.s

ava.s

1438 ms

ava.s

ava.s

1493 ms

ava.s

ava.s

1500 ms

ava.s

ava.s

1805 ms

ava.s

ava.s

2847 ms

ava.s

ava.s

1869 ms

ava.s

ava.s

2188 ms

face55.gif

face55.gif

8 ms

face56.gif

face56.gif

10 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

891 ms

675539944205859332.jpg

675539944205859332.jpg

149 ms

face74.gif

face74.gif

31 ms

2997427027092268052.jpg

2997427027092268052.jpg

374 ms

face59.gif

face59.gif

23 ms

face49.gif

face49.gif

20 ms

face50.gif

face50.gif

20 ms

face50.gif

face50.gif

21 ms

face25.gif

face25.gif

21 ms

6608627832887293753.jpg

6608627832887293753.jpg

370 ms

SEO Factors

colimited.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 Colimited.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 Colimited.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

colimited.blog.163.com

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