Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

scolar.jp

レトロで個性的なブランドならScoLar【スカラー】

Page Load Speed

10.7 sec in total

First Response

553 ms

Resources Loaded

9.6 sec

Page Rendered

548 ms

scolar.jp screenshot

About Website

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

ScoLar【スカラー】ではレトロで個性的なファッションを提案、コーディネートの主役になれる服を提供しています。幅広い年代にご利用頂けるゆったりとしたシルエットで、レトロな雰囲気を彷彿させる独創的でインパクトのあるデザインです。

Visit scolar.jp

Key Findings

We analyzed Scolar.jp page load time and found that the first response time was 553 ms and then it took 10.2 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

scolar.jp performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value40.1 s

0/100

25%

SI (Speed Index)

Value27.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.816

4/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

Network Requests Diagram

scolar.jp

553 ms

www.scolar.jp

743 ms

common.css

340 ms

jquery-1.8.3.min.js

729 ms

jquery.easing.1.3.js

362 ms

Our browser made a total of 177 requests to load all elements on the main page. We found that 84% of them (149 requests) were addressed to the original Scolar.jp, 6% (10 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to R2.future-shop.jp. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Scolar.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.6 kB (7%)

Content Size

4.3 MB

After Optimization

4.0 MB

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

HTML Optimization

-81%

Potential reduce by 43.8 kB

  • Original 54.0 kB
  • After minification 44.4 kB
  • After compression 10.1 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 9.6 kB, which is 18% 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 43.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 55.5 kB

  • Original 3.9 MB
  • After minification 3.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. Scolar images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 149.9 kB

  • Original 245.9 kB
  • After minification 212.3 kB
  • After compression 96.1 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 149.9 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 39.4 kB

  • Original 46.6 kB
  • After minification 32.0 kB
  • After compression 7.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. Scolar.jp needs all CSS files to be minified and compressed as it can save up to 39.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (20%)

Requests Now

171

After Optimization

136

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

Accessibility Review

scolar.jp accessibility score

87

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

scolar.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

scolar.jp SEO score

64

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

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

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