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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

32.5 sec in total

First Response

4.6 sec

Resources Loaded

27.2 sec

Page Rendered

721 ms

better.blog.163.com screenshot

About Website

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

Visit better.blog.163.com

Key Findings

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

Performance Metrics

better.blog.163.com performance score

0

Network Requests Diagram

better.blog.163.com

4642 ms

c.css

43 ms

b.css

805 ms

4831517975239039083.jpg

572 ms

icon.png

68 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Better.blog.163.com, 21% (11 requests) were made to B.bst.126.net and 17% (9 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 G.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.5 kB (55%)

Content Size

964.4 kB

After Optimization

432.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 62.7 kB

  • Original 79.7 kB
  • After minification 79.7 kB
  • After compression 17.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 62.7 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 9.2 kB

  • Original 253.6 kB
  • After minification 244.3 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. Better 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 149.2 kB

  • Original 182.1 kB
  • After minification 178.1 kB
  • After compression 32.9 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. Better.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

better.blog.163.com

better.blog.163.com

4642 ms

c.css

c.css

43 ms

b.css

b.css

805 ms

4831517975239039083.jpg

4831517975239039083.jpg

572 ms

icon.png

icon.png

68 ms

1158551004141883555.jpg

1158551004141883555.jpg

7532 ms

1158551004141883576.jpg

1158551004141883576.jpg

3015 ms

1158551004141883593.jpg

1158551004141883593.jpg

856 ms

lnkbar.png

lnkbar.png

35 ms

6630133180817252049.jpg

6630133180817252049.jpg

3397 ms

xcode.png

xcode.png

44 ms

1.0.0.js

1.0.0.js

96 ms

pc.js

pc.js

61 ms

ph.js

ph.js

63 ms

1158551004141883611.jpg

1158551004141883611.jpg

396 ms

image.png

image.png

22 ms

arrow24.png

arrow24.png

29 ms

newtopbaricon8.png

newtopbaricon8.png

27 ms

crossdomain.html

crossdomain.html

719 ms

crossdomain.html

crossdomain.html

771 ms

crossdomain.html

crossdomain.html

736 ms

request.s

request.s

828 ms

analyse.png

analyse.png

5065 ms

ava.s

ava.s

838 ms

loftericon.png

loftericon.png

419 ms

ava.s

ava.s

2475 ms

analyse.png

analyse.png

834 ms

analytics.js

analytics.js

25 ms

collect

collect

68 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

731 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1119 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1180 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

2679 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1328 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1411 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1694 ms

blogPhotoAd

blogPhotoAd

428 ms

close_01.png

close_01.png

20 ms

top_bg.png

top_bg.png

31 ms

bottom_bg.png

bottom_bg.png

37 ms

left_bg.png

left_bg.png

36 ms

right_bg.png

right_bg.png

35 ms

left_top.png

left_top.png

48 ms

right_top.png

right_top.png

48 ms

left_bottom.png

left_bottom.png

49 ms

right_bottom.png

right_bottom.png

50 ms

shadow.png

shadow.png

20 ms

r

r

20429 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

743 ms

ava.s

ava.s

20036 ms

ava.s

ava.s

577 ms

close2.png

close2.png

30 ms

face60.png

face60.png

7 ms

SEO Factors

better.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 Better.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 Better.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

better.blog.163.com

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