sac-saas.ch website review

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

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

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

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

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

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

Google Tag Manager costs a phone 186 ms of main-thread work and 450 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.

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

About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

5 third-party services load with your homepage (Google Tag Manager, cleantalk.org and PrintFriendly and others), adding 585 KiB and 201 ms of main-thread time.

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

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

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

Visually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 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 “Sac-Saas Logo”. Most of its time is resource load delay (2.7 s).

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.3 MB in 149 requests on a phone: images 1.8 MB (36), scripts 1.1 MB (85) and fonts 205 KiB (5). Under 2 MB keeps phones on slow connections fast.

20 images (1.4 MB) 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.

18 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 15 characters: “Home - Sac-Saas”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 33 characters: “Alle Touren News & Tourenberichte”. 70 to 160 characters is enough to sell the click.

The homepage links to 269 pages on sac-saas.ch and 8 external pages.

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.

There is no https://sac-saas.ch/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://sac-saas.ch/sektion, https://sac-saas.ch/unser-engagement, https://sac-saas.ch/vorstand, https://sac-saas.ch/tourenleiter-sac-saas, https://sac-saas.ch/tourenleiter-jo and https://sac-saas.ch/kommissionen and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sac-saas.ch/vorstand, https://sac-saas.ch/tourenleiter-sac-saas, https://sac-saas.ch/clubgeschichte, https://sac-saas.ch/jahresbericht-protokoll-gv-2025, https://sac-saas.ch/ehrenmitglieder-sac-saas and https://sac-saas.ch/ehemalige-vorstands-und-kommissionsmitglieder and 1 other took over 3 s to send their HTML from our server.

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

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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