Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

17.com

17汽车网(17.com)17买车,一起省钱

Page Load Speed

40.1 sec in total

First Response

1.4 sec

Resources Loaded

38.2 sec

Page Rendered

437 ms

17.com screenshot

About Website

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

「17汽车网」汽车资讯,本地经销商最新报价,汽车4S店优惠/品牌促销、汽车团购活动,品牌齐全,就在17汽车网!

Visit 17.com

Key Findings

We analyzed 17.com page load time and found that the first response time was 1.4 sec and then it took 38.7 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

17.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

17.com

1421 ms

www.17.com

6379 ms

jquery.min.js

3669 ms

common_style.css

1207 ms

tuangou_index.css

1285 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 16% of them (18 requests) were addressed to the original 17.com, 62% (69 requests) were made to Images.17.com and 5% (6 requests) were made to 17js.17.com. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Images.17.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.5 kB (11%)

Content Size

1.1 MB

After Optimization

981.4 kB

In fact, the total size of 17.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. 35% of websites need less resources to load. Images take 896.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.8 kB

  • Original 83.1 kB
  • After minification 69.1 kB
  • After compression 19.3 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 14.0 kB, which is 17% 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 63.8 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 35.3 kB

  • Original 896.7 kB
  • After minification 861.4 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. 17 images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 12.1 kB

  • Original 109.2 kB
  • After minification 106.9 kB
  • After compression 97.2 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 12.1 kB or 11% of the original size.

CSS Optimization

-81%

Potential reduce by 15.3 kB

  • Original 18.8 kB
  • After minification 17.0 kB
  • After compression 3.5 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. 17.com needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

106

After Optimization

81

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

Accessibility Review

17.com accessibility score

51

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

17.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

17.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 17.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 17.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

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