whirlpool.fr website review

vtexassets.com costs a phone 1.2 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 4.3 MB and 2.5 s of main-thread time.

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

About 797 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

Optanon costs a phone 68 ms of main-thread work and 458 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.

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

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

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

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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 209 requests on a phone: scripts 2.9 MB (60), images 699 KiB (82) and other files 421 KiB (60). Under 2 MB keeps phones on slow connections fast.

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

42 buttons have no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 10 elements on the page fail this check, rated serious by axe-core.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

19 visible links have no text or label, so screen readers cannot say where they go.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 204 pages on whirlpool.fr and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.whirlpool.fr/produits/lavage/lave-linge/classe-a took over 3 s to send its HTML from our server.

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

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

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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,442 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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