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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

57.8 sec in total

First Response

17.9 sec

Resources Loaded

39.5 sec

Page Rendered

387 ms

lihoulin2009.blog.163.com screenshot

About Website

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

Visit lihoulin2009.blog.163.com

Key Findings

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

lihoulin2009.blog.163.com performance score

0

Network Requests Diagram

lihoulin2009.blog.163.com

17893 ms

c.css

93 ms

b.css

963 ms

ava.s

809 ms

goodbloghead.png

46 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lihoulin2009.blog.163.com, 18% (10 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 (20.5 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 618.0 kB (25%)

Content Size

2.4 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lihoulin2009.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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 90.5 kB

  • Original 129.8 kB
  • After minification 129.6 kB
  • After compression 39.2 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 90.5 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 14.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. Lihoulin 2009 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 154.8 kB

  • Original 189.8 kB
  • After minification 184.5 kB
  • After compression 34.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. Lihoulin2009.blog.163.com needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (48%)

Requests Now

50

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lihoulin2009.blog.163.com

lihoulin2009.blog.163.com

17893 ms

c.css

c.css

93 ms

b.css

b.css

963 ms

ava.s

ava.s

809 ms

goodbloghead.png

goodbloghead.png

46 ms

r

r

3414 ms

4564961172310468132.jpg

4564961172310468132.jpg

656 ms

icon.png

icon.png

80 ms

2869918862558887485.jpg

2869918862558887485.jpg

647 ms

4022277417212311633.jpg

4022277417212311633.jpg

675 ms

lnkbar.png

lnkbar.png

203 ms

image.png

image.png

267 ms

arrow24.png

arrow24.png

32 ms

6630133180817252049.jpg

6630133180817252049.jpg

977 ms

xcode.png

xcode.png

41 ms

1.0.0.js

1.0.0.js

163 ms

newtopbaricon8.png

newtopbaricon8.png

31 ms

pc.js

pc.js

22 ms

ph.js

ph.js

97 ms

crossdomain.html

crossdomain.html

2369 ms

crossdomain.html

crossdomain.html

2233 ms

crossdomain.html

crossdomain.html

754 ms

request.s

request.s

893 ms

analyse.png

analyse.png

19534 ms

163NewsList.do

163NewsList.do

849 ms

mailEntry.do

mailEntry.do

20459 ms

analyse.png

analyse.png

20260 ms

analytics.js

analytics.js

52 ms

rec.s

rec.s

1217 ms

collect

collect

14 ms

imgsize.ph.126.net

imgsize.ph.126.net

1424 ms

blogPhotoAd

blogPhotoAd

20050 ms

close_01.png

close_01.png

44 ms

top_bg.png

top_bg.png

111 ms

bottom_bg.png

bottom_bg.png

115 ms

left_bg.png

left_bg.png

116 ms

right_bg.png

right_bg.png

127 ms

left_top.png

left_top.png

161 ms

right_top.png

right_top.png

162 ms

left_bottom.png

left_bottom.png

164 ms

right_bottom.png

right_bottom.png

170 ms

shadow.png

shadow.png

38 ms

reset.css

reset.css

101 ms

ad.css

ad.css

102 ms

cdc05e36042744ccb1e819c5ac3654e0.jpg

cdc05e36042744ccb1e819c5ac3654e0.jpg

1020 ms

jquery-1.4.2.js

jquery-1.4.2.js

133 ms

scroll.js

scroll.js

105 ms

bbecd7d520934c0ba8fec4087b9c6266.jpg

bbecd7d520934c0ba8fec4087b9c6266.jpg

1026 ms

91298965028c45c29c4dec44e8ae8ddd.jpg

91298965028c45c29c4dec44e8ae8ddd.jpg

1527 ms

07495ca411cb4725b9d2909fd7232a7f.jpg

07495ca411cb4725b9d2909fd7232a7f.jpg

1024 ms

bfe3bb95db3e4e96b29c2b2624ac6f52.jpg

bfe3bb95db3e4e96b29c2b2624ac6f52.jpg

1928 ms

76e7b9abb3b24b79bd2d49353dce85be.jpg

76e7b9abb3b24b79bd2d49353dce85be.jpg

1770 ms

logo-24.png

logo-24.png

73 ms

discount-1.png

discount-1.png

72 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

4967 ms

SEO Factors

lihoulin2009.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 Lihoulin2009.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 Lihoulin2009.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

lihoulin2009.blog.163.com

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