Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 0

    Best Practices

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

97.7 sec in total

First Response

7.1 sec

Resources Loaded

89.8 sec

Page Rendered

824 ms

guocar.com screenshot

About Website

Click here to check amazing Guocar content. Otherwise, check out these important facts you probably never knew about guocar.com

国车网励志于中国汽车第一垂直门户,提供最新最专业的汽车之家报价、汽车新闻、汽车行情、汽车评测、汽车图片、汽车超市、汽车导购等内容为一体的汽车类垂直门户网站。

Visit guocar.com

Key Findings

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

Performance Metrics

guocar.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

guocar.com

7084 ms

global.css

1844 ms

websit_head.css

1387 ms

validator.js

1399 ms

indexv7.css

4301 ms

Our browser made a total of 290 requests to load all elements on the main page. We found that 84% of them (245 requests) were addressed to the original Guocar.com, 3% (10 requests) were made to Cpro.baidustatic.com and 2% (7 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Cpro.baidustatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 741.9 kB (22%)

Content Size

3.3 MB

After Optimization

2.6 MB

In fact, the total size of Guocar.com main page is 3.3 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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 218.9 kB

  • Original 254.2 kB
  • After minification 190.1 kB
  • After compression 35.2 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 64.1 kB, which is 25% 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 218.9 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 250.4 kB

  • Original 2.7 MB
  • After minification 2.4 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. Guocar images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 222.0 kB

  • Original 331.9 kB
  • After minification 316.7 kB
  • After compression 109.9 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 222.0 kB or 67% of the original size.

CSS Optimization

-80%

Potential reduce by 50.5 kB

  • Original 63.3 kB
  • After minification 54.1 kB
  • After compression 12.8 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. Guocar.com needs all CSS files to be minified and compressed as it can save up to 50.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

264

After Optimization

240

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

Accessibility Review

guocar.com accessibility score

45

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.

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.

SEO Factors

guocar.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guocar.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Guocar.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

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