Website review, no card needed

wellness-saas.ch logo

wellness-saas.ch website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 77 checks

This review found 29 issues worth fixing on wellness-saas.ch, 9 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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
1.6 s820 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Aug 15, 2026992 ms
Aug 22, 2026994 ms
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 2026959 ms
Oct 10, 2026950 ms
Oct 17, 2026909 ms
Oct 24, 2026955 ms
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
88 ms68 msMay 16Oct 3176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202680 ms
May 30, 202682 ms
Jun 6, 202686 ms
Jul 4, 202674 ms
Aug 15, 202670 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202675 ms
Sep 12, 202676 ms
Sep 19, 202677 ms
Sep 26, 202676 ms
Oct 3, 202672 ms
Oct 10, 202673 ms
Oct 17, 202672 ms
Oct 24, 202674 ms
Oct 31, 202676 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 wellness-saas.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wellness-saas.ch at 0.4 s0.4 s
  2. wellness-saas.ch at 0.8 s0.8 s
  3. wellness-saas.ch at 1.1 s1.1 s
  4. wellness-saas.ch at 1.5 s1.5 s
  5. wellness-saas.ch at 1.9 s1.9 s
  6. wellness-saas.ch at 2.3 s2.3 s
  7. wellness-saas.ch at 2.6 s2.6 s
  8. wellness-saas.ch at 3.0 s3.0 s

Speed

6 to fix55
  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 115 KiB

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

  • Use efficient cache lifetimes

    450 ms · 137 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (cdn-website.com, termly.io and dwhitelabel.com and others), adding 2.2 MB and 293 ms of main-thread time.

  • cdn-website.com adds 203 ms

    203 ms

    cdn-website.com costs a phone 203 ms of main-thread work and 1.8 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.

  • Reduce unused CSS

    300 ms · 50 KiB

    About 50 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.

  • Improve image delivery

    150 ms · 49 KiB

    4 images could be 49 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.

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 409 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.60

    0.60

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

  • Largest Contentful Paint: 11.4 s

    11.4 s

    Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wellness Hotel Christiania”.

  • Time to Interactive: 11.4 s

    11.4 s

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

  • Cumulative Layout Shift: 0.449

    0.449

    The layout shifts by 0.449 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    -6%

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

8 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 73 ms

    73 ms

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 584 ms

    584 ms

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

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

    -29%

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

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 47 ms

    47 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 70 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 70 requests on a phone: images 1.3 MB (20), scripts 443 KiB (27) and fonts 405 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

3 to fixGoogle 9695
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (7 elements)

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 36 internal links, 13 external

    The homepage links to 36 pages on wellness-saas.ch and 13 external pages.

6 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Herzlich willkommen im Wellness-Hotel Christiania in Saas-Almagell - Ihre Urlaubsoase inmitten der Walliser Alpen.”.

  • One H1 headline

    Your main headline reads: “Herzlich willkommen”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Christiania ▪︎ Hotel & Wellness ▪︎ Saas-Almagell”.

  • Canonical URL set

    The canonical URL is https://www.hotel-christiania.ch/.

  • 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.hotel-christiania.ch/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • llms.txt published

    The site publishes https://www.hotel-christiania.ch/llms.txt (4 KiB, 22 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages share a title

    / and https://www.hotel-christiania.ch/en-gb all use the title “Christiania ▪︎ Hotel & Wellness ▪︎ Saas-Almagell”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.hotel-christiania.ch/galerie/hotel--wellness and https://www.hotel-christiania.ch/galerie/umgebung use the same meta description. A description written for each page earns more clicks.

  • 5 pages with very little text

    https://www.hotel-christiania.ch/online-buchen--sonderangebote/online-buchen, https://www.hotel-christiania.ch/galerie/hotel--wellness, https://www.hotel-christiania.ch/galerie/zimmer, https://www.hotel-christiania.ch/galerie/kulinarisches and https://www.hotel-christiania.ch/galerie/umgebung have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 pages slow to respond

    https://www.hotel-christiania.ch/galerie/kulinarisches, https://www.hotel-christiania.ch/galerie/umgebung, https://www.hotel-christiania.ch/kontakt, https://www.hotel-christiania.ch/en-gb and https://www.hotel-christiania.ch/impressum took over 3 s to send their HTML from our server.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 11 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 11 pages that loaded have a meta description.

  • 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 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 9 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 249 words

    The homepage has only about 249 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 wellness-saas.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on wellness-saas.ch, including 11 speed issues, 3 SEO issues and 5 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