laclusaz.com website review

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

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

25 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, YouTube and Google Tag Manager and others), adding 3.2 MB and 2.3 s of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page.

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

YouTube costs a phone 569 ms of main-thread work and 972 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 costs a phone 554 ms of main-thread work and 515 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 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

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

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

13 KiB could be saved by minifying CSS.

9 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.

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

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

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

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

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

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

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

Your homepage downloads 21.0 MB in 171 requests on a phone: images 15.8 MB (73), scripts 3.1 MB (50) and fonts 1.1 MB (6). Under 2 MB keeps phones on slow connections fast.

La-Clusaz-Hiver-19-20-BD©C.HUDRY-5-scaled.jpg weighs 534 KiB. On a phone connection a single image that size takes seconds.

1 image (93 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.

1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

12 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

The homepage links to 83 pages on laclusaz.com and 30 external pages.

There is no https://www.laclusaz.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.

https://www.laclusaz.com/la-station, https://www.laclusaz.com/ski, https://www.laclusaz.com/le-mag, https://www.laclusaz.com/le-mag/inspirations/votre-journee-parfaite-au-yoga-festival-2, https://www.laclusaz.com/le-mag/no-story-no-future/botanico-et-les-racines-du-coeur and https://www.laclusaz.com/le-mag/inspirations/vacancessportives-4-astuces-pour-bien-tricher have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.laclusaz.com/reservation/hebergements has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.laclusaz.com/reservation/hebergements and https://www.laclusaz.com/nl took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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 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 932 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 8 cookies, 1 of them by other companies (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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.