2.2 sec in total
188 ms
1.8 sec
184 ms
Welcome to clarins.ch homepage info - get ready to check CLARINS best content for Switzerland right away, or after learning these important things about clarins.ch
L'expert du soin de la peau depuis 1954. Découvrez la gamme Clarins; des soins ciblés ultra-efficaces fabriqués à partir d'ingrédients naturels durables.
Visit clarins.chWe analyzed Clarins.ch page load time and found that the first response time was 188 ms and then it took 2 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.
clarins.ch performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value7.9 s
3/100
25%
Value8.7 s
16/100
10%
Value1,210 ms
20/100
30%
Value0.194
63/100
15%
Value12.7 s
14/100
10%
188 ms
321 ms
649 ms
27 ms
33 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 94% of them (45 requests) were addressed to the original Clarins.ch, 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 (649 ms) belongs to the original domain Clarins.ch.
Page size can be reduced by 149.3 kB (20%)
748.3 kB
599.0 kB
In fact, the total size of Clarins.ch main page is 748.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. 50% of websites need less resources to load. Javascripts take 291.7 kB which makes up the majority of the site volume.
Potential reduce by 149.0 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 149.0 kB or 84% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 197 B
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.
Potential reduce by 61 B
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.ch has all CSS files already compressed.
Number of requests can be reduced by 33 (73%)
45
12
The browser has sent 45 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 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
clarins.ch
188 ms
clarins.ch
321 ms
www.clarins.ch
649 ms
global_styles.css
27 ms
fonts.css
33 ms
be651539c393478f0a1af46466b4b708.js
94 ms
define_core_components.css
22 ms
custom-pagedesigner.css
26 ms
webcomponents-loader.js
35 ms
pagedesignerbase_styles.css
35 ms
tagging.js
40 ms
base_tagging.js
44 ms
navigation_styles.css
20 ms
custom-rewardsboutique-hamburger-menu.css
19 ms
custom-logo-70years.css
20 ms
cba-rewards-join-the-club-link.css
19 ms
generics_lookup_dll.js
23 ms
commons_lookup_dll.js
51 ms
components_lookup_dll.js
31 ms
global_script.js
29 ms
app_components_lib.js
39 ms
app_components_tagging_lib.js
27 ms
app_components_bonus_lib.js
41 ms
app_components_rb_lib.js
40 ms
app_components_pgc_lib.js
43 ms
app_components_svs_lib.js
43 ms
int_components_integrationplatform_lib.js
51 ms
int_components_adyen_lib.js
50 ms
app_components_pdp_lib.js
53 ms
app_components_eu_lib.js
57 ms
priority_components.js
58 ms
define_core_components.js
64 ms
dwanalytics-22.2.js
60 ms
dwac-21.7.js
62 ms
gretel.min.js
20 ms
polyfills.js
553 ms
webcomponents-sd-ce-pf.js
460 ms
Pictogram-Gift.svg
81 ms
logo-cba-70years.svg
32 ms
loader-dual-ring-100px.gif
31 ms
megamenu-placeholder.gif
31 ms
Flyout-preciousmega.png
31 ms
Megamenu_GWP_Lancement_Gen9.gif
36 ms
CBA_HP_Aspot-Desktop_DOUBLE-SERUM_2024.jpg
54 ms
expertadvice_icon.svg
53 ms
ui-overlay-shadow.png
49 ms
Services_LiveConsultation-CH-FR.jpg
37 ms
fonts.css
15 ms
clarins.ch accessibility score
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
[aria-*] attributes are not valid or misspelled
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
Links do not have a discernible name
clarins.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
clarins.ch SEO score
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
Document uses legible font sizes
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Clarins.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Clarins.ch 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.
clarins.ch
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: