insujet.fr website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Google CDN and others), adding 1.9 MB and 793 ms of main-thread time.

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

Some JavaScript is shipped twice across bundles. Google estimates it would make the page about 450 ms faster on a phone.

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

Google CDN costs a phone 113 ms of main-thread work and 352 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.

Shopify costs a phone 34 ms of main-thread work and 893 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.

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

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

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.

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.

Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “L’insuline, sans aiguille Simplifiez-vous la vie !”.

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

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

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

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

4 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 24.5 MB in 293 requests on a phone: media 20.8 MB (2), images 1.2 MB (26) and scripts 1.2 MB (57). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example illustration-without-insujet.png at 1,809 px wide, shown at 350 px. Resized copies would save about 48 KiB.

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Your title is 86 characters, so Google will cut it off around 60: “InsuJet – Premier Injecteur d’Insuline Sans Aiguille, Sûr et Innovant – InsuJet France”.

There are 4 <h1> headlines (“”, “” and “L’insuline, sans aiguille”). One clear main headline is easier for people and search engines.

The homepage links to 47 pages on insujet.fr and 2 external pages.

https://insujet.fr/collections/e-shop, https://insujet.fr/pages/about-us, https://insujet.fr/pages/mode-d-emploi, https://insujet.fr/pages/etudes-cliniques, https://insujet.fr/pages/professionnels-de-sante and https://insujet.fr/pages/accompagnement and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

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

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