Website review, no card needed

kaestle.com logo

kaestle.com website review

Visit site (opens in a new tab)Reviewed 25 October 202628 issues · 75 checks

This review found 28 issues worth fixing on kaestle.com, 10 of them high impact, across 75 checks. The most urgent: avoid multiple page redirects. 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
3.2 s773 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.8 s
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.2 s
Jun 20, 20261.8 s
Jun 27, 20261.6 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
127 ms100 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026111 ms
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026114 ms
May 30, 2026113 ms
Jun 6, 2026118 ms
Jun 13, 2026116 ms
Jun 20, 2026115 ms
Jun 27, 2026115 ms
Jul 4, 2026112 ms
Jul 11, 2026106 ms
Jul 18, 2026103 ms
Jul 25, 2026105 ms
Aug 1, 2026108 ms
Aug 8, 2026113 ms
Aug 15, 2026119 ms
Aug 22, 2026117 ms
Aug 29, 2026120 ms
Sep 5, 2026118 ms
Sep 12, 2026116 ms
Sep 19, 2026117 ms
Sep 26, 2026120 ms
Oct 3, 2026124 ms
Oct 10, 2026122 ms
Oct 17, 2026120 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 kaestle.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kaestle.com at 0.9 s0.9 s
  2. kaestle.com at 1.8 s1.8 s
  3. kaestle.com at 2.7 s2.7 s
  4. kaestle.com at 3.7 s3.7 s
  5. kaestle.com at 4.6 s4.6 s
  6. kaestle.com at 5.5 s5.5 s
  7. kaestle.com at 6.4 s6.4 s
  8. kaestle.com at 7.3 s7.3 s

Speed

6 to fix53
  • Avoid multiple page redirects

    6.3 s

    The page goes through 1 redirect before it starts loading, costing about 6.3 s. Link and advertise the final URL directly.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused JavaScript

    600 ms · 181 KiB

    About 181 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Main-thread work: 3.9 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, embedsocial.com and modapps.com.au and others), adding 1.3 MB and 250 ms of main-thread time.

  • embedsocial.com adds 85 ms

    85 ms

    embedsocial.com costs a phone 85 ms of main-thread work and 965 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.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    87 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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: 5 ms

    5 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 22.9 s

    22.9 s

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

  • Time to Interactive: 26.4 s

    26.4 s

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

  • First Contentful Paint: 7.6 s

    7.6 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 67 ms

    67 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 524 ms

    524 ms

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

  • Largest content (LCP) got 61% faster for real visitors

    -61%

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

  • Total Blocking Time: 166 ms

    166 ms

    Scripts block the page for only 166 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 36.4 MB in 516 requests

    36.4 MB

    Your homepage downloads 36.4 MB in 516 requests on a phone: media 30.1 MB (8), images 3.3 MB (106) and other files 1.4 MB (261). Under 2 MB keeps phones on slow connections fast.

  • About 10.3 g of CO₂ per visit

    10.33 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

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

  • 3 images without alt text

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

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

SEO

2 to fixGoogle 7796
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • 163 internal links, 6 external

    The homepage links to 163 pages on kaestle.com and 6 external pages.

8 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Discover high-end alpine, touring and nordic skis from Kästle. Precision-engineered since 1924 for skiers who demand ex…”.

  • One H1 headline

    Your main headline reads: “KÄSTLE GmbH”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Kästle | Alpine, Touring & Nordic Skis”.

  • Canonical URL set

    The canonical URL is https://kaestle.com/en-us.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and 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://kaestle.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), 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.

3 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 (568 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://kaestle.com/en-us/collections/alpine-race, https://kaestle.com/en-us/collections/piste, https://kaestle.com/en-us/collections/allmountain, https://kaestle.com/en-us/collections/tour, https://kaestle.com/en-us/collections/freeride and https://kaestle.com/en-us/collections/freestyle and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 7785
  • 10 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 291 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn more”, “Subscribe” and “Contact us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 15 cookies set on arrival

    15

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 kaestle.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
Shopify
Hosting
Shopify Hosted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on kaestle.com, including 10 speed issues, 2 SEO issues and 4 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