Website review, no card needed

beautysuccess.fr logo

beautysuccess.fr website review

Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 73 checks

This review found 39 issues worth fixing on beautysuccess.fr, 15 of them high impact, across 73 checks. The most urgent: render-blocking 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.5 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
231 ms181 msMay 9Oct 24187 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026213 ms
May 16, 2026212 ms
May 23, 2026212 ms
May 30, 2026214 ms
Jun 6, 2026215 ms
Jun 13, 2026217 ms
Jun 20, 2026218 ms
Jun 27, 2026218 ms
Jul 4, 2026221 ms
Jul 11, 2026223 ms
Jul 18, 2026225 ms
Jul 25, 2026223 ms
Aug 1, 2026222 ms
Aug 8, 2026213 ms
Aug 15, 2026205 ms
Aug 22, 2026197 ms
Aug 29, 2026189 ms
Sep 5, 2026187 ms
Sep 12, 2026188 ms
Sep 19, 2026187 ms
Sep 26, 2026188 ms
Oct 3, 2026188 ms
Oct 10, 2026187 ms
Oct 17, 2026187 ms
Oct 24, 2026187 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 beautysuccess.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beautysuccess.fr at 1.1 s1.1 s
  2. beautysuccess.fr at 2.2 s2.2 s
  3. beautysuccess.fr at 3.4 s3.4 s
  4. beautysuccess.fr at 4.5 s4.5 s
  5. beautysuccess.fr at 5.6 s5.6 s
  6. beautysuccess.fr at 6.7 s6.7 s
  7. beautysuccess.fr at 7.9 s7.9 s
  8. beautysuccess.fr at 9.0 s9.0 s

Speed

11 to fix44
  • Render-blocking requests

    1.6 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 679 KiB 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: 44

    44/100

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

  • Main-thread work: 8.7 s

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

  • 7,534 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, YouTube and Clarity and others), adding 1.8 MB and 2.1 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 913 KiB

    About 913 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • YouTube adds 747 ms

    747 ms

    YouTube costs a phone 747 ms of main-thread work and 969 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.

  • Improve image delivery

    250 ms · 463 KiB

    10 images could be 463 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Minify JavaScript

    450 ms · 72 KiB

    72 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    111 KiB

    About 111 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).

  • Use efficient cache lifetimes

    21 KiB

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

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

    361 ms

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

Core Web Vitals

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

  • Time to Interactive: 20.3 s

    20.3 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Beauty Success -25% sur les coffrets beauté”.

  • Real-user INP: 319 ms

    319 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 2 images without width and height

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.07

    0.07

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.063

    0.063

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

Images and page weight

1 to fix50
  • Page weight: 3.5 MB in 106 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 106 requests on a phone: scripts 1.8 MB (28), images 1.1 MB (43) and HTML 265 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

Accessibility

5 to fix89
  • 4 images without alt text

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 22 links without text

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

  • 11 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

SEO

4 to fixGoogle 9280
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (211 characters)

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

  • 5 links crawlers can't follow

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

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 1,095 internal links, 10 external

    The homepage links to 1,095 pages on beautysuccess.fr and 10 external pages.

4 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Beauty Success : Parfum – Soin - Maquillage - Institut”.

  • Canonical URL set

    The canonical URL is https://www.beautysuccess.fr/.

  • 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.beautysuccess.fr/sitemap/sitemap.xml.

AI search readiness

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

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.beautysuccess.fr/rendez-vous-en-institut has no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.beautysuccess.fr/nos-points-de-vente, https://www.beautysuccess.fr/rendez-vous-en-institut, https://www.beautysuccess.fr/aide, https://www.beautysuccess.fr/shop, https://www.beautysuccess.fr/shop/parfum/parfum-femme and https://www.beautysuccess.fr/shop/parfum/parfum-femme/extrait-de-parfum and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.beautysuccess.fr/rendez-vous-en-institut, https://www.beautysuccess.fr/aide, https://www.beautysuccess.fr/shop, https://www.beautysuccess.fr/shop/parfum/parfum-femme, https://www.beautysuccess.fr/shop/parfum/parfum-femme/extrait-de-parfum and https://www.beautysuccess.fr/shop/parfum/parfum-femme/eau-de-senteur-sans-alcool took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    8 pages of 15 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7388
  • 5 third-party cookies

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

  • 1 console error

    1 error was logged to the browser console during Google's test (“TypeError: Cannot read properties of null (reading 'closest') at https://www.beautysuccess.fr/:1651…”).

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 3,503 words of copy

    The homepage carries about 3,503 words of visible text.

2 checks passed
  • 38 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 beautysuccess.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Inherent

Company

Founded
1978

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on beautysuccess.fr, including 21 speed issues, 4 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