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

ace.jp screenshot

11

Performance

Renders faster than
24% of other websites
85

Accessibility

Visual factors better than
that of 60% of websites
75

Best Practices

More advanced features
available than in
36% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

557 ms

Resources Loaded

10.6 sec

Page Rendered

344 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 557 ms and then it took 10.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.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value35.3 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value1.217

1/100

15%

TTI (Time to Interactive)

Value33.1 s

0/100

10%

ace.jp

557 ms

www.ace.jp

537 ms

www.ace.jp

979 ms

default.css

222 ms

common.css

444 ms

Our browser made a total of 209 requests to load all elements on the main page. We found that 97% of them (203 requests) were addressed to the original Ace.jp, 1% (2 requests) were made to Ssl.google-analytics.com and 0% (1 request) were made to B92.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ace.jp.

Content Size

2.3 MB

After Optimization

2.0 MB

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

HTML Optimization

-81%

Potential reduce by 29.8 kB

Original 36.7 kB
After minification 28.7 kB
After compression 6.9 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 8.0 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 29.8 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 181.5 kB

Original 2.1 MB
After minification 1.9 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

-51%

Potential reduce by 74.1 kB

Original 145.6 kB
After minification 136.2 kB
After compression 71.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 74.1 kB or 51% of the original size.

CSS Optimization

-82%

Potential reduce by 16.7 kB

Original 20.5 kB
After minification 14.4 kB
After compression 3.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. Ace.jp needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 82% of the original size.

Requests Now

205

After Optimization

188

The browser has sent 205 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 7 to 1 for JavaScripts and from 4 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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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

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

High

Links are not crawlable

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

N/A
Encoding

SHIFT_JIS

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ace.jp main page’s claimed encoding is shift_jis. 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

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: