vvrb.de website review

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

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

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

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

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

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

2 third-party services load with your homepage (Optanon and Adobe Scene7), adding 1.2 MB and 39 ms of main-thread time.

Adobe Scene7 costs a phone 0 ms of main-thread work and 914 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.

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

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

28 KiB could be saved by minifying JavaScript.

2 images could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mann und Frau sitzen auf einem Sofa vor dem Laptop und scha…”.

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

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

The page becomes fully interactive after 13.6 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.3 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 2.4 MB in 112 requests on a phone: scripts 1.0 MB (49), images 979 KiB (42) and fonts 221 KiB (5). Under 2 MB keeps phones on slow connections fast.

prfssnls_mitte:3-2 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).

2 images (61 KiB) 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.

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

8 buttons have no accessible name, so screen readers announce just “button”.

Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 96 characters, so Google will cut it off around 60: “Startseite Ihrer Vereinigte Volksbank Raiffeisenbank eG - Vereinigte Volksbank Raiffeisen…”.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 26 pages on vvrb.de and 7 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.

The HTML your server sends has 214 of the 421 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.vvrb.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.vvrb.de/services_cloud/portal is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.vvrb.de/karriere.html and https://www.vvrb.de/meine-bank/karriere.html all use the title “Karriere - Vereinigte Volksbank Raiffeisenbank eG”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vvrb.de/services_cloud/portal and https://www.vvrb.de/service/online-services/online-terminvereinbarung.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.vvrb.de/karriere.html and https://www.vvrb.de/meine-bank/karriere.html use the same meta description. A description written for each page earns more clicks.

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

https://www.vvrb.de/services_cloud/portal and https://www.vvrb.de/service/online-services/online-terminvereinbarung.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vvrb.de/privatkunden.html, https://www.vvrb.de/firmenkunden.html, https://www.vvrb.de/banking-und-vertraege.html and https://www.vvrb.de/service/online-services/online-terminvereinbarung.html 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.

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

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

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.

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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

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