mustela.com.tr website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 2.9 MB and 2.5 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 950 ms of main-thread work and 813 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

Shopify costs a phone 223 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.

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

22 files are served with short cache lifetimes, so returning visitors download them again (242 KiB).

88 KiB could be saved by minifying JavaScript.

About 53 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 5.1 MB in 278 requests on a phone: scripts 2.8 MB (124), images 1.0 MB (49) and other files 657 KiB (65). Under 2 MB keeps phones on slow connections fast.

1 image (41 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.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 81 characters, so Google will cut it off around 60: “Yenidoğandan İtibaren Tüm Ailenizin Cilt Bakım Uzmanı | Mustela | Mustela Türkiye”.

The homepage links to 281 pages on mustela.com.tr and 7 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.mustela.com.tr/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.

https://www.mustela.com.tr/collections/tum-urunlerimiz and https://www.mustela.com.tr/collections/tum-urunler all use the title “Tüm Ürünlerimiz | Mustela Türkiye”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mustela.com.tr/collections/tum-urunlerimiz and https://www.mustela.com.tr/collections/tum-urunler use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mustela.com.tr/collections/tum-urunler, whose canonical is https://www.mustela.com.tr/collections/tum-urunlerimiz. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mustela.com.tr/pages/cilt-tipi-testi has no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/939520189/791058197/square.jpg?1764245695.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

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

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