Website review, no card needed

dermalogica.es logo

dermalogica.es website review

Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 86 checks

This review found 42 issues worth fixing on dermalogica.es, 13 of them high impact, across 86 checks. The most urgent: page weight: 41.7 MB in 381 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.9 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
214 ms173 msMay 16Oct 31200 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026192 ms
May 23, 2026182 ms
May 30, 2026193 ms
Jun 6, 2026208 ms
Jun 13, 2026201 ms
Jun 20, 2026200 ms
Jun 27, 2026195 ms
Jul 4, 2026190 ms
Jul 11, 2026188 ms
Jul 18, 2026178 ms
Jul 25, 2026180 ms
Aug 1, 2026178 ms
Aug 8, 2026178 ms
Aug 15, 2026193 ms
Aug 22, 2026207 ms
Sep 12, 2026206 ms
Sep 19, 2026201 ms
Sep 26, 2026203 ms
Oct 3, 2026209 ms
Oct 10, 2026198 ms
Oct 17, 2026209 ms
Oct 24, 2026209 ms
Oct 31, 2026200 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

Full-page screenshot of dermalogica.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dermalogica.es at 0.7 s0.7 s
  2. dermalogica.es at 1.5 s1.5 s
  3. dermalogica.es at 2.2 s2.2 s
  4. dermalogica.es at 2.9 s2.9 s
  5. dermalogica.es at 3.7 s3.7 s
  6. dermalogica.es at 4.4 s4.4 s
  7. dermalogica.es at 5.1 s5.1 s
  8. dermalogica.es at 5.9 s5.9 s

Speed

12 to fix56
  • 5,050 HTML elements

    The page has 5,050 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    300 ms · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 1.8 MB

    54 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Yotpo, heyamplify.com and pickystory.com and others), adding 2.9 MB and 981 ms of main-thread time.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Improve image delivery

    811 KiB

    21 images could be 811 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Yotpo adds 310 ms

    310 ms

    Yotpo costs a phone 310 ms of main-thread work and 645 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.

  • pickystory.com adds 116 ms

    116 ms

    pickystory.com costs a phone 116 ms of main-thread work and 1.1 MB 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.

  • Klaviyo adds 106 ms

    106 ms

    Klaviyo costs a phone 106 ms of main-thread work and 342 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.

  • Reviews.io adds 108 ms

    108 ms

    Reviews.io costs a phone 108 ms of main-thread work and 320 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.

  • Minify JavaScript

    150 ms · 132 KiB

    132 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    80 ms · 90 KiB

    About 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 80 ms faster on a phone.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need.

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • 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.

  • Time to Interactive: 33.7 s

    33.7 s

    The page becomes fully interactive after 33.7 s. Good is under 3.8 s.

  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 7.4 s

    7.4 s

    Visually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.

  • Real-user INP: 211 ms

    211 ms

    Real visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.21

    0.21

    For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 441 ms

    441 ms

    Scripts block taps and scrolling for 441 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 192 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 555 ms

    555 ms

    Real visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.022

    0.022

    The layout barely moves while loading (CLS 0.022, good is under 0.1).

Images and page weight

3 to fix60
  • Page weight: 41.7 MB in 381 requests

    41.7 MB

    Your homepage downloads 41.7 MB in 381 requests on a phone: media 35.1 MB (4), scripts 3.8 MB (139) and images 1.2 MB (46). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HP_Banner_mobile_Brand_campaign_DMF_ohne_Siegel.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    3 KiB

    1 image is downloaded at several times the size a phone draws it, for example Trockene_Haut.jpg at 342 px wide, shown at 110 px. Resized copies would save about 3 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 11.8 g of CO₂ per visit

    11.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 11.82 g of CO₂e: 1418.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 8788
  • 25 text elements with low contrast

    25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Form elements should have a visible label (11 elements)

    Form elements should have a visible label: 11 elements on the page fail this check, rated serious by axe-core.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 17 images without alt text

    17 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 links without text

    18 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8586
  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Dermalogica | Tienda oficial | Cuidado de la piel a nivel de instituto – Dermalogica”.

  • Meta description is long (204 characters)

    Your meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 207 internal links, 22 external

    The homepage links to 207 pages on dermalogica.es and 22 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Cuidado de la piel con calidad profesional”.

  • Canonical URL set

    The canonical URL is https://www.dermalogica.es/.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.dermalogica.es/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,120 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.dermalogica.es/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.dermalogica.es/cdn/shop/t/202/assets/quantity-popover.css?v=223766' because it…”.

2 checks passed
  • Tap targets are thumb-sized

    88 of 101 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 79 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 1,296 words of copy

    The homepage carries about 1,296 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Subscribe to Unlock”, “Shop” and “Clear Start”.

  • 27 short forms

    27 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 2 of them by other companies (measured from a US location before any click).

  • 50 other companies contacted

    Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 dermalogica.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seowill Ai Seo · Elevar Conversion Tracking · Bundler Bundles App · Amplify Bundles Upsell · Klaviyo Email Marketing Sms · Doofinder Search Discovery · Gorgias Live Chat Helpdesk · Microsoft Clarity · Geoip Country Redirect · Yotpo Loyalty Rewards · Seowill Redirects · Forms · Reviews Co Uk Product And Merchant Review Collection · Polar Analytics · nice-team.net · pickystory.com · mulwi.com · linkster.co · rechargecdn.com · goaffpro.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
4 open roles
Teams
CA-Ecommerce (2), CA-Customer Service (1), CA-Sales (1)
Job board
bamboohr

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on dermalogica.es, including 21 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25