Website review, no card needed
hautesglaces.com website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 81 checks
This review found 38 issues worth fixing on hautesglaces.com, 18 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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
67D- #111,982 of 124,980 reviewed websitesbeats 9%
- #66,249 of 70,081 online storesbeats 4%
- #60,778 of 63,691 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 214 ms |
| May 23, 2026 | 225 ms |
| May 30, 2026 | 236 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 223 ms |
| Jul 4, 2026 | 241 ms |
| Jul 11, 2026 | 244 ms |
| Jul 18, 2026 | 244 ms |
| Jul 25, 2026 | 256 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 245 ms |
| Aug 22, 2026 | 218 ms |
| Aug 29, 2026 | 220 ms |
| Sep 5, 2026 | 223 ms |
| Sep 12, 2026 | 224 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 168 ms |
| Oct 31, 2026 | 186 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.9 s
1.8 s
2.7 s
3.6 s
4.6 s
5.5 s
6.4 s
7.3 s
Speed
Avoid multiple page redirects
9.8 sThe page goes through 1 redirect before it starts loading, costing about 9.8 s. Link and advertise the final URL directly.
Reduce unused JavaScript
6.6 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
hcaptcha.com adds 5.1 s
5.1 shcaptcha.com costs a phone 5.1 s of main-thread work and 4.4 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.
Main-thread work: 16.2 s
A phone's processor spends 16.2 s on main-thread work while loading, 9.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 6
6/100Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, customerfields.com and Google Tag Manager and others), adding 5.6 MB and 6.8 s of main-thread time.
Use efficient cache lifetimes
750 ms · 489 KiB15 files are served with short cache lifetimes, so returning visitors download them again (489 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Reduce unused CSS
270 ms · 446 KiBAbout 446 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
customerfields.com adds 457 ms
457 mscustomerfields.com costs a phone 457 ms of main-thread work and 268 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 Tag Manager adds 394 ms
394 msGoogle Tag Manager costs a phone 394 ms of main-thread work and 173 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.
Shopify adds 222 ms
222 msShopify costs a phone 222 ms of main-thread work and 369 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.
2,241 HTML elements
The page has 2,241 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
197 KiB3 images could be 197 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
62 KiBPolyfills for old browsers add 62 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Real-user CLS: 0.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 19.8 s
19.8 sYour largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Distillerie, malterie et chai de vieillissement des Hautes …”.
Speed Index: 18.0 s
18.0 sVisually, the page fills in at 18.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 4.6 s
4.6 sScripts block taps and scrolling for 4.6 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 55.7 s
55.7 sThe page becomes fully interactive after 55.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.621
0.621The layout shifts by 0.621 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 565 ms
565 msReal visitors wait 565 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 214 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 10.6 MB in 431 requests
10.6 MBYour homepage downloads 10.6 MB in 431 requests on a phone: scripts 5.4 MB (125), HTML 1.9 MB (11) and images 1.8 MB (24). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
EXTERIEURS_DOMAINE-7094_900x.progressive.jpg 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).
3 images far larger than shown
114 KiB3 images are downloaded at several times the size a phone draws them, for example hg_logo_decentre_gauche_blanc_rvb_1_1_168x.svg at 183 px wide, shown at 42 px. Resized copies would save about 114 KiB.
About 3.0 g of CO₂ per visit
3.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.01 g of CO₂e: 361.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
20 form fields without a label
20 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 4 problems
Structured data found (Organization and WebSite) but with 4 problems, for example “Organization: missing name”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
65 internal links, 4 external
The homepage links to 65 pages on hautesglaces.com and 4 external pages.
7 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Le Domaine des Hautes Glaces crée de bout en bout du whisky bio. C'est la plus ancienne distillerie de whisky bio au mo…”.
One H1 headline
Your main headline reads: “hautes glaces Ferme & Distillerie biologiques”.
Title: 60 characters
Your title is a healthy 60 characters: “Whisky français bio, single malt – Domaine des Hautes Glaces”.
Canonical URL set
The canonical URL is https://hautesglaces.com/.
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://hautesglaces.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
No llms.txt
There is no https://hautesglaces.com/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,115 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
1 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
2 small tap targets
2 of 5 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 628 words of copy
The homepage carries about 628 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “SUBSCRIBE!”.
8 short forms
8 short forms (6 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: LinkedIn Insight.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads LinkedIn Insight (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 hautesglaces.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Headquarters
- Saint-Jean-d'Herans
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on hautesglaces.com, including 21 speed issues, 2 SEO issues and 3 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.