Tools & Wizards About Us
clarins.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

clarins.jp

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

Page Load Speed

2.3 sec in total

First Response

173 ms

Resources Loaded

1.8 sec

Page Rendered

289 ms

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 173 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

clarins.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value38.7 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.687

7/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

clarins.jp

173 ms

clarins.jp

320 ms

www.clarins.jp

1121 ms

global_styles.css

31 ms

845457e973de8e19a3bff195066057e5.js

19 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original Clarins.jp, 2% (1 request) were made to Try.abtasty.com and 2% (1 request) were made to Cdn.cquotient.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Clarins.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.9 kB (19%)

Content Size

761.5 kB

After Optimization

613.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Clarins.jp main page is 761.5 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. 60% of websites need less resources to load. Javascripts take 288.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 147.7 kB

  • Original 174.8 kB
  • After minification 174.7 kB
  • After compression 27.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. 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 147.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 265.8 kB
  • After minification 265.8 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

-0%

Potential reduce by 168 B

  • Original 288.3 kB
  • After minification 288.3 kB
  • After compression 288.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 99 B

  • Original 32.6 kB
  • After minification 32.5 kB
  • After compression 32.5 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 34 (79%)

Requests Now

43

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 43 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 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

clarins.jp

clarins.jp

173 ms

clarins.jp

clarins.jp

320 ms

www.clarins.jp

www.clarins.jp

1121 ms

global_styles.css

global_styles.css

31 ms

845457e973de8e19a3bff195066057e5.js

845457e973de8e19a3bff195066057e5.js

19 ms

define_core_components.css

define_core_components.css

26 ms

variables.css

variables.css

40 ms

productabovethefoldname.css

productabovethefoldname.css

40 ms

trackorder_jp.css

trackorder_jp.css

40 ms

custom-pagedesigner.css

custom-pagedesigner.css

47 ms

webcomponents-loader.js

webcomponents-loader.js

58 ms

pagedesignerbase_styles.css

pagedesignerbase_styles.css

55 ms

tagging.js

tagging.js

55 ms

base_tagging.js

base_tagging.js

55 ms

fonts.css

fonts.css

25 ms

polyfills.js

polyfills.js

23 ms

webcomponents-sd-ce-pf.js

webcomponents-sd-ce-pf.js

81 ms

navigation_styles.css

navigation_styles.css

26 ms

custom-rewardsboutique-hamburger-menu.css

custom-rewardsboutique-hamburger-menu.css

34 ms

custom-logo-70years.css

custom-logo-70years.css

19 ms

generics_lookup_dll.js

generics_lookup_dll.js

44 ms

commons_lookup_dll.js

commons_lookup_dll.js

44 ms

components_lookup_dll.js

components_lookup_dll.js

51 ms

global_script.js

global_script.js

50 ms

app_components_lib.js

app_components_lib.js

53 ms

app_components_account_lib.js

app_components_account_lib.js

52 ms

int_components_janrain_lib.js

int_components_janrain_lib.js

88 ms

app_components_loyalty_lib.js

app_components_loyalty_lib.js

52 ms

app_components_ordergroove_lib.js

app_components_ordergroove_lib.js

52 ms

app_components_tagging_lib.js

app_components_tagging_lib.js

56 ms

app_components_bonus_lib.js

app_components_bonus_lib.js

71 ms

int_components_integrationplatform_lib.js

int_components_integrationplatform_lib.js

70 ms

int_components_ordergroove_lib.js

int_components_ordergroove_lib.js

71 ms

priority_components.js

priority_components.js

71 ms

define_core_components.js

define_core_components.js

71 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

72 ms

dwac-21.7.js

dwac-21.7.js

82 ms

gretel.min.js

gretel.min.js

22 ms

logo-cba-70years.svg

logo-cba-70years.svg

75 ms

Flyout-Precious.png

Flyout-Precious.png

81 ms

megamenu-placeholder.gif

megamenu-placeholder.gif

77 ms

20240610BodyCampaign_ASPOT-PC.jpg

20240610BodyCampaign_ASPOT-PC.jpg

88 ms

expertadvice_icon-honda_maru.svg

expertadvice_icon-honda_maru.svg

127 ms

ui-overlay-shadow.png

ui-overlay-shadow.png

53 ms

online-counselling-widget.jpg

online-counselling-widget.jpg

39 ms

fonts.css

fonts.css

16 ms

Accessibility Review

clarins.jp accessibility score

92

Accessibility Issues

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

Form elements do not have associated labels

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

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

clarins.jp

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: