Website review, no card needed
clarel.es website review
Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 84 checks
This review found 40 issues worth fixing on clarel.es, 17 of them high impact, across 84 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 287 ms |
| May 16, 2026 | 284 ms |
| May 23, 2026 | 288 ms |
| May 30, 2026 | 288 ms |
| Jun 6, 2026 | 290 ms |
| Jun 13, 2026 | 289 ms |
| Jun 20, 2026 | 286 ms |
| Jun 27, 2026 | 282 ms |
| Jul 4, 2026 | 280 ms |
| Jul 11, 2026 | 281 ms |
| Jul 18, 2026 | 285 ms |
| Jul 25, 2026 | 287 ms |
| Aug 1, 2026 | 285 ms |
| Aug 8, 2026 | 290 ms |
| Aug 15, 2026 | 292 ms |
| Aug 22, 2026 | 300 ms |
| Aug 29, 2026 | 304 ms |
| Sep 5, 2026 | 296 ms |
| Sep 12, 2026 | 294 ms |
| Sep 19, 2026 | 287 ms |
| Sep 26, 2026 | 284 ms |
| Oct 3, 2026 | 285 ms |
| Oct 10, 2026 | 285 ms |
| Oct 17, 2026 | 280 ms |
| Oct 24, 2026 | 278 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
Speed
Render-blocking requests
4.9 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.9 s.
Reduce unused JavaScript
1.9 s · 396 KiBAbout 396 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
cloudfront.net adds 1.2 s
1.2 scloudfront.net costs a phone 1.2 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4 third-party services on the page
4 third-party services load with your homepage (cloudfront.net, connectif.cloud and imgix and others), adding 4.0 MB and 1.2 s of main-thread time.
Improve image delivery
300 ms · 997 KiB13 images could be 997 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
1.1 MB5 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
imgix adds 0 ms
0 msimgix costs a phone 0 ms of main-thread work and 892 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.
connectif.cloud adds 0 ms
0 msconnectif.cloud costs a phone 0 ms of main-thread work and 863 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.
flavedo.io adds 0 ms
0 msflavedo.io costs a phone 0 ms of main-thread work and 600 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.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
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: 539 ms
539 msYour server sent the HTML in 539 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.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 15.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Crema Cuello Y Escote Reafirmante Y Antiarrugas Q10 Nivea 2…”.
Time to Interactive: 18.9 s
18.9 sThe page becomes fully interactive after 18.9 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.257
0.257The layout shifts by 0.257 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 422 ms
422 msReal visitors wait 422 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 244 ms
244 msScripts block taps and scrolling for 244 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 287 ms to 278 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 675 ms
675 msReal visitors wait 675 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.2 MB in 242 requests
4.2 MBYour homepage downloads 4.2 MB in 242 requests on a phone: images 2.3 MB (73), scripts 1.1 MB (106) and fonts 470 KiB (7). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (864 KiB) are 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.
1 image below the first screen load straight away
1 image further down the page (324 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (2 elements)
Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
418 internal links, 7 external
The homepage links to 418 pages on clarel.es and 7 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Compra online en Clarel: Maquillaje, Cosmética y Perfumería con envío rápido y muestras gratis. Todo para tu belleza, h…”.
One H1 headline
Your main headline reads: “Clarel: tu tienda online de maquillaje, cosmética y perfumes que cuida de ti”.
Title: 50 characters
Your title is a healthy 50 characters: “Clarel | Maquillaje, Cosmética y Perfumería online”.
Canonical URL set
The canonical URL is https://www.clarel.es/es/.
Structured data in place
Structured data found: Organization and 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.clarel.es/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.clarel.es/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,487 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without an H1
https://www.clarel.es/es/cosmetica, https://www.clarel.es/es/ofertas/cosmetica, https://www.clarel.es/es/cosmetica/limpieza-facial, https://www.clarel.es/es/cosmetica/limpieza-facial/geles-y-espumas-limpiadoras, https://www.clarel.es/es/cosmetica/cuidado-facial and https://www.clarel.es/es/cosmetica/cuidado-facial/antiarrugas-y-anti-edad and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.clarel.es/es/cosmetica/limpieza-facial, https://www.clarel.es/es/cosmetica/limpieza-facial/desmaquillante-de-ojos, https://www.clarel.es/es/cosmetica/limpieza-facial/tonicos, https://www.clarel.es/es/cosmetica/cuidado-facial and https://www.clarel.es/es/cosmetica/cuidado-facial/antiarrugas-y-anti-edad took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
113 of 113 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 758 words of copy
The homepage carries about 758 words of visible text.
1 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 clarel.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- AWS
Company
- Founded
- 2013
- Headquarters
- Las Rozas de Madrid
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on clarel.es, including 23 speed issues, 3 SEO issues and 7 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.