botanic.com website review

50 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Didomi and Google Analytics and others), adding 5.4 MB and 607 ms of main-thread time.

Your mobile performance score is 61 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

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

Google Tag Manager costs a phone 488 ms of main-thread work and 670 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 481 KiB of JavaScript is downloaded but never used on this page.

proximis.com costs a phone 0 ms of main-thread work and 4.5 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.

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

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (71 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.

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Collection Noël Sapins, décorations et gourmandises Le vill…”.

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 157 requests on a phone: images 4.7 MB (95), scripts 1.8 MB (34) and fonts 263 KiB (5). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example 64b907bc98b0a_chien_chat_ext_rieur.png at 1,400 px wide, shown at 83 px. Resized copies would save about 2.1 MB.

21 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (71 KiB) is 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.

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

Links must have discernible text: 8 elements on the page fail this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Your title is 74 characters, so Google will cut it off around 60: “botanic® : jardinerie écologique, animalerie, décoration, alimentation bio”.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 385 pages on botanic.com and 14 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/creer-votre-compte.html and /mon-panier.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/nous-connaitre/aide-contact.html, /s-inspirer.html, /services.html, /nous-connaitre/botanic-s-engage/botanic-s-engage.html, /consulter/apprendre-ensemble/apprendre-ensemble.html and /le-club-botanic-/le-programme-de-fidelite.html and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /nous-connaitre/botanic-s-engage/botanic-s-engage.html, whose canonical is /nous-connaitre/botanic-s-engage.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/nous-connaitre/botanic-s-engage/botanic-s-engage.html, /consulter/apprendre-ensemble/apprendre-ensemble.html, /le-club-botanic-/le-programme-de-fidelite.html and /nos-magasins.html took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://foire-aux-questions.botanic.com/.

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.

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

botanic.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 4 trust badges. 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.

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

DMARC is set to p=none, so mail pretending to be botanic.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

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

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