rvs.at website review

4 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

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

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

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

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

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

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

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

3 third-party services load with your homepage (Optanon, Adobe Tag Manager and r-itservices.at), adding 231 KiB and 115 ms of main-thread time.

Polyfills for old browsers add 27 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.

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 23.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Traden mit kleinen Beträgen”.

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

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

Scripts block taps and scrolling for 857 ms in total while the page loads. Good is under 200 ms.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 57 requests on a phone: images 2.3 MB (22), scripts 1.7 MB (8) and fonts 312 KiB (5). Under 2 MB keeps phones on slow connections fast.

buehne-sp4-wp.png weighs 624 KiB. On a phone connection a single image that size takes seconds.

6 images (817 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 1.33 g of CO₂e: 159.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

Your meta description is 283 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BankOrCreditUnion) but with 1 problem, for example “BankOrCreditUnion: image is not an absolute URL ("https://www.raiffeisen.at/rvs/de/config/header-co…”.

1 link has no real href, so search engines can't follow it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 231 pages on rvs.at and 23 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.raiffeisen.at/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.raiffeisen.at/rvs/de/privatkunden.html and https://www.raiffeisen.at/rvs/de.html all use the title “Raiffeisenverband Salzburg | Privatkunden”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.raiffeisen.at/rvs/de/meine-bank/raiffeisen-bankengruppe/raiffeisenbanken/self-service.html and https://www.raiffeisen.at/rvs/de/privatkunden/kredit-leasing/der-fairecredit.html have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://www.raiffeisen.at/rvs/de.html, https://www.raiffeisen.at/rvs/de/meine-bank/raiffeisen-bankengruppe/raiffeisenbanken/self-service.html, https://www.raiffeisen.at/rvs/de/privatkunden/konto.html, https://www.raiffeisen.at/rvs/de/privatkunden/konto/girokonto.html, https://www.raiffeisen.at/rvs/de/privatkunden/konto/studentenkonto.html and https://www.raiffeisen.at/rvs/de/privatkunden/konto/jugendkonto.html took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 168 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.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,632 words of visible text.

Opening the homepage sets 5 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.