Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gazoo.com

GAZOO.com クルマ情報サイトー愛車から最新の自動車情報までお届け

Page Load Speed

7.8 sec in total

First Response

601 ms

Resources Loaded

6.8 sec

Page Rendered

367 ms

gazoo.com screenshot

About Website

Visit gazoo.com now to see the best up-to-date GAZOO content for Japan and also check out these interesting facts you probably never knew about gazoo.com

GAZOO.comは、ニュースや新車、中古車情報だけでなく、皆さまの愛車を取材させていただいた記事、車好きのコラムやお役立ち情報など、メーカー問わず愛車の魅力を紹介しています。また、モビことではクルマ好きの皆さまが自ら愛車情報を発信することもできます。

Visit gazoo.com

Key Findings

We analyzed Gazoo.com page load time and found that the first response time was 601 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

gazoo.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

gazoo.com

601 ms

index.aspx

1370 ms

corev15.css

1349 ms

searchv15.css

895 ms

non-corev15.css

454 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 83% of them (94 requests) were addressed to the original Gazoo.com, 4% (4 requests) were made to Beacon.tws.toyota.jp and 3% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gazoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (43%)

Content Size

5.7 MB

After Optimization

3.3 MB

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

HTML Optimization

-82%

Potential reduce by 199.4 kB

  • Original 242.7 kB
  • After minification 229.7 kB
  • After compression 43.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 199.4 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 484.9 kB

  • Original 3.2 MB
  • After minification 2.7 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, GAZOO needs image optimization as it can save up to 484.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 1.3 MB

  • Original 1.8 MB
  • After minification 1.6 MB
  • After compression 459.3 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 1.3 MB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 427.2 kB

  • Original 488.5 kB
  • After minification 347.2 kB
  • After compression 61.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. Gazoo.com needs all CSS files to be minified and compressed as it can save up to 427.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (57%)

Requests Now

108

After Optimization

46

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

Accessibility Review

gazoo.com accessibility score

96

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

gazoo.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

gazoo.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gazoo.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Gazoo.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 GAZOO. 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: