Access ace.jp. エース株式会社

ace.jp screenshot

6

Performance

Renders faster than
21% of other websites
82

Accessibility

Visual factors better than
that of 52% of websites
75

Best Practices

More advanced features
available than in
35% of websites
92

SEO

Google-friendlier than
74% of websites

First Response

571 ms

Resources Loaded

10.2 sec

Page Rendered

926 ms

ace.jp screenshot

About Website

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

バッグとラゲージの総合メーカー、エース株式会社のオフィシャルサイトです。取り扱いのご商品紹介、修理サービスなどをご紹介いたします。

Visit ace.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value36.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value2.197

0/100

15%

TTI (Time to Interactive)

Value52.9 s

0/100

10%

ace.jp

571 ms

www.ace.jp

739 ms

www.ace.jp

1339 ms

default.css

538 ms

globalnav.css

714 ms

Our browser made a total of 255 requests to load all elements on the main page. We found that 54% of them (137 requests) were addressed to the original Ace.jp, 26% (66 requests) were made to Store.ace.jp and 5% (14 requests) were made to App.chatplus.jp. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Store.ace.jp.

Content Size

16.8 MB

After Optimization

16.4 MB

In fact, the total size of Ace.jp main page is 16.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 16.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 170.0 kB

Original 192.5 kB
After minification 150.5 kB
After compression 22.5 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 41.9 kB, which is 22% 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 170.0 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 139.1 kB

Original 16.2 MB
After minification 16.0 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. Ace images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 47.2 kB

Original 343.1 kB
After minification 335.2 kB
After compression 295.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 47.2 kB or 14% of the original size.

CSS Optimization

-59%

Potential reduce by 71.1 kB

Original 121.2 kB
After minification 99.6 kB
After compression 50.2 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. Ace.jp needs all CSS files to be minified and compressed as it can save up to 71.1 kB or 59% of the original size.

Requests Now

249

After Optimization

191

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

[role]s do not have all required [aria-*] attributes

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

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 Ace.jp 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 Ace.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

ace.jp

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