Website review, no card needed

cesttoutbeauty.com logo

cesttoutbeauty.com website review

Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 74 checks

This review found 30 issues worth fixing on cesttoutbeauty.com, 7 of them high impact, across 74 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

Full-page screenshot of cesttoutbeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cesttoutbeauty.com at 0.4 s0.4 s
  2. cesttoutbeauty.com at 0.8 s0.8 s
  3. cesttoutbeauty.com at 1.1 s1.1 s
  4. cesttoutbeauty.com at 1.5 s1.5 s
  5. cesttoutbeauty.com at 1.9 s1.9 s
  6. cesttoutbeauty.com at 2.3 s2.3 s
  7. cesttoutbeauty.com at 2.6 s2.6 s
  8. cesttoutbeauty.com at 3.0 s3.0 s

Speed

8 to fix64
  • Reduce unused JavaScript

    1.6 s · 883 KiB

    About 883 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Use efficient cache lifetimes

    2.0 s · 385 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, amaicdn.com and Privy and others), adding 1.9 MB and 856 ms of main-thread time.

  • Mobile performance score: 64

    64/100

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

  • YouTube adds 455 ms

    455 ms

    YouTube costs a phone 455 ms of main-thread work and 1,014 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.

  • Render-blocking requests

    450 ms

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

  • amaicdn.com adds 249 ms

    249 ms

    amaicdn.com costs a phone 249 ms of main-thread work and 409 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.

  • Main-thread work: 2.6 s

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 58 KiB

    Polyfills for old browsers add 58 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

    130 KiB

    About 130 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix59
  • Largest Contentful Paint: 7.9 s

    7.9 s

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

  • Time to Interactive: 17.9 s

    17.9 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Total Blocking Time: 338 ms

    338 ms

    Scripts block taps and scrolling for 338 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.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 186 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 186 requests on a phone: scripts 1.8 MB (63), other files 682 KiB (90) and fonts 180 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.85 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 to fixGoogle 9095
  • 8 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 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 8583
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Scalp Serum for Hair Density”). One clear main headline is easier for people and search engines.

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 36 internal links, 9 external

    The homepage links to 36 pages on cesttoutbeauty.com and 9 external pages.

5 checks passed
  • Title: 37 characters

    Your title is a healthy 37 characters: “C'est Tout Beauty – C'est Tout Beauty”.

  • Canonical URL set

    The canonical URL is https://cesttoutbeauty.com/.

  • Structured data in place

    Structured data found: BreadcrumbList.

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://cesttoutbeauty.com/collections/all and https://cesttoutbeauty.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://cesttoutbeauty.com/collections/all has 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    5 pages of 12 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 9 small tap targets

    9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “YT.Player is not a constructor”.

  • 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

3 to fix75
  • Thin social proof

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

  • 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 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 471 words of copy

    The homepage carries about 471 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Subscribe”, “LEARN MORE” and “Contact us”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 cesttoutbeauty.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

privy.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on cesttoutbeauty.com, including 13 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