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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

29.1 sec in total

First Response

1.4 sec

Resources Loaded

26.3 sec

Page Rendered

1.5 sec

zhiheong.blog.163.com screenshot

About Website

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

Visit zhiheong.blog.163.com

Key Findings

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

Performance Metrics

zhiheong.blog.163.com performance score

0

Network Requests Diagram

zhiheong.blog.163.com

1410 ms

c.css

56 ms

b.css

3629 ms

6630133180817252049.jpg

977 ms

xcode.png

21 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Zhiheong.blog.163.com, 44% (39 requests) were made to Os.blog.163.com and 12% (11 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 Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.4 kB (61%)

Content Size

874.5 kB

After Optimization

345.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 60.7 kB

  • Original 77.4 kB
  • After minification 77.4 kB
  • After compression 16.8 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 60.7 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 9.3 kB

  • Original 166.3 kB
  • After minification 157.1 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. Zhiheong 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.0 kB

  • Original 181.7 kB
  • After minification 177.8 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. Zhiheong.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 25 (30%)

Requests Now

83

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

zhiheong.blog.163.com

zhiheong.blog.163.com

1410 ms

c.css

c.css

56 ms

b.css

b.css

3629 ms

6630133180817252049.jpg

6630133180817252049.jpg

977 ms

xcode.png

xcode.png

21 ms

1.0.0.js

1.0.0.js

112 ms

pc.js

pc.js

27 ms

ph.js

ph.js

25 ms

4562146422543502116.jpg

4562146422543502116.jpg

11313 ms

blog_rec.png

blog_rec.png

75 ms

icon.png

icon.png

53 ms

lnkbar.png

lnkbar.png

53 ms

image.png

image.png

54 ms

arrow24.png

arrow24.png

52 ms

newtopbaricon8.png

newtopbaricon8.png

54 ms

crossdomain.html

crossdomain.html

711 ms

crossdomain.html

crossdomain.html

1897 ms

crossdomain.html

crossdomain.html

570 ms

request.s

request.s

754 ms

analyse.png

analyse.png

20471 ms

empty.png

empty.png

52 ms

6598217656856898013.jpg

6598217656856898013.jpg

565 ms

4823355201014246547.jpg

4823355201014246547.jpg

1036 ms

6598256139763638647.jpg

6598256139763638647.jpg

9846 ms

ava.s

ava.s

1558 ms

loftericon.png

loftericon.png

418 ms

6631442699169999294.jpg

6631442699169999294.jpg

1706 ms

ava.s

ava.s

685 ms

1627206840465270310.jpg

1627206840465270310.jpg

2566 ms

6631350340193245384.jpg

6631350340193245384.jpg

20400 ms

6598095611065987390.jpg

6598095611065987390.jpg

1051 ms

analyse.png

analyse.png

20199 ms

analytics.js

analytics.js

49 ms

collect

collect

12 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

1192 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

3064 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

3400 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

7380 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

6196 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

19509 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2031 ms

blogPhotoAd

blogPhotoAd

19973 ms

close_01.png

close_01.png

48 ms

top_bg.png

top_bg.png

85 ms

bottom_bg.png

bottom_bg.png

88 ms

left_bg.png

left_bg.png

87 ms

right_bg.png

right_bg.png

86 ms

left_top.png

left_top.png

90 ms

right_top.png

right_top.png

90 ms

left_bottom.png

left_bottom.png

128 ms

right_bottom.png

right_bottom.png

130 ms

shadow.png

shadow.png

46 ms

ava.s

ava.s

502 ms

ava.s

ava.s

393 ms

ava.s

ava.s

738 ms

ava.s

ava.s

779 ms

ava.s

ava.s

2560 ms

ava.s

ava.s

789 ms

ava.s

ava.s

992 ms

ava.s

ava.s

1078 ms

ava.s

ava.s

1134 ms

ava.s

ava.s

1173 ms

ava.s

ava.s

3013 ms

ava.s

ava.s

1409 ms

ava.s

ava.s

1486 ms

ava.s

ava.s

1548 ms

ava.s

ava.s

1670 ms

ava.s

ava.s

1752 ms

ava.s

ava.s

1864 ms

ava.s

ava.s

1911 ms

ava.s

ava.s

2015 ms

ava.s

ava.s

2094 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

689 ms

ava.s

ava.s

323 ms

ava.s

ava.s

374 ms

ava.s

ava.s

361 ms

ava.s

ava.s

324 ms

ava.s

ava.s

1876 ms

ava.s

ava.s

2429 ms

ava.s

ava.s

1058 ms

ava.s

ava.s

707 ms

ava.s

ava.s

715 ms

ava.s

ava.s

1077 ms

ava.s

ava.s

1084 ms

ava.s

ava.s

4165 ms

ava.s

ava.s

1486 ms

ava.s

ava.s

3231 ms

ava.s

ava.s

1499 ms

ava.s

ava.s

1610 ms

SEO Factors

zhiheong.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 Zhiheong.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 Zhiheong.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

zhiheong.blog.163.com

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