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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

32.3 sec in total

First Response

8.6 sec

Resources Loaded

23.5 sec

Page Rendered

278 ms

hanguozhengrong.blog.163.com screenshot

About Website

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

Visit hanguozhengrong.blog.163.com

Key Findings

We analyzed Hanguozhengrong.blog.163.com page load time and found that the first response time was 8.6 sec and then it took 23.8 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

hanguozhengrong.blog.163.com performance score

0

Network Requests Diagram

hanguozhengrong.blog.163.com

8570 ms

c.css

24 ms

b.css

804 ms

5728860200992701723.jpg

1006 ms

icon.png

51 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 594.7 kB (48%)

Content Size

1.2 MB

After Optimization

643.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 77.0 kB

  • Original 97.7 kB
  • After minification 97.6 kB
  • After compression 20.7 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 77.0 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 10.3 kB

  • Original 437.4 kB
  • After minification 427.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. Hanguozhengrong 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 149.2 kB

  • Original 182.0 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. Hanguozhengrong.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 27 (56%)

Requests Now

48

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

hanguozhengrong.blog.163.com

hanguozhengrong.blog.163.com

8570 ms

c.css

c.css

24 ms

b.css

b.css

804 ms

5728860200992701723.jpg

5728860200992701723.jpg

1006 ms

icon.png

icon.png

51 ms

5762074248244591780.jpg

5762074248244591780.jpg

19786 ms

5762074248244591781.jpg

5762074248244591781.jpg

19786 ms

5728860200992701720.jpg

5728860200992701720.jpg

4406 ms

lnkbar.png

lnkbar.png

12 ms

6630133180817252049.jpg

6630133180817252049.jpg

4312 ms

xcode.png

xcode.png

11 ms

image.png

image.png

6 ms

arrow24.png

arrow24.png

10 ms

newtopbaricon8.png

newtopbaricon8.png

8 ms

pc.js

pc.js

25 ms

ph.js

ph.js

21 ms

1.0.0.js

1.0.0.js

89 ms

crossdomain.html

crossdomain.html

2514 ms

crossdomain.html

crossdomain.html

2518 ms

crossdomain.html

crossdomain.html

3409 ms

request.s

request.s

671 ms

analyse.png

analyse.png

878 ms

empty.png

empty.png

36 ms

ava.s

ava.s

955 ms

loftericon.png

loftericon.png

1304 ms

ava.s

ava.s

3325 ms

3971611921404158236.jpg

3971611921404158236.jpg

12754 ms

analyse.png

analyse.png

2283 ms

analytics.js

analytics.js

10 ms

collect

collect

22 ms

blogPhotoAd

blogPhotoAd

448 ms

close_01.png

close_01.png

11 ms

top_bg.png

top_bg.png

13 ms

bottom_bg.png

bottom_bg.png

10 ms

left_bg.png

left_bg.png

12 ms

right_bg.png

right_bg.png

12 ms

left_top.png

left_top.png

12 ms

right_top.png

right_top.png

12 ms

left_bottom.png

left_bottom.png

13 ms

right_bottom.png

right_bottom.png

14 ms

shadow.png

shadow.png

10 ms

r

r

1904 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

960 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1364 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1404 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1676 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

6472 ms

close2.png

close2.png

6 ms

ad

ad

668 ms

ava.s

ava.s

430 ms

jquery-1.4.2.js

jquery-1.4.2.js

74 ms

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

2920 ms

SEO Factors

hanguozhengrong.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 Hanguozhengrong.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 Hanguozhengrong.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

hanguozhengrong.blog.163.com

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