Website review, no card needed
hansgrohe.fr website review
Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 84 checks
This review found 33 issues worth fixing on hansgrohe.fr, 13 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 893 ms |
| May 9, 2026 | 901 ms |
| May 16, 2026 | 924 ms |
| May 23, 2026 | 938 ms |
| May 30, 2026 | 942 ms |
| Jun 6, 2026 | 942 ms |
| Jun 13, 2026 | 946 ms |
| Jun 20, 2026 | 939 ms |
| Jun 27, 2026 | 934 ms |
| Jul 4, 2026 | 946 ms |
| Jul 11, 2026 | 943 ms |
| Jul 18, 2026 | 939 ms |
| Jul 25, 2026 | 927 ms |
| Aug 1, 2026 | 924 ms |
| Aug 8, 2026 | 912 ms |
| Aug 15, 2026 | 905 ms |
| Aug 22, 2026 | 921 ms |
| Aug 29, 2026 | 924 ms |
| Sep 5, 2026 | 944 ms |
| Sep 12, 2026 | 982 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 997 ms |
| Oct 10, 2026 | 981 ms |
| Oct 17, 2026 | 952 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 296 ms |
| May 9, 2026 | 301 ms |
| May 16, 2026 | 311 ms |
| May 23, 2026 | 314 ms |
| May 30, 2026 | 318 ms |
| Jun 6, 2026 | 326 ms |
| Jun 13, 2026 | 322 ms |
| Jun 20, 2026 | 323 ms |
| Jun 27, 2026 | 322 ms |
| Jul 4, 2026 | 322 ms |
| Jul 11, 2026 | 328 ms |
| Jul 18, 2026 | 329 ms |
| Jul 25, 2026 | 330 ms |
| Aug 1, 2026 | 334 ms |
| Aug 8, 2026 | 329 ms |
| Aug 15, 2026 | 332 ms |
| Aug 22, 2026 | 336 ms |
| Aug 29, 2026 | 331 ms |
| Sep 5, 2026 | 332 ms |
| Sep 12, 2026 | 329 ms |
| Sep 19, 2026 | 333 ms |
| Sep 26, 2026 | 332 ms |
| Oct 3, 2026 | 335 ms |
| Oct 10, 2026 | 340 ms |
| Oct 17, 2026 | 340 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.2 s · 493 KiBAbout 493 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Reduce unused CSS
1.2 s · 179 KiBAbout 179 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.4 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
350 ms · 139 KiB5 images could be 139 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 481 ms. During a long task the page ignores taps.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,157 HTML elements
The page has 2,157 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 173 ms
173 msGoogle Tag Manager costs a phone 173 ms of main-thread work and 321 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.
4 third-party services on the page
4 third-party services load with your homepage (piwik.pro, Google Tag Manager and hansgrohe.com and others), adding 708 KiB and 375 ms of main-thread time.
Legacy JavaScript
150 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
30 KiB10 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “En cliquant sur le bouton "Accepter", toutes les catégories…”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user INP: 354 ms
354 msReal visitors wait 354 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 296 ms to 340 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 333 ms
333 msReal visitors wait 333 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 125 requests
2.1 MBYour homepage downloads 2.1 MB in 125 requests on a phone: scripts 1.4 MB (89), images 238 KiB (23) and stylesheets 184 KiB (1). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
home-stage_tecturis-brushed-bronze-hands-under-water_16x9.jp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (124 KiB) 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.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Robinets & mitigeurs pour la salle de bains, la douche et la cuisine”.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
310 internal links, 14 external
The homepage links to 310 pages on hansgrohe.fr and 14 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Mitigeurs et douches de tête de qualité : chez hansgrohe, vous trouverez des produits premium pour la salle de bains et…”.
One H1 headline
Your main headline reads: “Votre marque premium pour la salle de bains & la cuisine.”.
Canonical URL set
The canonical URL is https://www.hansgrohe.fr/.
Structured data in place
Structured data found: WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.hansgrohe.fr/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.hansgrohe.fr/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,979 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.hansgrohe.fr/configurateur-salle-de-bains is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://www.hansgrohe.fr/salle-de-bain/produits/espace-lavabo has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.hansgrohe.fr/salle-de-bains/produits/douches took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 139 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,131 words of copy
The homepage carries about 1,131 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “contact”.
3 short forms
3 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
2 trackers load before any consent
2Before 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
No consent tool detected
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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hansgrohe.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on hansgrohe.fr, including 17 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.