Website review, no card needed
clarins.com website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 86 checks
This review found 46 issues worth fixing on clarins.com, 15 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
61D- #111,527 of 115,210 reviewed websitesbeats 3%
- #65,616 of 66,425 online storesbeats 1%
- #237 of 272 Salesforce Commerce Cloud storesbeats 11%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.1 s |
| Oct 31, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 169 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 217 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 238 ms |
| Jul 25, 2026 | 260 ms |
| Aug 1, 2026 | 271 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 247 ms |
| Aug 22, 2026 | 227 ms |
| Aug 29, 2026 | 213 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 209 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 216 ms |
| Oct 3, 2026 | 217 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 243 ms |
| Oct 24, 2026 | 254 ms |
| Oct 31, 2026 | 256 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.7 s
3.3 s
5.0 s
6.7 s
8.3 s
10.0 s
11.7 s
13.3 s
Speed
Render-blocking requests
2.2 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Improve image delivery
1.4 s · 776 KiB10 images could be 776 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 7.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 13
13/100Your mobile performance score is 13. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,550 HTML elements
The page has 3,550 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (TikTok, Facebook and TagCommander and others), adding 1.3 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 744 KiB187 files are served with short cache lifetimes, so returning visitors download them again (744 KiB).
TikTok adds 376 ms
376 msTikTok costs a phone 376 ms of main-thread work and 174 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Facebook adds 338 ms
338 msFacebook costs a phone 338 ms of main-thread work and 284 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 324 ms. During a long task the page ignores taps.
ContentSquare adds 299 ms
299 msContentSquare costs a phone 299 ms of main-thread work and 202 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
TagCommander adds 304 ms
304 msTagCommander costs a phone 304 ms of main-thread work and 154 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Didomi adds 171 ms
171 msDidomi costs a phone 171 ms of main-thread work and 335 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
150 ms · 30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 108 ms
108 msYour server sent the HTML in 108 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.61
0.61For real visitors the layout shifts by 0.61 (75th percentile). Good is under 0.1.
Speed Index: 16.2 s
16.2 sVisually, the page fills in at 16.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.4 s
35.4 sThe page becomes fully interactive after 35.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.909
0.909The layout shifts by 0.909 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 169 ms to 256 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.4 MB in 411 requests
5.4 MBYour homepage downloads 5.4 MB in 411 requests on a phone: scripts 3.6 MB (184), images 1.5 MB (65) and stylesheets 124 KiB (51). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (34 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (164 characters)
Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
25 internal links, 0 external
The homepage links to 25 pages on clarins.com and 0 external pages.
5 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “CLARINS® : Best Skin Care, Makeup, Face & Body Creams”.
Canonical URL set
The canonical URL is https://www.clarinsusa.com/.
Structured data in place
Structured data found: WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.clarinsusa.com/sitemap_index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (139 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.clarinsusa.com/llms.txt (3 KiB, 18 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.clarinsusa.com/en/gaming is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.clarinsusa.com/en/my-shopping-bag has no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.clarinsusa.com/en/offers/specialoffers, whose canonical is https://www.clarinsusa.com/en/discover-clarins/US_specialoffers.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.clarinsusa.com/en/my-shopping-bag, https://www.clarinsusa.com/en/spa-and-virtual-services and https://www.clarinsusa.com/en/gaming have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.clarinsusa.com/en/whats-new, https://www.clarinsusa.com/en/skincare/skincare and https://www.clarinsusa.com/en/makeup/600 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
19 small tap targets
19 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “NotSupportedError: The result must not have attributes”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 173 words
The homepage has only about 173 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
4 calls to action
The homepage has 4 calls to action, for example “Shop now”, “Book your consultation” and “Start live consultation”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at clarins.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Nameshield Nameshield Sas
Company
- Headquarters
- Barrington
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on clarins.com, including 28 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.