Tools & Wizards About Us
blog.80tian.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.80tian.com

冻结

Page Load Speed

22.1 sec in total

First Response

3.7 sec

Resources Loaded

18.1 sec

Page Rendered

309 ms

blog.80tian.com screenshot

About Website

Welcome to blog.80tian.com homepage info - get ready to check Blog 80 Tian best content for China right away, or after learning these important things about blog.80tian.com

80天环游网,出游,旅游,旅行,游记,攻略,博客,日志

Visit blog.80tian.com

Key Findings

We analyzed Blog.80tian.com page load time and found that the first response time was 3.7 sec and then it took 18.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. This domain responded with an error, which can significantly jeopardize Blog.80tian.com rating and web reputation

Performance Metrics

blog.80tian.com performance score

0

Network Requests Diagram

blog.80tian.com

3690 ms

common.css

457 ms

content.css

682 ms

head.css

685 ms

06.css

909 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 94% of them (64 requests) were addressed to the original Blog.80tian.com, 3% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Eiv.baidu.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Blog.80tian.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.7 kB (53%)

Content Size

601.0 kB

After Optimization

282.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.80tian.com main page is 601.0 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. 25% of websites need less resources to load. Javascripts take 228.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 79.4 kB

  • Original 91.5 kB
  • After minification 64.5 kB
  • After compression 12.1 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. This page needs HTML code to be minified as it can gain 27.0 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.4 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 17.4 kB

  • Original 207.1 kB
  • After minification 189.7 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. Blog 80 Tian images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 156.3 kB

  • Original 228.2 kB
  • After minification 208.1 kB
  • After compression 71.8 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 156.3 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 65.5 kB

  • Original 74.2 kB
  • After minification 68.9 kB
  • After compression 8.7 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. Blog.80tian.com needs all CSS files to be minified and compressed as it can save up to 65.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (40%)

Requests Now

65

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog 80 Tian. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

blog.80tian.com

blog.80tian.com

3690 ms

common.css

common.css

457 ms

content.css

content.css

682 ms

head.css

head.css

685 ms

06.css

06.css

909 ms

ProvinceCity.js

ProvinceCity.js

909 ms

jquery-1.4.1.min.js

jquery-1.4.1.min.js

1363 ms

head.js

head.js

1134 ms

script06.js

script06.js

1141 ms

TravelListothers.js

TravelListothers.js

1003 ms

member_I.gif

member_I.gif

678 ms

defaultPhoto.jpg

defaultPhoto.jpg

681 ms

member_P.gif

member_P.gif

773 ms

member_O.gif

member_O.gif

903 ms

member_S.gif

member_S.gif

907 ms

member_T.gif

member_T.gif

1633 ms

member_L.gif

member_L.gif

1608 ms

member_D.gif

member_D.gif

1716 ms

member_O2.gif

member_O2.gif

1834 ms

logo1.jpg

logo1.jpg

2807 ms

eyeball.gif

eyeball.gif

1946 ms

telephone.gif

telephone.gif

2511 ms

text3.gif

text3.gif

2178 ms

left.gif

left.gif

2408 ms

right.gif

right.gif

2547 ms

png3.png

png3.png

2545 ms

png2.png

png2.png

2775 ms

png1.png

png1.png

2634 ms

png4.png

png4.png

2738 ms

left.gif

left.gif

2774 ms

right.gif

right.gif

2772 ms

buttom1.gif

buttom1.gif

2864 ms

pic1.gif

pic1.gif

6128 ms

left_1.gif

left_1.gif

3005 ms

right_1.gif

right_1.gif

3004 ms

ad1.jpg

ad1.jpg

3457 ms

pic1.jpg

pic1.jpg

3035 ms

pic6.gif

pic6.gif

3092 ms

bg1.gif

bg1.gif

2764 ms

bg5.gif

bg5.gif

2765 ms

search_bg.gif

search_bg.gif

2795 ms

button1.gif

button1.gif

3318 ms

main.gif

main.gif

2990 ms

indexblogImg.aspx

indexblogImg.aspx

2992 ms

pic.gif

pic.gif

3691 ms

h.js

h.js

1403 ms

bg2.gif

bg2.gif

3147 ms

text1.gif

text1.gif

3018 ms

text2.gif

text2.gif

3018 ms

bg3.gif

bg3.gif

3147 ms

pic2.gif

pic2.gif

3022 ms

bg1.jpg

bg1.jpg

3020 ms

bg2.jpg

bg2.jpg

2411 ms

bg3.jpg

bg3.jpg

2513 ms

21.gif

21.gif

911 ms

s.js

s.js

1060 ms

hm.gif

hm.gif

353 ms

flexslider.css

flexslider.css

683 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

1874 ms

jquery.flexslider.js

jquery.flexslider.js

1004 ms

01.jpg

01.jpg

9609 ms

02.jpg

02.jpg

10255 ms

03.jpg

03.jpg

2108 ms

04.jpg

04.jpg

1231 ms

05.jpg

05.jpg

1688 ms

06.jpg

06.jpg

1923 ms

07.jpg

07.jpg

2324 ms

slider-nav.png

slider-nav.png

229 ms

SEO Factors

blog.80tian.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.80tian.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blog.80tian.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

blog.80tian.com

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