Access superclassic.jp. SUPER CLASSIC (スーパークラシック) | abrAsus(アブラサス)、SUPER COMSUMER(スーパーコンシューマー)のプロダクトを取り扱うストア

superclassic.jp screenshot

26

Performance

Renders faster than
47% of other websites
90

Accessibility

Visual factors better than
that of 76% of websites
58

Best Practices

More advanced features
available than in
19% of websites
85

SEO

Google-friendlier than
56% of websites

First Response

1.3 sec

Resources Loaded

15.4 sec

Page Rendered

2 sec

superclassic.jp screenshot

About Website

Click here to check amazing SUPER CLASSIC content for Japan. Otherwise, check out these important facts you probably never knew about superclassic.jp

【公式】SUPER CLASSIC(スーパークラシック)は、薄い財布abrAsus(アブラサス)、小さい財布abrAsus、旅行財布abrAsusなど、機能性を追求したプロダクトを取扱うストアです

Visit superclassic.jp

Key Findings

We analyzed Superclassic.jp page load time and found that the first response time was 1.3 sec and then it took 17.4 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)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

superclassic.jp

1274 ms

common.css

449 ms

lightbox.css

302 ms

top.css

305 ms

jquery-1.11.2.min.js

794 ms

Our browser made a total of 234 requests to load all elements on the main page. We found that 80% of them (187 requests) were addressed to the original Superclassic.jp, 2% (4 requests) were made to Tag.ladsp.com and 1% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Superclassic.jp.

Content Size

3.7 MB

After Optimization

3.1 MB

In fact, the total size of Superclassic.jp main page is 3.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.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 106.3 kB

Original 127.7 kB
After minification 111.1 kB
After compression 21.3 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 16.6 kB, which is 13% 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 106.3 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 184.9 kB

Original 3.0 MB
After minification 2.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. SUPER CLASSIC images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 317.4 kB

Original 534.2 kB
After minification 501.2 kB
After compression 216.7 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 317.4 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 25.4 kB

Original 30.6 kB
After minification 23.1 kB
After compression 5.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. Superclassic.jp needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 83% of the original size.

Requests Now

219

After Optimization

178

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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 Superclassic.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 Superclassic.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

superclassic.jp

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