Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

clasic.jp

白衣 スクラブ ナース服ほか おしゃれ白衣のクラシコ公式通販

Page Load Speed

7.3 sec in total

First Response

587 ms

Resources Loaded

6.4 sec

Page Rendered

341 ms

clasic.jp screenshot

About Website

Welcome to clasic.jp homepage info - get ready to check Clasic best content for Japan right away, or after learning these important things about clasic.jp

おしゃれな白衣通販のクラシコ【Classico】公式サイト。デザイナーを起用し、上質さと機能性を兼ね備えたスタイリッシュな白衣・ケーシー・スクラブ・ナース服を開発販売しております。

Visit clasic.jp

Key Findings

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

Performance Metrics

clasic.jp performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value25.7 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value3,060 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.525

14/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

clasic.jp

587 ms

www.clasic.jp

1249 ms

avatars.css

298 ms

imgareaselect.css

299 ms

dashicons.min.css

444 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 23% of them (30 requests) were addressed to the original Clasic.jp, 29% (38 requests) were made to S3-ap-northeast-1.amazonaws.com and 5% (6 requests) were made to V9999.adv.admeme.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source S3-ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 523.7 kB (31%)

Content Size

1.7 MB

After Optimization

1.2 MB

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

HTML Optimization

-82%

Potential reduce by 67.7 kB

  • Original 82.5 kB
  • After minification 62.4 kB
  • After compression 14.8 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 20.0 kB, which is 24% 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 67.7 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 27.1 kB

  • Original 990.3 kB
  • After minification 963.2 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. Clasic images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 252.8 kB

  • Original 381.1 kB
  • After minification 341.1 kB
  • After compression 128.3 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 252.8 kB or 66% of the original size.

CSS Optimization

-76%

Potential reduce by 176.1 kB

  • Original 230.5 kB
  • After minification 182.7 kB
  • After compression 54.4 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. Clasic.jp needs all CSS files to be minified and compressed as it can save up to 176.1 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (59%)

Requests Now

120

After Optimization

49

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

Accessibility Review

clasic.jp accessibility score

65

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.

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

clasic.jp SEO score

100

Search Engine Optimization Advices

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

    JA

  • Encoding

    UTF-8

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