iamelsy.fr website review

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

About 899 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (Shopify, widebundle.com and b-cdn.net and others), adding 1.8 MB and 864 ms of main-thread time.

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

Shopify costs a phone 766 ms of main-thread work and 1.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 31 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.

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

2 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

81 KiB could be saved by minifying JavaScript.

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

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 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 152 ms to 168 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.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 359 requests on a phone: scripts 1.5 MB (96), images 1.4 MB (38) and other files 1.1 MB (180). Under 2 MB keeps phones on slow connections fast.

ELSY_HOME_PAGE.png 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).

3 images (500 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.

1 image is downloaded at several times the size a phone draws it, for example Logo_ELSY_seul.png at 6,169 px wide, shown at 61 px. Resized copies would save about 127 KiB.

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

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

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 2 <h1> headlines (“” and “.heading-template--30620307423567__otsb_promotion…”). One clear main headline is easier for people and search engines.

The homepage links to 78 pages on iamelsy.fr and 4 external pages.

https://iamelsy.fr/pages/pack-a-compose, https://iamelsy.fr/collections/nos-boxs, https://iamelsy.fr/collections/billes, https://iamelsy.fr/collections/les-minis-a-emporter and https://iamelsy.fr/collections/pack-familial-xl have no meta description, so Google writes the search snippet from whatever text it finds.

https://iamelsy.fr/pages/pack-a-compose and https://iamelsy.fr/collections/les-sirops have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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,036 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel, Pinterest Tag and TikTok Pixel (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 13 cookies, 1 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.