123gelules.com website review

19 images could be 817 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.0 MB and 744 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.

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

Google Tag Manager costs a phone 419 ms of main-thread work and 532 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.

About 432 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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.

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.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Complexe 5 Magnésium”.

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

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

Real visitors wait 827 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 240 ms to 277 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

123G-Banniere-Home-09-5Magnesium-GPH.JPG weighs 634 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.2 MB in 105 requests on a phone: images 1.4 MB (49), scripts 1.2 MB (24) and fonts 359 KiB (8). Under 2 MB keeps phones on slow connections fast.

8 images (901 KiB) 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.

18 images further down the page (471 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 123G-Banniere-Home-09-5Magnesium-GPH.JPG at 1,240 px wide, shown at 390 px. Resized copies would save about 70 KiB.

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

21 buttons have no accessible name, so screen readers announce just “button”.

Some list items are not inside a list.

20 tap targets are too small or too close together to hit reliably with a finger.

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

4 visible links have no text or label, so screen readers cannot say where they go.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 204 pages on 123gelules.com and 3 external pages.

https://www.123gelules.com/content/8-livraison and https://www.123gelules.com/commande are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.123gelules.com/content/8-livraison, https://www.123gelules.com/commande, https://www.123gelules.com/234-vitamines-et-min%C3%A9raux, https://www.123gelules.com/6-circulation and https://www.123gelules.com/83-digestion-transit have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.123gelules.com/commande has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5090412&tm=gtm002&Ver=2&mid=c21ad306-fc62-4bad-97d3-66dab6abd814&bo=1&sid=c96adf80dd7211f1b1712759af9b0b4c&vid=c96b1660dd7211f19b9d1789ce6a867d&vids=1&msclkid=N&pi=918.

17 of 83 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 60 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 708 words of visible text.

Before 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 18 cookies, 2 of them by other companies (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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.