interflora.fr website review

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and korvus.fr and others), adding 772 KiB and 705 ms of main-thread time.

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

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

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

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

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

About 44 KiB of CSS is downloaded but never applied on this page.

33 KiB could be saved by minifying JavaScript.

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.6 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.7 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 3.0 MB in 141 requests on a phone: scripts 1.9 MB (60), images 871 KiB (39) and HTML 142 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 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.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate 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.

The homepage links to 166 pages on interflora.fr and 16 external pages.

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.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “[Axeptio marketplace] piano:init failed: ReferenceError: pa is not defined”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

Before a visitor clicks anything, the page loads Google Ads 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 8 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.