prosenectute.ch website review

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

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

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

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

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

5 images could be 245 KiB 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.

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

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

21 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (azurestaticapps.net, Cloudflare CDN and Ipify), adding 270 KiB and 112 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zwei ältere Personen beim wandern.”.

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

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

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

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

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

Your homepage downloads 2.0 MB in 46 requests on a phone: images 1.5 MB (16), scripts 379 KiB (20) and stylesheets 51 KiB (2). Under 2 MB keeps phones on slow connections fast.

PS_Slider_Digitaler_Nachlas_2800x1000px_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example ZEWO_Claim_Footer.png at 3,000 px wide, shown at 293 px. Resized copies would save about 85 KiB.

1 image further down the page (93 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 0.57 g of CO₂e: 68.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 21 characters: “Pro Senectute Schweiz”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 5 <h1> headlines (“Beziehungen im Alter”, “Niemand will alleine alt werden...” and “So regeln Sie Ihr digitales Erbe”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 204 pages on prosenectute.ch and 58 external pages.

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.

There is no https://www.prosenectute.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://www.prosenectute.ch/de.html and / all use the title “Pro Senectute Schweiz”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.prosenectute.ch/de/suche.html has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.prosenectute.ch/de.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ and https://www.prosenectute.ch/de/ratgeber/wohnen.html took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://ashy-ocean-0ddefcb03.7.azurestaticapps.net/maintenance.json' from origin 'https://www.prose…”.

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

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 535 words of visible text.

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