Website review, no card needed
mercihandy.fr website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 89 checks
This review found 34 issues worth fixing on mercihandy.fr, 13 of them high impact, across 89 checks. The most urgent: mobile performance score: 48. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78C- #63,200 of 126,458 reviewed websitesbeats 45%
- #40,908 of 70,479 online storesbeats 36%
- #39,026 of 63,977 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 138 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 159 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 209 ms |
| Oct 31, 2026 | 204 ms |
| Nov 7, 2026 | 202 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
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,197 HTML elements
The page has 3,197 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
2.3 MBAbout 2.3 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, achille.ai and Shopify and others), adding 2.4 MB and 1.4 s of main-thread time.
Render-blocking requests
900 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Improve image delivery
650 ms · 246 KiB10 images could be 246 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Use efficient cache lifetimes
596 KiB18 files are served with short cache lifetimes, so returning visitors download them again (596 KiB).
Google Tag Manager adds 369 ms
369 msGoogle Tag Manager costs a phone 369 ms of main-thread work and 366 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.
achille.ai adds 274 ms
274 msachille.ai costs a phone 274 ms of main-thread work and 755 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.
Shopify adds 186 ms
186 msShopify costs a phone 186 ms of main-thread work and 494 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.
Reduce unused CSS
150 ms · 146 KiBAbout 146 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 242 ms. During a long task the page ignores taps.
Minify JavaScript
101 KiB101 KiB could be saved by minifying JavaScript.
Legacy JavaScript
64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need.
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
Duplicated JavaScript
9 KiB9 KiB JavaScript is shipped twice across bundles.
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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 801 ms
801 msScripts block taps and scrolling for 801 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 138 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 199 ms
199 msReal visitors wait 199 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 346 requests
5.9 MBYour homepage downloads 5.9 MB in 346 requests on a phone: scripts 3.3 MB (126), images 1.1 MB (46) and other files 935 KiB (121). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.67 g of CO₂e: 199.9 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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “Merci Handy | Nous existons pour rendre l'ordinaire extraordinaire 🌈 – Merci Handy FR”.
Meta description is long (213 characters)
Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
156 internal links, 7 external
The homepage links to 156 pages on mercihandy.fr and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Le calendrier de l'avent pour un Noël au sommet”.
Canonical URL set
The canonical URL is https://www.mercihandy.com/.
Structured data in place
Structured data found: Organization 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://www.mercihandy.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,033 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.mercihandy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages share a meta description
https://www.mercihandy.com/collections/la-folie-douce, https://www.mercihandy.com/collections/la-folie-douce/calendrier, https://www.mercihandy.com/collections/la-folie-douce/soin-des-mains and https://www.mercihandy.com/collections/la-folie-douce/soin-du-corps use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://www.mercihandy.com/collections/les-mains/sprays-mains-nettoyants took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/JEdjH7/images/44d3b458-3da8-4701-bc84-9544c23ef62e.png.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “jQuery library not found. Unable to initiate Custom Fields Accordion widget.”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
44 of 50 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 802 words of copy
The homepage carries about 802 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
20 short forms
20 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 90 testimonial or review blocks, 16 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and TikTok Pixel.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (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.
41 other companies contacted
Loading the homepage contacts 41 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 mercihandy.fr, 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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Addingwell · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Forms · Freegifts · Discount Planner By Productessentials · usedrop.io · bogos.io · scalingo.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on mercihandy.fr, including 19 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.