Website review, no card needed

puissante.co logo

puissante.co website review

Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 63 checks

This review found 24 issues worth fixing on puissante.co, 5 of them high impact, across 63 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.2 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.9 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
172 ms143 msMay 16Oct 31163 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026148 ms
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026149 ms
Jun 13, 2026155 ms
Jun 20, 2026158 ms
Jun 27, 2026158 ms
Jul 4, 2026159 ms
Jul 11, 2026160 ms
Jul 18, 2026158 ms
Jul 25, 2026156 ms
Aug 1, 2026156 ms
Aug 8, 2026155 ms
Aug 15, 2026155 ms
Aug 22, 2026156 ms
Aug 29, 2026157 ms
Sep 5, 2026159 ms
Sep 12, 2026161 ms
Sep 19, 2026164 ms
Sep 26, 2026166 ms
Oct 3, 2026168 ms
Oct 10, 2026169 ms
Oct 17, 2026169 ms
Oct 24, 2026168 ms
Oct 31, 2026163 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Largest content (LCP) got 25% slower for real visitors

    +25%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

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

    +13%

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

3 checks passed
  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 708 ms

    708 ms

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

Images and page weight

3 to fix53
  • Page weight: 7.7 MB

    7.7 MB

    Your homepage downloads 7.7 MB on a phone, 1.4 MB of it images (19%). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HP_Site-04_beedee93-3ea8-405d-a149-b06c4f842f57.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).

  • 6 images in older formats

    6 images (576 KiB) are 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 2.2 g of CO₂ per visit

    2.19 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fix93
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 14 images without alt text

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

  • All page content should be contained by landmarks (103 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 12 links without text

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

  • 7 form fields without a label

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

  • ARIA role should be appropriate for the element (4 elements)

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

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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

100
  • 110 internal links, 6 external

    The homepage links to 110 pages on puissante.co and 6 external pages.

8 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Découvrez Puissante, votre nouvelle marque de bien-être féminin. Parce qu'être bien avec soi passe aussi par une sexual…”.

  • One H1 headline

    Your main headline reads: “Puissante, le bien-être féminin.”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Puissante - Le bien-être au féminin”.

  • Canonical URL set

    The canonical URL is https://puissante.co/.

  • Structured data in place

    Structured data found: ItemList, Organization, WebPage 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://puissante.co/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://puissante.co/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.

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.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://puissante.co/pages/le-club-puissante has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://puissante.co/pages/le-club-puissante, https://puissante.co/collections/complements-alimentaires and https://puissante.co/collections/soins-et-hygiene-intime have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://puissante.co/collections/vibros took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    5 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 5 pages that loaded have a <title>.

Best practices

2 to fix87
  • 18 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Identifier 'PredictiveSearch' has already been declared”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Quick shop”.

  • 10 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

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

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 puissante.co, 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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Qtrack · Microsoft Clarity · Klaviyo Email Marketing Sms · Autocart · Kaching Bundles · Join Stories · Revoq Eu Withdrawal Button · Judgeme · Reviews Co Uk Product And Merchant Review Collection · Ralph · nfcube.com · wisepops.com · redirectify.app · cloudfront.net · rechargecdn.com · loyoly.io

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on puissante.co, including 4 speed issues and 5 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