Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

clarins.jp

CLARINS: 《公式》クラランス|植物バイオテックのナチュラルビューティ|スキンケア・メイクアップ

Page Load Speed

5.6 sec in total

First Response

214 ms

Resources Loaded

3.8 sec

Page Rendered

1.6 sec

clarins.jp screenshot

About Website

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

1954年に誕生したフランス No.1のスキンケアブランド。"プラント&サイエンス"の先進技術で作られた植物由来成分をたっぷり含むスキンケアをお試し下さい。

Visit clarins.jp

Key Findings

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

Performance Metrics

clarins.jp performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value28.5 s

0/100

10%

TBT (Total Blocking Time)

Value37,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.178

1/100

15%

TTI (Time to Interactive)

Value54.1 s

0/100

10%

Network Requests Diagram

clarins.jp

214 ms

www.clarins.jp

1526 ms

global_styles.css

32 ms

845457e973de8e19a3bff195066057e5.js

72 ms

define_core_components.css

58 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 67% of them (37 requests) were addressed to the original Clarins.jp, 7% (4 requests) were made to Cdn.tagcommander.com and 5% (3 requests) were made to Sync.commander1.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Clarins.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.6 kB (18%)

Content Size

613.3 kB

After Optimization

502.8 kB

In fact, the total size of Clarins.jp main page is 613.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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 202.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 109.6 kB

  • Original 131.1 kB
  • After minification 131.0 kB
  • After compression 21.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 109.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 202.6 kB
  • After minification 202.6 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. CLARINS images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 880 B

  • Original 103.0 kB
  • After minification 103.0 kB
  • After compression 102.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 53 B

  • Original 176.7 kB
  • After minification 176.7 kB
  • After compression 176.6 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. Clarins.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (78%)

Requests Now

50

After Optimization

11

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

Accessibility Review

clarins.jp accessibility score

72

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

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best Practices

clarins.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

clarins.jp SEO score

88

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Clarins.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 Clarins.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 CLARINS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: