Website review, no card needed
ioma-paris.com website review
Visit site (opens in a new tab)Reviewed 11 November 202627 issues · 80 checks
This review found 27 issues worth fixing on ioma-paris.com, 8 of them high impact, across 80 checks. The most urgent: main-thread work: 5.4 s. 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
87B- #8,497 of 123,904 reviewed websitesbeats 90%
- #4,868 of 69,715 online storesbeats 90%
- #4,717 of 63,419 Shopify storesbeats 89%
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.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 145 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 134 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 159 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 149 ms |
| Oct 3, 2026 | 150 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 157 ms |
| Oct 31, 2026 | 160 ms |
| Nov 7, 2026 | 155 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
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.3 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 (Clarity, Shopify and Google Tag Manager and others), adding 1.7 MB and 860 ms of main-thread time.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
350 ms · 462 KiB39 files are served with short cache lifetimes, so returning visitors download them again (462 KiB).
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
240 ms · 427 KiBAbout 427 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 240 ms faster on a phone.
Shopify adds 167 ms
167 msShopify costs a phone 167 ms of main-thread work and 796 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.
2,405 HTML elements
The page has 2,405 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 97 ms
97 msKlaviyo costs a phone 97 ms of main-thread work and 317 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
210 ms · 65 KiBAbout 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 210 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Improve image delivery
184 KiB10 images could be 184 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.9 s
20.9 sThe page becomes fully interactive after 20.9 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 241 ms
241 msScripts block taps and scrolling for 241 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 145 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 160 ms
160 msReal visitors wait 160 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 630 ms
630 msReal visitors wait 630 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 416 requests
4.0 MBYour homepage downloads 4.0 MB in 416 requests on a phone: scripts 1.8 MB (207), other files 1.0 MB (138) and images 950 KiB (50). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 137.4 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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 64 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 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 (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “IOMA Paris - n°1 des soins personnalisés | Soins visage et cheveux”.
Meta description is long (226 characters)
Your meta description is 226 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
174 internal links, 5 external
The homepage links to 174 pages on ioma-paris.com and 5 external pages.
6 checks passed
One H1 headline
Your main headline reads: “IOMA Paris”.
Canonical URL set
The canonical URL is https://ioma-paris.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://ioma-paris.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,249 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ioma-paris.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 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
43 small tap targets
43 of 76 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 “Access to XMLHttpRequest at 'https://cdn.doofinder.com/livelayer/1.8.211/css/2/common.css?v=1.8.211' from origin 'https…”.
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.
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 986 words of copy
The homepage carries about 986 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 144 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
44 other companies contacted
Loading the homepage contacts 44 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 ioma-paris.com, 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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Scalapay On Site Messaging · Addingwell · Judge Me Reviews · Doofinder Search Discovery · Klaviyo Email Marketing Sms · Sc Easy Redirects · Dr Stacked Discounts · Inbox · Abconsent Cmp Sirdata · Scalapay Widget Installer Prod · Social Widget · Awesomemotive Optinmonster Shopify App · Sales Motivator Free Gifts · chimpstatic.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 Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Founded
- 2008
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on ioma-paris.com, including 13 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.