Website review, no card needed
my-origines.com website review
Visit site (opens in a new tab)Reviewed 24 October 202647 issues · 97 checks
This review found 47 issues worth fixing on my-origines.com, 25 of them high impact, across 97 checks. The most urgent: improve image delivery. 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
66D- #114,778 of 125,770 reviewed websitesbeats 7%
- #67,156 of 70,261 online storesbeats 4%
- #217 of 292 Salesforce Commerce Cloud storesbeats 22%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 174 ms |
| May 9, 2026 | 173 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 185 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 192 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 204 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 202 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 188 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
0.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Improve image delivery
4.3 s · 3.6 MB21 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.
Reduce unused JavaScript
3.0 s · 869 KiBAbout 869 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 1.2 MB33 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Render-blocking requests
2.9 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 11
11/100Your mobile performance score is 11 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,539 HTML elements
The page has 3,539 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 (Stripe, Facebook and Didomi and others), adding 1.3 MB and 859 ms of main-thread time.
Minify JavaScript
600 ms · 180 KiB180 KiB could be saved by minifying JavaScript.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 310 ms. During a long task the page ignores taps.
myorigines.tech adds 39 ms
39 msmyorigines.tech costs a phone 39 ms of main-thread work and 515 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 · 101 KiBAbout 101 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.
Minify CSS
38 KiB38 KiB could be saved by minifying CSS.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 48 but mobile only 11. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 11 ms
11 msYour server sent the HTML in 11 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: 31.5 s
31.5 sYour largest element takes 31.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Grande Braderie”.
Time to Interactive: 32.4 s
32.4 sThe page becomes fully interactive after 32.4 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.55
0.55The layout shifts by 0.55 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 174 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Real-user TTFB: 768 ms
768 msReal visitors wait 768 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 22.3 MB in 161 requests
22.3 MBYour homepage downloads 22.3 MB in 161 requests on a phone: media 13.5 MB (1), images 6.4 MB (74) and scripts 1.9 MB (37). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
3.0 MB9 images are downloaded at several times the size a phone draws them, for example S43_BIOTHERM_WEEKLY_OFFER_02_400x400_MOB.jpg at 1,667 px wide, shown at 193 px. Resized copies would save about 3.0 MB.
1 image over 500 KB
S43_BIOTHERM_WEEKLY_OFFER_02_400x400_MOB.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.
16 images in older formats
16 images (2.6 MB) 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.
An image on the first screen is lazy-loaded
S43_BIOTHERM_MENU_CONTENT_BON_PLAN_MOBILE_530x340.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).
About 6.3 g of CO₂ per visit
6.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.32 g of CO₂e: 758.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 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: 46 passed and 9 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 (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “MyOrigines : L'eshop beauté - Parfum, Maquillage, Cosmétiques, Parapharmacie en ligne”.
Meta description is long (241 characters)
Your meta description is 241 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
462 internal links, 7 external
The homepage links to 462 pages on my-origines.com and 7 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Parfum, cosmétiques, maquillage, soins cheveux et parapharmacie sur MyOrigines”.
Canonical URL set
The canonical URL is https://www.my-origines.com/fr.
Structured data in place
Structured data found: Organization and WebSite.
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.my-origines.com/fr/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.my-origines.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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,660 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.my-origines.com/fr and https://www.my-origines.com/fr/marques/the-niche-list all use the title “MyOrigines : L'eshop beauté - Parfum, Maquillage, Cosmétiques, Paraph…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.my-origines.com/fr/octobre-rose.html and https://www.my-origines.com/fr/marques/the-niche-list use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.my-origines.com/fr/marques/the-niche-list, whose canonical is https://www.my-origines.com/fr/the-niche-list.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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://bat.bing.com/action/0?ti=4024601&tm=gtm002&Ver=2&mid=af991476-cfed-48dc-869b-29b58183c74f&bo=1&sid=ab468950cf9b11f1991ee14c1b915981&vid=ab467dd0cf9b11f1a15a33346e754192&vids=1&msclkid=N&pi=918.
30 small tap targets
30 of 89 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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 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 999 words of copy
The homepage carries about 999 words of visible text.
6 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SHOP” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
36 cookies set on arrival
36Opening the homepage sets 36 cookies (measured from a US location before any click).
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) loads with the page.
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 my-origines.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on my-origines.com, including 20 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.