Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

221616.com

【公式】中古車のガリバー

Page Load Speed

4.8 sec in total

First Response

64 ms

Resources Loaded

3 sec

Page Rendered

1.8 sec

221616.com screenshot

About Website

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

[ガリバー]累計販売台数150万台突破、買取続けて30年。全国約460店舗で、中古車探しと車の売却を受付中。保証や返品サービスの充実した良質な在庫が毎日入荷。もちろん車買取もお任せください。お近くのお店はこちらで検索!

Visit 221616.com

Key Findings

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

Performance Metrics

221616.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value7,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value39.9 s

0/100

10%

Network Requests Diagram

221616.com

64 ms

viewport.js

37 ms

style_pc.css

51 ms

header_pc.css

50 ms

footer_pc.css

100 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that all of those requests were addressed to 221616.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 221616.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.0 kB (47%)

Content Size

142.9 kB

After Optimization

76.0 kB

In fact, the total size of 221616.com main page is 142.9 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. 70% of websites need less resources to load. HTML takes 81.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 65.1 kB

  • Original 81.5 kB
  • After minification 76.9 kB
  • After compression 16.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 65.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 1.9 kB

  • Original 61.4 kB
  • After minification 59.5 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. 221616 images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 28 (41%)

Requests Now

69

After Optimization

41

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 221616. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

221616.com accessibility score

88

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

Image elements do not have [alt] attributes

Best Practices

221616.com best practices score

83

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

Page has valid source maps

SEO Factors

221616.com SEO score

85

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 221616.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 221616.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 data is detected on the main page of 221616. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: