Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

autoflags.co.jp

「デリカにこだわる」オートフラッグス

Page Load Speed

10.5 sec in total

First Response

538 ms

Resources Loaded

9 sec

Page Rendered

871 ms

autoflags.co.jp screenshot

About Website

Click here to check amazing Autoflags content for Japan. Otherwise, check out these important facts you probably never knew about autoflags.co.jp

デリカ専門店オートフラッグス GOQBUTOをはじめBUSTERS、XrossFourXtremeなど、オリジナルブランドを展開 MLJ代理店 KMCホイール BF-Goodrich TOYOタイヤ

Visit autoflags.co.jp

Key Findings

We analyzed Autoflags.co.jp page load time and found that the first response time was 538 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

autoflags.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value29.9 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value7,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value38.6 s

0/100

10%

Network Requests Diagram

autoflags.co.jp

538 ms

www.autoflags.co.jp

773 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css

1045 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

1158 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

570 ms

Our browser made a total of 178 requests to load all elements on the main page. We found that 58% of them (103 requests) were addressed to the original Autoflags.co.jp, 15% (27 requests) were made to Static.xx.fbcdn.net and 10% (18 requests) were made to Web.xaas.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Autoflags.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.8 kB (18%)

Content Size

2.4 MB

After Optimization

1.9 MB

In fact, the total size of Autoflags.co.jp main page is 2.4 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 73.0 kB

  • Original 90.9 kB
  • After minification 88.8 kB
  • After compression 18.0 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 73.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.6 kB

  • Original 1.8 MB
  • After minification 1.8 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. Autoflags images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 214.9 kB

  • Original 307.3 kB
  • After minification 295.9 kB
  • After compression 92.4 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 214.9 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 144.3 kB

  • Original 177.2 kB
  • After minification 162.8 kB
  • After compression 32.9 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. Autoflags.co.jp needs all CSS files to be minified and compressed as it can save up to 144.3 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

175

After Optimization

103

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

Accessibility Review

autoflags.co.jp accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

autoflags.co.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

autoflags.co.jp SEO score

86

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

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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