Website review, no card needed
umawell.fr website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 90 checks
This review found 40 issues worth fixing on umawell.fr, 12 of them high impact, across 90 checks. The most urgent: mobile performance score: 39. 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
68D- #108,269 of 123,369 reviewed websitesbeats 10%
- #64,799 of 69,519 online storesbeats 5%
- #59,662 of 63,279 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 242 ms |
| May 23, 2026 | 244 ms |
| May 30, 2026 | 245 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 231 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 212 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 200 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 203 ms |
| Oct 24, 2026 | 206 ms |
| Oct 31, 2026 | 209 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
Speed
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.1 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, Shopify and Klaviyo and others), adding 1.9 MB and 1.0 s of main-thread time.
Reduce unused JavaScript
150 ms · 629 KiBAbout 629 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
700 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Google Tag Manager adds 394 ms
394 msGoogle Tag Manager costs a phone 394 ms of main-thread work and 748 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.
Use efficient cache lifetimes
200 ms · 263 KiB23 files are served with short cache lifetimes, so returning visitors download them again (263 KiB).
Minify JavaScript
300 ms · 26 KiB26 KiB could be saved by minifying JavaScript.
Shopify adds 219 ms
219 msShopify costs a phone 219 ms of main-thread work and 563 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 252 ms. During a long task the page ignores taps.
2,142 HTML elements
The page has 2,142 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 144 ms
144 msKlaviyo costs a phone 144 ms of main-thread work and 331 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 · 19 KiBAbout 19 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.
Improve image delivery
50 ms · 39 KiB4 images could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
7 KiB7 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: 132 ms
132 msYour server sent the HTML in 132 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.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nos nouveaux packs associent des solutions ciblées pour rép…”.
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 719 ms
719 msScripts block taps and scrolling for 719 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 213 ms
213 msReal visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 447 ms
447 msReal visitors wait 447 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 242 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.1 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 298 requests
3.6 MBYour homepage downloads 3.6 MB in 298 requests on a phone: scripts 2.0 MB (136), other files 823 KiB (108) and HTML 376 KiB (2). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
slider_harmonie-mob_EN.webp 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).
1 image in older formats
1 image (87 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.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.9 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
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (273 characters)
Your meta description is 273 characters; Google truncates after about 160, so the end of your pitch is cut.
58 internal links, 1 external
The homepage links to 58 pages on umawell.fr and 1 external page.
7 checks passed
One H1 headline
Your main headline reads: “Discover our new packs”.
Title: 50 characters
Your title is a healthy 50 characters: “Laboratoires üma – Natural Solutions for Menopause”.
Canonical URL set
The canonical URL is https://umawell.fr/en.
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.
XML sitemap found
Your XML sitemap is reachable at https://umawell.fr/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: 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 (1,199 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://umawell.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without an H1
https://umawell.fr/en/collections/shopall, https://umawell.fr/en/collections/offres-speciales, https://umawell.fr/en/pages/ingredients, https://umawell.fr/en/pages/about, https://umawell.fr/en/blogs/news and https://umawell.fr/en/pages/symptoms and 1 other have 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 19 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 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.
Every page has a meta description
All 7 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 7 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343240343&tm=gtm002&Ver=2&mid=ef6a6451-424e-4205-b68f-658583a9d602&bo=1&sid=12c25670db4d11f1b557d3208ea698ce&vid=12c264d0db4d11f1b291f53ef4771ae4&vids=1&msclkid=N>m_.
4 small tap targets
4 of 18 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 “Cornercart Failed to fetch from abt.usecorner.io: AbortError: signal is aborted without reason”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
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.
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,520 words of copy
The homepage carries about 1,520 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Help & Contact”, “Contact us” and “Shop now”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 6 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.
34 cookies set on arrival
34Opening the homepage sets 34 cookies, 4 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.
48 other companies contacted
Loading the homepage contacts 48 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 umawell.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Triplewhale · Smart Seo · T Lab Ai Translate · Judge Me Reviews · Xo Insert Code · Foxify Page Builder · Microsoft Clarity · Foxkit Upsell Bundles · Analyzify Ga4 Ads Tracking · Tolstoy · Content Translation · Applovin Shop Integration · Guarantees Features Icons · Cornercart · pleasestay.co · cloudfront.net · amazonaws.com · web.app · archive-digger.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 Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on umawell.fr, including 21 speed issues, 1 SEO issue and 4 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.