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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

33.1 sec in total

First Response

4.7 sec

Resources Loaded

27.9 sec

Page Rendered

556 ms

hou610726.blog.163.com screenshot

About Website

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

Visit hou610726.blog.163.com

Key Findings

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

Performance Metrics

hou610726.blog.163.com performance score

0

Network Requests Diagram

hou610726.blog.163.com

4709 ms

c.css

272 ms

b.css

854 ms

7916839961756448643.jpg

1894 ms

3075395595558095531.jpg

2275 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hou610726.blog.163.com, 32% (39 requests) were made to Os.blog.163.com and 24% (29 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Os.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 612.1 kB (23%)

Content Size

2.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 83.8 kB

  • Original 104.7 kB
  • After minification 104.7 kB
  • After compression 20.9 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 83.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 19.4 kB

  • Original 1.8 MB
  • After minification 1.8 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. Hou 610726 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.5 kB

  • Original 521.7 kB
  • After minification 521.6 kB
  • After compression 163.1 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.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 150.3 kB

  • Original 183.6 kB
  • After minification 179.6 kB
  • After compression 33.2 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. Hou610726.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (38%)

Requests Now

117

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

hou610726.blog.163.com

hou610726.blog.163.com

4709 ms

c.css

c.css

272 ms

b.css

b.css

854 ms

7916839961756448643.jpg

7916839961756448643.jpg

1894 ms

3075395595558095531.jpg

3075395595558095531.jpg

2275 ms

001e373a672e15f1217023.jpg

001e373a672e15f1217023.jpg

8063 ms

1711086383424784473.jpg

1711086383424784473.jpg

10526 ms

1166150828513120931.jpg

1166150828513120931.jpg

2973 ms

890305351337259048.jpg

890305351337259048.jpg

648 ms

6598185770959415142.png

6598185770959415142.png

2330 ms

1936829314747870857.jpg

1936829314747870857.jpg

5585 ms

6630146374956642388.jpg

6630146374956642388.jpg

704 ms

6597718478517150889.jpg

6597718478517150889.jpg

472 ms

icon.png

icon.png

34 ms

6630133180817252049.jpg

6630133180817252049.jpg

1528 ms

xcode.png

xcode.png

90 ms

1.0.0.js

1.0.0.js

130 ms

pc.js

pc.js

103 ms

ph.js

ph.js

105 ms

6630503716233801767.jpg

6630503716233801767.jpg

1954 ms

lnkbar.png

lnkbar.png

45 ms

image.png

image.png

60 ms

arrow24.png

arrow24.png

59 ms

newtopbaricon8.png

newtopbaricon8.png

56 ms

6630433347491494203.jpg

6630433347491494203.jpg

2608 ms

1711086383424784725.jpg

1711086383424784725.jpg

898 ms

crossdomain.html

crossdomain.html

786 ms

crossdomain.html

crossdomain.html

889 ms

crossdomain.html

crossdomain.html

767 ms

request.s

request.s

3628 ms

analyse.png

analyse.png

711 ms

empty.png

empty.png

45 ms

ava.s

ava.s

4668 ms

loftericon.png

loftericon.png

432 ms

nb.css

nb.css

22 ms

001e373a672e15f1217024.jpg

001e373a672e15f1217024.jpg

14446 ms

6599325964517998922.jpg

6599325964517998922.jpg

2208 ms

ava.s

ava.s

876 ms

6597886703797265601.jpg

6597886703797265601.jpg

730 ms

background.gif

background.gif

7 ms

player_02.gif

player_02.gif

11 ms

player_06.gif

player_06.gif

12 ms

player_16.gif

player_16.gif

15 ms

player_17.gif

player_17.gif

13 ms

player_23.gif

player_23.gif

23 ms

timeline_1.gif

timeline_1.gif

21 ms

player_29.gif

player_29.gif

15 ms

analyse.png

analyse.png

776 ms

analytics.js

analytics.js

14 ms

collect

collect

16 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

916 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1067 ms

HomeBeanNew.getWeatherCityCode.dwr

HomeBeanNew.getWeatherCityCode.dwr

3985 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1344 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1362 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

1700 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1750 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

3417 ms

blogPhotoAd

blogPhotoAd

364 ms

close_01.png

close_01.png

48 ms

top_bg.png

top_bg.png

46 ms

bottom_bg.png

bottom_bg.png

44 ms

left_bg.png

left_bg.png

44 ms

right_bg.png

right_bg.png

44 ms

left_top.png

left_top.png

45 ms

right_top.png

right_top.png

63 ms

left_bottom.png

left_bottom.png

64 ms

right_bottom.png

right_bottom.png

72 ms

shadow.png

shadow.png

42 ms

ava.s

ava.s

448 ms

ava.s

ava.s

688 ms

ava.s

ava.s

851 ms

ava.s

ava.s

861 ms

ava.s

ava.s

11926 ms

ava.s

ava.s

1045 ms

ava.s

ava.s

5297 ms

ava.s

ava.s

1285 ms

ava.s

ava.s

5000 ms

ava.s

ava.s

20177 ms

ava.s

ava.s

1856 ms

ava.s

ava.s

2319 ms

ava.s

ava.s

2758 ms

ava.s

ava.s

3189 ms

ava.s

ava.s

3274 ms

ava.s

ava.s

3623 ms

ava.s

ava.s

6846 ms

ava.s

ava.s

4037 ms

ava.s

ava.s

4473 ms

ava.s

ava.s

4916 ms

r

r

508 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1242 ms

ava.s

ava.s

7391 ms

ava.s

ava.s

4948 ms

ava.s

ava.s

15871 ms

ava.s

ava.s

5296 ms

ava.s

ava.s

5645 ms

ava.s

ava.s

8735 ms

ava.s

ava.s

6840 ms

ava.s

ava.s

7308 ms

ava.s

ava.s

7738 ms

ava.s

ava.s

7828 ms

ava.s

ava.s

9464 ms

ava.s

ava.s

10362 ms

ava.s

ava.s

9079 ms

ava.s

ava.s

11389 ms

ava.s

ava.s

12292 ms

face50.gif

face50.gif

65 ms

face50.gif

face50.gif

63 ms

face30.gif

face30.gif

64 ms

face39.gif

face39.gif

64 ms

face51.gif

face51.gif

64 ms

face58.gif

face58.gif

65 ms

face56.gif

face56.gif

65 ms

bless.png

bless.png

63 ms

ad

ad

841 ms

ava.s

ava.s

20374 ms

close2.png

close2.png

36 ms

jquery-1.4.2.js

jquery-1.4.2.js

41 ms

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

1310 ms

.gif

.gif

415 ms

face60.png

face60.png

14 ms

SEO Factors

hou610726.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 Hou610726.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 Hou610726.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

hou610726.blog.163.com

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