Tools & Wizards About Us
qichetong.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

qichetong.com

登录

Page Load Speed

58.9 sec in total

First Response

1.6 sec

Resources Loaded

57.1 sec

Page Rendered

215 ms

qichetong.com screenshot

About Website

Welcome to qichetong.com homepage info - get ready to check Qichetong best content for China right away, or after learning these important things about qichetong.com

Visit qichetong.com

Key Findings

We analyzed Qichetong.com page load time and found that the first response time was 1.6 sec and then it took 57.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 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

qichetong.com performance score

0

Network Requests Diagram

i.yiche.com

1552 ms

login.aspx

6733 ms

jquery-1.8.1.min.js

9407 ms

2014gerenzhongxin_pc_friendlogin_style-20160316154459-838.css

14406 ms

c.js

12810 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Qichetong.com, 14% (2 requests) were made to I.yiche.com and 14% (2 requests) were made to Js.inc.baa.bitautotech.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Webtrends.yccdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (51%)

Content Size

227.2 kB

After Optimization

112.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qichetong.com main page is 227.2 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. Only 5% of websites need less resources to load. Javascripts take 111.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 6.5 kB

  • Original 9.4 kB
  • After minification 7.3 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 22% 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 6.5 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 45 B

  • Original 60.8 kB
  • After minification 60.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. Qichetong images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 72.7 kB

  • Original 111.8 kB
  • After minification 108.6 kB
  • After compression 39.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 72.7 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 35.8 kB

  • Original 45.2 kB
  • After minification 45.2 kB
  • After compression 9.4 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. Qichetong.com needs all CSS files to be minified and compressed as it can save up to 35.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

10

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qichetong. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

i.yiche.com

i.yiche.com

1552 ms

login.aspx

login.aspx

6733 ms

jquery-1.8.1.min.js

jquery-1.8.1.min.js

9407 ms

2014gerenzhongxin_pc_friendlogin_style-20160316154459-838.css

2014gerenzhongxin_pc_friendlogin_style-20160316154459-838.css

14406 ms

c.js

c.js

12810 ms

dcs_tag_baa9.js

dcs_tag_baa9.js

7098 ms

;

;

1 ms

allbg.png

allbg.png

1943 ms

checkbox.png

checkbox.png

1649 ms

2014indexbg13.png

2014indexbg13.png

6370 ms

iwt-min20151127.js

iwt-min20151127.js

1737 ms

wtid.js

wtid.js

17541 ms

irt

irt

1241 ms

dcs.gif

dcs.gif

19849 ms

SEO Factors

qichetong.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 Qichetong.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 Qichetong.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

qichetong.com

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