bulbesdefleurs.com website review

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

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

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

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

About 553 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.

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

16 images could be 345 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

About 47 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.

36 KiB could be saved by minifying JavaScript.

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

7 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Scripts block taps and scrolling for 311 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 144 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 344 requests on a phone: images 3.6 MB (112), scripts 1.3 MB (82) and other files 1.1 MB (115). Under 2 MB keeps phones on slow connections fast.

21 images are downloaded at several times the size a phone draws them, for example ALV-UjXE67m4KOEqdCxKDIhbIv_rlOlTIXUkikrem4oPdjqxfUOFnJR_ at 512 px wide, shown at 39 px. Resized copies would save about 1.4 MB.

26 images (1.7 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.

6 images further down the page (290 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.76 g of CO₂e: 211.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

Your title is 81 characters, so Google will cut it off around 60: “Flower Bulb Wholesaler Supplier - Producer Price – Floriverse - Econome à Légumes”.

Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

Your <h1> is empty.

The homepage links to 91 pages on bulbesdefleurs.com and 2 external pages.

https://bulbesdefleurs.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://bulbesdefleurs.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://bulbesdefleurs.com/en/collections/acheter-bulbes-de-fleurs-pro-non-traites-en-ligne-fournisseur-grossiste-specialiste and https://bulbesdefleurs.com/en/collections/acheter-bulbes-de-fleurs-non-traites-en-ligne-creez-le-jardin-de-vos-reves all use the title “Buy Flower Bulbs Online - Producer Prices – Floriverse - Econome à Lé…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://bulbesdefleurs.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://bulbesdefleurs.com/en/pages/contact and https://bulbesdefleurs.com/en/pages/modalites-de-livraison use the same meta description. A description written for each page earns more clicks.

https://bulbesdefleurs.com/customer_authentication/redirect, https://bulbesdefleurs.com/en/collections/acheter-bulbes-de-fleurs-pro-non-traites-en-ligne-fournisseur-grossiste-specialiste, https://bulbesdefleurs.com/en/collections/acheter-bulbes-de-fleurs-pro-bio-en-ligne-fournisseur-grossiste-specialiste, https://bulbesdefleurs.com/en/collections/acheter-bulbes-de-fleurs-non-traites-en-ligne-creez-le-jardin-de-vos-reves and https://bulbesdefleurs.com/en/collections/mix-bulbes-de-fleurs-en-ligne-pour-particuliers have no <h1> headline, so visitors and search engines get no clear main topic.

https://bulbesdefleurs.com/en/collections/mix-bulbes-de-fleurs-en-ligne-fournisseur-grossiste-specialiste took over 3 s to send its HTML from our server.

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

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

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

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

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

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

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

The homepage carries about 4,407 words of visible text.

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