Website review, no card needed
capsme.fr website review
Visit site (opens in a new tab)Reviewed 7 November 202649 issues · 91 checks
This review found 49 issues worth fixing on capsme.fr, 19 of them high impact, across 91 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
70C- #98,771 of 118,247 reviewed websitesbeats 14%
- #60,405 of 67,198 online storesbeats 8%
- #55,998 of 61,274 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 438 ms |
| May 23, 2026 | 430 ms |
| May 30, 2026 | 433 ms |
| Jun 6, 2026 | 457 ms |
| Jun 13, 2026 | 453 ms |
| Jun 20, 2026 | 448 ms |
| Jun 27, 2026 | 440 ms |
| Jul 4, 2026 | 420 ms |
| Jul 11, 2026 | 428 ms |
| Jul 18, 2026 | 437 ms |
| Jul 25, 2026 | 436 ms |
| Aug 1, 2026 | 415 ms |
| Aug 8, 2026 | 413 ms |
| Aug 15, 2026 | 391 ms |
| Aug 22, 2026 | 360 ms |
| Aug 29, 2026 | 345 ms |
| Sep 5, 2026 | 322 ms |
| Sep 12, 2026 | 314 ms |
| Sep 19, 2026 | 323 ms |
| Sep 26, 2026 | 324 ms |
| Oct 3, 2026 | 326 ms |
| Oct 10, 2026 | 339 ms |
| Oct 17, 2026 | 329 ms |
| Oct 24, 2026 | 328 ms |
| Oct 31, 2026 | 331 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
Improve image delivery
16.4 s · 3.7 MB19 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.4 s faster on a phone.
Main-thread work: 10.2 s
A phone's processor spends 10.2 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,540 HTML elements
The page has 3,540 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 (Shopify, replocdn.com and Clarity and others), adding 7.0 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
910 ms · 977 KiBAbout 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.
Render-blocking requests
850 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Shopify adds 622 ms
622 msShopify costs a phone 622 ms of main-thread work and 2.2 MB 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
400 ms · 390 KiB23 files are served with short cache lifetimes, so returning visitors download them again (390 KiB).
replocdn.com adds 287 ms
287 msreplocdn.com costs a phone 287 ms of main-thread work and 4.3 MB 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 649 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 137 KiBAbout 137 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
8 KiB8 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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.6 s
31.6 sYour largest element takes 31.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “L'innovation primée qui réinvente la capsule réutilisable É…”.
Time to Interactive: 41.2 s
41.2 sThe page becomes fully interactive after 41.2 s. Good is under 3.8 s.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 665 ms
665 msScripts block taps and scrolling for 665 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 330 ms
330 msReal visitors wait 330 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 413 ms
413 msReal visitors wait 413 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 438 ms to 331 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 10.7 MB in 493 requests
10.7 MBYour homepage downloads 10.7 MB in 493 requests on a phone: images 5.8 MB (70), scripts 2.6 MB (158) and other files 1.6 MB (209). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.
33 images in older formats
33 images (10.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.
10 images below the first screen load straight away
10 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images far larger than shown
436 KiB6 images are downloaded at several times the size a phone draws them, for example EXCTRACTION_OPTIMALE_1.webp at 2,160 px wide, shown at 351 px. Resized copies would save about 436 KiB.
About 3.0 g of CO₂ per visit
3.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.02 g of CO₂e: 362.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
99 text elements with low contrast
99 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (6 elements)
ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (3 elements)
ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails 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
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 65 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Capsules café réutilisables – Écologiques, économiques | CAPS'ME – CAPS ME”.
Meta description is long (276 characters)
Your meta description is 276 characters; Google truncates after about 160, so the end of your pitch is cut.
70 internal links, 10 external
The homepage links to 70 pages on capsme.fr and 10 external pages.
6 checks passed
One H1 headline
Your main headline reads: “L'innovation primée qui réinvente la capsule réutilisable”.
Canonical URL set
The canonical URL is https://www.capsme.fr/.
Structured data in place
Structured data found: BreadcrumbList.
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.capsme.fr/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
47%The HTML your server sends has 743 of the 1,584 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
2 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.
llms.txt published
The site publishes https://www.capsme.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.capsme.fr/products/recharges-caps-me is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.capsme.fr/products/abonnement-cafes-opercules, https://www.capsme.fr/pages/points-de-vente, https://www.capsme.fr/pages/histoire and https://www.capsme.fr/products/recharges-caps-me have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.capsme.fr/products/le-boise, whose canonical is https://www.capsme.fr/products/le-boise-200g. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://www.capsme.fr/products/coffret-caps-me, https://www.capsme.fr/products/3-capsules-reutilisables-inox, https://www.capsme.fr/products/le-boise, https://www.capsme.fr/products/opercules-en-papier-compostable, https://www.capsme.fr/pages/capsme-nos-produits and https://www.capsme.fr/products/abonnement-cafes-opercules and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.capsme.fr/pages/articles-de-blog took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “your_user_id is not defined”.
2 checks passed
Tap targets are thumb-sized
71 of 86 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,584 words of copy
The homepage carries about 1,584 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
2 calls to action
The homepage has 2 calls to action, for example “F.A.Q - CONTACT” and “Contact”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
52 other companies contacted
Loading the homepage contacts 52 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 capsme.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
Klaviyo Email Marketing Sms · Judge Me Reviews · Addingwell · Loyoly · Transcy · Dialog E Commerce Ai Agent · trustpilot.com · rechargecdn.com · cloudfront.net · bogos.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | 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 49 issues on capsme.fr, including 21 speed issues, 2 SEO issues and 1 conversion gap. 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.