Tools & Wizards About Us
yangche51.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yangche51.com

www.养车无忧网-汽车自助保养服务，正品汽车保养配件商城，自助保养车主之家-官网首页

Page Load Speed

46 sec in total

First Response

1.6 sec

Resources Loaded

44 sec

Page Rendered

491 ms

yangche51.com screenshot

About Website

Click here to check amazing Yangche 51 content for China. Otherwise, check out these important facts you probably never knew about yangche51.com

yangche51.com

Visit yangche51.com

Key Findings

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

yangche51.com performance score

0

Network Requests Diagram

yangche51.com

1553 ms

www.yangche51.com

3742 ms

common_z20151221.css

3835 ms

home_z20160111.css

3894 ms

jquery-1.6.420130626-1.js

14496 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Yangche51.com, 64% (72 requests) were made to C1.yangche51img.com and 17% (19 requests) were made to C3.yangche51img.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source C1.yangche51img.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 328.1 kB (21%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yangche51.com main page is 1.5 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 53.1 kB

  • Original 70.9 kB
  • After minification 63.1 kB
  • After compression 17.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 7.8 kB, which is 11% 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 53.1 kB or 75% of the original size.

Image Optimization

-14%

Potential reduce by 192.4 kB

  • Original 1.4 MB
  • After minification 1.2 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. Obviously, Yangche 51 needs image optimization as it can save up to 192.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 8.4 kB

  • Original 14.8 kB
  • After minification 14.8 kB
  • After compression 6.5 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 8.4 kB or 56% of the original size.

CSS Optimization

-86%

Potential reduce by 74.2 kB

  • Original 86.8 kB
  • After minification 69.8 kB
  • After compression 12.6 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. Yangche51.com needs all CSS files to be minified and compressed as it can save up to 74.2 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

106

After Optimization

82

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yangche51.com

yangche51.com

1553 ms

www.yangche51.com

www.yangche51.com

3742 ms

common_z20151221.css

common_z20151221.css

3835 ms

home_z20160111.css

home_z20160111.css

3894 ms

jquery-1.6.420130626-1.js

jquery-1.6.420130626-1.js

14496 ms

common_JSClass-index20160114.js

common_JSClass-index20160114.js

13687 ms

swfobject20130621.js

swfobject20130621.js

3740 ms

jquery-select-plugintwo.js

jquery-select-plugintwo.js

3323 ms

jquery-select-plugin-2.js

jquery-select-plugin-2.js

3683 ms

home_z20151219.js

home_z20151219.js

6075 ms

autoFilter20151214.js

autoFilter20151214.js

7143 ms

carsteward20150305.js

carsteward20150305.js

4204 ms

ChildUserAutoModel20150924.js

ChildUserAutoModel20150924.js

6200 ms

jquery.scroll20150325.js

jquery.scroll20150325.js

4720 ms

jQuery.Lazyload20130916.js

jQuery.Lazyload20130916.js

5226 ms

Maintenance20150922.js

Maintenance20150922.js

6742 ms

AutoModelParam20150303.js

AutoModelParam20150303.js

8439 ms

CookieHelper.js

CookieHelper.js

6800 ms

advertload20110216.js

advertload20110216.js

7203 ms

ntkfstat.js

ntkfstat.js

6699 ms

yc-logspring.js

yc-logspring.js

7354 ms

loginbj.jpg

loginbj.jpg

4537 ms

chexing.png

chexing.png

4497 ms

jiantou_xia.png

jiantou_xia.png

5827 ms

btn_red.png

btn_red.png

6332 ms

index_num.png

index_num.png

5139 ms

top_line.jpg

top_line.jpg

5767 ms

logo.png

logo.png

6740 ms

new_hb_03.png

new_hb_03.png

11011 ms

new_hb_05.png

new_hb_05.png

20002 ms

new_hb_06.png

new_hb_06.png

7859 ms

new_hb_07.png

new_hb_07.png

18851 ms

yindaotx.png

yindaotx.png

9342 ms

ben1_1.png

ben1_1.png

10312 ms

ben1_2.png

ben1_2.png

18820 ms

ben_car.png

ben_car.png

18818 ms

ben2_1.png

ben2_1.png

18840 ms

ben2_2.png

ben2_2.png

18818 ms

ben_map.png

ben_map.png

19973 ms

ben3_1.png

ben3_1.png

18830 ms

538.jpg

538.jpg

7156 ms

ben3_2.png

ben3_2.png

18804 ms

457.jpg

457.jpg

7785 ms

258.jpg

258.jpg

9268 ms

259.jpg

259.jpg

19922 ms

ben3_3.png

ben3_3.png

18721 ms

btn_off.png

btn_off.png

18363 ms

maintenancenew.png

maintenancenew.png

18316 ms

fucengxia.png

fucengxia.png

17860 ms

wenhao.jpg

wenhao.jpg

17350 ms

appxiazai.jpg

appxiazai.jpg

16838 ms

andordapp.jpg

andordapp.jpg

15990 ms

iphoneapp.jpg

iphoneapp.jpg

15865 ms

weixin.jpg

weixin.jpg

15323 ms

appdown.gif

appdown.gif

15311 ms

appdown2.jpg

appdown2.jpg

20044 ms

appdown.jpg

appdown.jpg

15193 ms

shop_xia.png

shop_xia.png

15299 ms

by.png

by.png

14908 ms

yindaobj.png

yindaobj.png

16591 ms

xzcxbj.png

xzcxbj.png

18099 ms

tishibj.png

tishibj.png

14797 ms

ban2bj.jpg

ban2bj.jpg

15466 ms

ban3bj.jpg

ban3bj.jpg

17650 ms

nextArrow.png

nextArrow.png

14663 ms

prevArrow.png

prevArrow.png

14770 ms

floatbj.jpg

floatbj.jpg

15496 ms

erweima.png

erweima.png

15916 ms

tip1.png

tip1.png

12452 ms

tip2.png

tip2.png

12782 ms

index_baoyang.png

index_baoyang.png

13196 ms

indexghicon1.png

indexghicon1.png

14978 ms

autobrand.ashx

autobrand.ashx

7476 ms

hm.js

hm.js

7994 ms

AdvertLoad20111026.aspx

AdvertLoad20111026.aspx

7427 ms

userinfo.php

userinfo.php

7396 ms

nt2.js

nt2.js

10547 ms

invite.js

invite.js

7394 ms

newheadtopprovider.aspx

newheadtopprovider.aspx

7376 ms

userautomodelprovider.aspx

userautomodelprovider.aspx

832 ms

GetRecomArticlehtml

GetRecomArticlehtml

7375 ms

loading.gif

loading.gif

7349 ms

hotmaintain.aspx

hotmaintain.aspx

518 ms

zh_cn.js

zh_cn.js

3808 ms

chat.in.js

chat.in.js

7580 ms

icon-jy-mr.png

icon-jy-mr.png

7332 ms

bottom2.png

bottom2.png

5563 ms

beian.png

beian.png

7337 ms

shgs.png

shgs.png

7135 ms

function.png

function.png

6272 ms

btn_on.png

btn_on.png

6845 ms

709500+1000.jpg

709500+1000.jpg

3951 ms

710500+1000.jpg

710500+1000.jpg

2031 ms

711500+1000.jpg

711500+1000.jpg

1737 ms

106500+1000.jpeg

106500+1000.jpeg

5189 ms

107500+1000.jpeg

107500+1000.jpeg

4164 ms

108500+1000.jpeg

108500+1000.jpeg

7316 ms

935500+1000.jpg

935500+1000.jpg

7306 ms

936500+1000.jpg

936500+1000.jpg

5658 ms

938500+1000.jpg

938500+1000.jpg

6145 ms

201604011611232586.jpg

201604011611232586.jpg

6384 ms

201604081511319685.jpg

201604081511319685.jpg

7955 ms

201511061826303902.jpg

201511061826303902.jpg

6616 ms

201603311644549197.jpg

201603311644549197.jpg

7741 ms

201602141741205627.jpg

201602141741205627.jpg

9134 ms

201604071656504978.jpg

201604071656504978.jpg

8491 ms

hm.gif

hm.gif

380 ms

s.js

s.js

10917 ms

kf_9627_kf_9627_1441100171330.js

kf_9627_kf_9627_1441100171330.js

1644 ms

mobileicon.png

mobileicon.png

8205 ms

ydclose.png

ydclose.png

528 ms

hm.gif

hm.gif

739 ms

SEO Factors

yangche51.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yangche51.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Yangche51.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

yangche51.com

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