Website review, no card needed

mustelausa.com logo

mustelausa.com website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 87 checks

This review found 36 issues worth fixing on mustelausa.com, 15 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.5 s1.8 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.3 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
162 ms125 msMay 16Oct 31158 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026130 ms
Jun 6, 2026137 ms
Jun 13, 2026138 ms
Jun 20, 2026141 ms
Jun 27, 2026145 ms
Jul 4, 2026139 ms
Jul 11, 2026141 ms
Jul 18, 2026139 ms
Jul 25, 2026139 ms
Aug 1, 2026138 ms
Aug 8, 2026138 ms
Aug 15, 2026138 ms
Aug 22, 2026140 ms
Aug 29, 2026144 ms
Sep 5, 2026139 ms
Sep 12, 2026139 ms
Sep 19, 2026139 ms
Sep 26, 2026141 ms
Oct 3, 2026145 ms
Oct 10, 2026150 ms
Oct 17, 2026153 ms
Oct 24, 2026154 ms
Oct 31, 2026158 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 mustelausa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mustelausa.com at 1.6 s1.6 s
  2. mustelausa.com at 3.2 s3.2 s
  3. mustelausa.com at 4.8 s4.8 s
  4. mustelausa.com at 6.4 s6.4 s
  5. mustelausa.com at 8.0 s8.0 s
  6. mustelausa.com at 9.6 s9.6 s
  7. mustelausa.com at 11.2 s11.2 s
  8. mustelausa.com at 12.8 s12.8 s

Speed

10 to fix34
  • Reduce unused JavaScript

    2.5 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.0 s

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

  • 8 third-party services on the page

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

  • Google Tag Manager adds 739 ms

    739 ms

    Google Tag Manager costs a phone 739 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.

  • Use efficient cache lifetimes

    300 ms · 375 KiB

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

  • Legacy JavaScript

    300 ms · 77 KiB

    Polyfills for old browsers add 77 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Klaviyo adds 301 ms

    301 ms

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

  • ContentSquare adds 319 ms

    319 ms

    ContentSquare costs a phone 319 ms of main-thread work and 172 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.

  • 2,609 HTML elements

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

  • Reduce unused CSS

    150 ms · 55 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    43 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 12 ms

    12 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 17.7 s

    17.7 s

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

  • Speed Index: 18.2 s

    18.2 s

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

  • Time to Interactive: 33.6 s

    33.6 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.24

    0.24

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

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

5 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 162 ms

    162 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 720 ms

    720 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

1 to fix70
  • Page weight: 6.0 MB in 510 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 510 requests on a phone: scripts 3.5 MB (143), other files 1.7 MB (304) and images 406 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (50 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.7 g of CO₂ per visit

    1.71 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 204.8 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

8 to fixGoogle 8990
  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 2 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail 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.

  • 52 links without text

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 8594
  • Structured data has 6 problems

    Structured data found ((untyped), Organization and WebSite) but with 6 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 194 internal links, 7 external

    The homepage links to 194 pages on mustelausa.com and 7 external pages.

7 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Mustela is the mom and baby skincare brand with clean & gentle products for the delicate skin of newborns, babies, kids…”.

  • One H1 headline

    Your main headline reads: “Mustela USA”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Mom and Baby Skincare Experts - Mustela USA”.

  • Canonical URL set

    The canonical URL is https://www.mustelausa.com/.

  • 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.mustelausa.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

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 (1,028 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.mustelausa.com/collections has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 89 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

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://px.adentifi.com/Pixels?a_id=5758;uq=1792925230;.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    118 of 130 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 674 words of copy

    The homepage carries about 674 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Start buying”, “Shop all Products” and “What is my order status?”.

  • 10 short forms

    10 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 5 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 31 cookies set on arrival

    31

    Opening the homepage sets 31 cookies, 1 of them by other companies (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.

  • 60 other companies contacted

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

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 mustelausa.com, 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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Consentmo Gdpr · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Helium Customer Fields · Yotpo Product Reviews · Easylocation · Gdpr Backpack · rise-ai.com · gorgias.chat · 9gtb.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
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on mustelausa.com, including 18 speed issues, 2 SEO issues and 2 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