concours-capsme.fr website review

19 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.

About 999 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 9.5 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,544 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, replocdn.com and Clarity and others), adding 7.0 MB and 1.2 s of main-thread time.

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Shopify costs a phone 554 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.

23 files are served with short cache lifetimes, so returning visitors download them again (392 KiB).

20 long tasks block the main thread while loading, the longest for 702 ms. During a long task the page ignores taps.

replocdn.com costs a phone 219 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.

About 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need.

8 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 32.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 É…”.

The page becomes fully interactive after 40.9 s. Good is under 3.8 s.

Visually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 791 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 3.0 s on a phone. Good is under 1.8 s.

9 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 10.4 MB in 460 requests on a phone: images 5.8 MB (70), scripts 2.6 MB (158) and other files 1.4 MB (176). Under 2 MB keeps phones on slow connections fast.

5 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.

33 images (10.5 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 further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 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 435 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.96 g of CO₂e: 355.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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 on the page fail this check, rated serious by axe-core.

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 on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

24 images have no alt text, which hurts accessibility and image search.

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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 on the page fail this check, rated minor by axe-core.

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. (1 element).

Your title is 74 characters, so Google will cut it off around 60: “Capsules café réutilisables – Écologiques, économiques | CAPS'ME – CAPS ME”.

Your canonical URL points to capsme.fr, not concours-capsme.fr, so Google may credit that host instead.

Your meta description is 276 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 62 pages on concours-capsme.fr and 18 external pages.

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.

The HTML your server sends has 743 of the 1,426 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/products/cafe-moulu-pour-capsules-reutilisables is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/products/abonnement-cafes-opercules, /pages/points-de-vente, /pages/histoire, /collections/offres-a-ne-pas-rater and /collections/tous-les-produits-capsme have no meta description, so Google writes the search snippet from whatever text it finds.

/products/coffret-caps-me, /products/3-capsules-reutilisables-inox, /products/le-boise, /products/opercules-en-papier-compostable, /pages/capsme-nos-produits and /products/abonnement-cafes-opercules and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/products/coffret-caps-me, /products/le-boise, /products/opercules-en-papier-compostable, /pages/histoire, /collections/offres-a-ne-pas-rater and /collections/tous-les-produits-capsme took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “your_user_id is not defined”.

1 link to other sites is dead, for example https://youtube.com/@capsme9729 (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://concours-capsme.fr/pages/capsme-dolcegusto.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,426 words of visible text.

DMARC is set to p=none, so mail pretending to be concours-capsme.fr is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 23 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.