Website review, no card needed

alpedhuez.com logo

alpedhuez.com website review

Visit site (opens in a new tab)Reviewed 24 October 202641 issues · 86 checks

This review found 41 issues worth fixing on alpedhuez.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.4 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.6 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
155 ms116 msMay 2Oct 17145 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026141 ms
May 9, 2026146 ms
May 16, 2026150 ms
May 23, 2026149 ms
May 30, 2026146 ms
Jun 6, 2026135 ms
Jun 13, 2026126 ms
Jun 20, 2026122 ms
Jun 27, 2026122 ms
Jul 4, 2026122 ms
Jul 11, 2026122 ms
Jul 18, 2026126 ms
Jul 25, 2026129 ms
Aug 1, 2026129 ms
Aug 8, 2026127 ms
Aug 15, 2026125 ms
Aug 22, 2026120 ms
Aug 29, 2026121 ms
Sep 5, 2026124 ms
Sep 12, 2026127 ms
Sep 19, 2026129 ms
Sep 26, 2026128 ms
Oct 3, 2026130 ms
Oct 10, 2026145 ms
Oct 17, 2026145 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

Full-page screenshot of alpedhuez.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alpedhuez.com at 1.6 s1.6 s
  2. alpedhuez.com at 3.2 s3.2 s
  3. alpedhuez.com at 4.8 s4.8 s
  4. alpedhuez.com at 6.4 s6.4 s
  5. alpedhuez.com at 8.0 s8.0 s
  6. alpedhuez.com at 9.6 s9.6 s
  7. alpedhuez.com at 11.2 s11.2 s
  8. alpedhuez.com at 12.8 s12.8 s

Speed

15 to fix29
  • Reduce unused JavaScript

    5.1 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Use efficient cache lifetimes

    4.6 s · 1.5 MB

    98 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Render-blocking requests

    2.1 s

    27 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Reduce unused CSS

    1.8 s · 231 KiB

    About 231 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Google CDN adds 1.3 s

    1.3 s

    Google CDN costs a phone 1.3 s of main-thread work and 1.1 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: 12.2 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29 (desktop: 74). 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 (Google CDN, tolk.ai and Facebook and others), adding 2.0 MB and 3.4 s of main-thread time.

  • 20 long tasks on the main thread

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

  • tolk.ai adds 930 ms

    930 ms

    tolk.ai costs a phone 930 ms of main-thread work and 427 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.

  • Facebook adds 417 ms

    417 ms

    Facebook costs a phone 417 ms of main-thread work and 212 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.

  • wonderpush.com adds 361 ms

    361 ms

    wonderpush.com costs a phone 361 ms of main-thread work and 104 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.

  • Legacy JavaScript

    300 ms · 27 KiB

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

  • Minify JavaScript

    300 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Improve image delivery

    150 ms · 144 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 74 but mobile only 29. 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: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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: 63.1 s

    63.1 s

    Your largest element takes 63.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies and gives you control over what you …”.

  • Time to Interactive: 67.5 s

    67.5 s

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

  • Total Blocking Time: 4.1 s

    4.1 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 23 images without width and height

    23 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 141 ms to 145 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 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.016

    0.016

    The layout barely moves while loading (CLS 0.016, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 16.0 MB in 164 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 164 requests on a phone: images 12.5 MB (56), scripts 2.2 MB (47) and fonts 532 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (342 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.

  • 2 images below the first screen load straight away

    2 images further down the page (57 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.53 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.53 g of CO₂e: 543.6 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

5 to fixGoogle 9594
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 3 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 50 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: 50 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9283
  • Title is short (18 characters)

    Your title is only 18 characters: “Home | Alpe d'Huez”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

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

  • 142 internal links, 51 external

    The homepage links to 142 pages on alpedhuez.com and 51 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Welcome to our home page, your starting point for all the essential information for your stay in our mountains - Alpe d…”.

  • Canonical URL set

    The canonical URL is https://www.alpedhuez.com/en/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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.alpedhuez.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (833 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.alpedhuez.com/llms.txt (6 KiB, 51 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.alpedhuez.com/en and / all use the title “Home | Alpe d'Huez”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.alpedhuez.com/en/discover/family-destination/family-plus/family-activities, https://www.alpedhuez.com/en/your-stay/day-nursery, https://www.alpedhuez.com/en/childrens-indoor-playground-agoralp and https://www.alpedhuez.com/en/your-stay/access/transport-to-the-resort have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.alpedhuez.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages slow to respond

    https://www.alpedhuez.com/en/your-stay/access/transport-to-the-resort and https://www.alpedhuez.com/en/your-stay/access/parking-lots took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 92100
  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    49 of 49 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 507 words of copy

    The homepage carries about 507 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Book your stay”, “buy your pass” and “book your stay”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 alpedhuez.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on alpedhuez.com, including 25 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25