spktw.de website review

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

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

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

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

About 221 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 34 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

14 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

8 long tasks block the main thread while loading, the longest for 232 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 third-party service load with your homepage (sparkasse.de), adding 3 KiB and 0 ms of main-thread time.

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.

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

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir, als Ihre Sparkasse, verwenden Cookies, die unbedingt e…”. Most of its time is element render delay (4.6 s).

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

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

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

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

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

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

11 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-17, real Chrome visitors' tap response (inp) went from 100 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

7 images are downloaded at several times the size a phone draws them, for example 1789538673633.jpg at 1,280 px wide, shown at 72 px. Resized copies would save about 679 KiB.

Your homepage downloads 2.5 MB in 40 requests on a phone: images 1.4 MB (26), stylesheets 366 KiB (2) and fonts 344 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

13 images further down the page (1.1 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.71 g of CO₂e: 84.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

There are 2 <h1> headlines (“Mehr Zukunft für Dein Geld!” and “Mehr Zukunft für Dein Geld!”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 367 pages on spktw.de and 16 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.spktw.de/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.spktw.de/fi/home.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.spktw.de/de/home.html and https://www.spktw.de/fi/home.html all use the title “Internet-Filiale - Sparkasse Bad Tölz-Wolfratshausen”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.spktw.de/en/home.html, https://www.spktw.de/fr/home.html, https://www.spktw.de/pl/home.html, https://www.spktw.de/tr/home.html, https://www.spktw.de/cs/home.html and https://www.spktw.de/de/home/beratung-digital0.html have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.spktw.de/de/home/private-banking.html, whose canonical is https://www.spktw.de/de/home/privatkunden/private-banking.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.spktw.de/fi/home.html, https://www.spktw.de/de/home/barrierefreiheit/leichte-sprache.html, https://www.spktw.de/de/home/barrierefreiheit/gebaerdensprache.html, https://www.spktw.de/en/home.html, https://www.spktw.de/fr/home.html and https://www.spktw.de/pl/home.html and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

Large scripts ship without source maps.

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: 7 trust badges. 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 494 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 11 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.