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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

30.3 sec in total

First Response

3.5 sec

Resources Loaded

26.4 sec

Page Rendered

326 ms

litaixian2012.blog.163.com screenshot

About Website

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

Visit litaixian2012.blog.163.com

Key Findings

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

Performance Metrics

litaixian2012.blog.163.com performance score

0

Network Requests Diagram

litaixian2012.blog.163.com

3520 ms

c.css

38 ms

b.css

969 ms

6630133180817252049.jpg

567 ms

xcode.png

10 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Litaixian2012.blog.163.com, 24% (19 requests) were made to Os.blog.163.com and 14% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Img7.ph.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 586.8 kB (54%)

Content Size

1.1 MB

After Optimization

499.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 71.7 kB

  • Original 90.5 kB
  • After minification 90.5 kB
  • After compression 18.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 71.7 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 9.4 kB

  • Original 294.9 kB
  • After minification 285.5 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. Litaixian 2012 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 147.1 kB

  • Original 179.1 kB
  • After minification 175.4 kB
  • After compression 32.0 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. Litaixian2012.blog.163.com needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

76

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

litaixian2012.blog.163.com

litaixian2012.blog.163.com

3520 ms

c.css

c.css

38 ms

b.css

b.css

969 ms

6630133180817252049.jpg

6630133180817252049.jpg

567 ms

xcode.png

xcode.png

10 ms

1.0.0.js

1.0.0.js

89 ms

pc.js

pc.js

14 ms

ph.js

ph.js

13 ms

5772207347405742436.jpg

5772207347405742436.jpg

1212 ms

blog_rec.png

blog_rec.png

48 ms

5791066170845357749.jpg

5791066170845357749.jpg

717 ms

5791066170845357824.jpg

5791066170845357824.jpg

476 ms

5791066170845357823.jpg

5791066170845357823.jpg

482 ms

5791066170845357826.jpg

5791066170845357826.jpg

558 ms

5772207347405742474.jpg

5772207347405742474.jpg

557 ms

5791066170845357828.jpg

5791066170845357828.jpg

716 ms

5791066170845357830.jpg

5791066170845357830.jpg

723 ms

5791066170845357832.jpg

5791066170845357832.jpg

825 ms

5791066170845357836.jpg

5791066170845357836.jpg

816 ms

5791066170845357834.jpg

5791066170845357834.jpg

952 ms

icon.png

icon.png

33 ms

lnkbar.png

lnkbar.png

34 ms

image.png

image.png

34 ms

arrow24.png

arrow24.png

34 ms

newtopbaricon8.png

newtopbaricon8.png

34 ms

crossdomain.html

crossdomain.html

2691 ms

crossdomain.html

crossdomain.html

498 ms

crossdomain.html

crossdomain.html

645 ms

request.s

request.s

480 ms

analyse.png

analyse.png

497 ms

empty.png

empty.png

32 ms

6597742667772547042.jpg

6597742667772547042.jpg

5189 ms

6597177518797257727.jpeg

6597177518797257727.jpeg

19873 ms

ava.s

ava.s

6320 ms

loftericon.png

loftericon.png

1881 ms

ava.s

ava.s

3153 ms

analyse.png

analyse.png

458 ms

analytics.js

analytics.js

21 ms

collect

collect

15 ms

blogPhotoAd

blogPhotoAd

246 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

10 ms

bottom_bg.png

bottom_bg.png

9 ms

left_bg.png

left_bg.png

11 ms

right_bg.png

right_bg.png

12 ms

left_top.png

left_top.png

40 ms

right_top.png

right_top.png

11 ms

left_bottom.png

left_bottom.png

40 ms

right_bottom.png

right_bottom.png

39 ms

shadow.png

shadow.png

9 ms

r

r

599 ms

ad

ad

537 ms

close2.png

close2.png

4 ms

jquery-1.4.2.js

jquery-1.4.2.js

19 ms

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

ad.bid.material_f84d827cd06e43a28ef019b53849c47d

4303 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

16157 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1299 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1381 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

16358 ms

HomeBeanNew.getClassifyModuleData.dwr

HomeBeanNew.getClassifyModuleData.dwr

3859 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

2270 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1036 ms

ava.s

ava.s

852 ms

ava.s

ava.s

688 ms

ava.s

ava.s

854 ms

ava.s

ava.s

2558 ms

ava.s

ava.s

894 ms

ava.s

ava.s

1358 ms

ava.s

ava.s

3215 ms

ava.s

ava.s

12669 ms

ava.s

ava.s

1344 ms

ava.s

ava.s

17279 ms

ava.s

ava.s

1799 ms

ava.s

ava.s

2029 ms

ava.s

ava.s

2701 ms

ava.s

ava.s

2385 ms

ava.s

ava.s

2735 ms

ava.s

ava.s

522 ms

SEO Factors

litaixian2012.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 Litaixian2012.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 Litaixian2012.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

litaixian2012.blog.163.com

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