Website review, no card needed

volksbank.it logo

volksbank.it website review

Visit site (opens in a new tab)Reviewed 28 October 202659 issues · 103 checks

This review found 59 issues worth fixing on volksbank.it, 28 of them high impact, across 103 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.3 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
175 ms156 msMay 9Oct 24173 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026161 ms
May 16, 2026160 ms
May 23, 2026158 ms
May 30, 2026161 ms
Jun 6, 2026164 ms
Jun 13, 2026166 ms
Jun 20, 2026166 ms
Jun 27, 2026163 ms
Jul 4, 2026161 ms
Jul 11, 2026161 ms
Jul 18, 2026162 ms
Jul 25, 2026161 ms
Aug 1, 2026161 ms
Aug 8, 2026160 ms
Aug 15, 2026159 ms
Aug 22, 2026159 ms
Aug 29, 2026160 ms
Sep 5, 2026161 ms
Sep 12, 2026162 ms
Sep 19, 2026167 ms
Sep 26, 2026170 ms
Oct 3, 2026172 ms
Oct 10, 2026173 ms
Oct 17, 2026172 ms
Oct 24, 2026173 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of volksbank.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. volksbank.it at 0.5 s0.5 s
  2. volksbank.it at 1.1 s1.1 s
  3. volksbank.it at 1.6 s1.6 s
  4. volksbank.it at 2.1 s2.1 s
  5. volksbank.it at 2.7 s2.7 s
  6. volksbank.it at 3.2 s3.2 s
  7. volksbank.it at 3.7 s3.7 s
  8. volksbank.it at 4.3 s4.3 s

Speed

13 to fix46
  • Use efficient cache lifetimes

    6.0 s · 7.8 MB

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

  • Improve image delivery

    1.0 s · 6.9 MB

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

  • Render-blocking requests

    4.3 s

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

  • Cookiebot adds 1.2 s

    1.2 s

    Cookiebot costs a phone 1.2 s of main-thread work and 144 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 6.1 s

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

  • 3,726 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Cookiebot, Google CDN and Other Google APIs/SDKs and others), adding 1.0 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    900 ms · 528 KiB

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

  • Reduce unused CSS

    750 ms · 170 KiB

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

  • 19 long tasks on the main thread

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

  • Google CDN adds 425 ms

    425 ms

    Google CDN costs a phone 425 ms of main-thread work and 741 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.

  • Font display

    400 ms

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

  • Minify CSS

    150 ms · 36 KiB

    36 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    16 KiB

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 122 ms

    122 ms

    Your server sent the HTML in 122 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 19.4 s

    19.4 s

    Your largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SPARMONAT OKTOBER Gemeinsam machen wir Träume wahr Entdecke…”.

  • Time to Interactive: 41.7 s

    41.7 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 978 ms

    978 ms

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

  • Total Blocking Time: 404 ms

    404 ms

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

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix28
  • Page weight: 11.4 MB in 147 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 147 requests on a phone: images 8.6 MB (42), scripts 1.6 MB (61) and other files 457 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

  • 25 images in older formats

    25 images (6.6 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.

  • 22 images below the first screen load straight away

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

  • 3 images far larger than shown

    123 KiB

    3 images are downloaded at several times the size a phone draws them, for example 42958a50-a241-712f-d2d3-f46f55dd19f0 at 500 px wide, shown at 124 px. Resized copies would save about 123 KiB.

  • About 3.2 g of CO₂ per visit

    3.24 g

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

Accessibility

19 to fixGoogle 7178
  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (4 elements)

    ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.

  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • 15 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

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

  • 27 form fields without a label

    27 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (9 elements).

  • 2 links without text

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

  • ARIA toggle fields do not have accessible names

    ARIA toggle fields do not have accessible names (1 element).

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (2 elements).

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 14 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9286
  • No structured data

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

  • 21 links crawlers can't follow

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

  • Meta description is long (177 characters)

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 358 internal links, 19 external

    The homepage links to 358 pages on volksbank.it and 19 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Navigation”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Volksbank online banking • Alle Produkte & Leistungen | Volksbank”.

  • Canonical URL set

    The canonical URL is https://www.volksbank.it/de/home.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.volksbank.it/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.volksbank.it/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (11,453 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://www.volksbank.it/de/home and https://www.volksbank.it/de all use the title “Volksbank online banking • Alle Produkte & Leistungen | Volksbank”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 links to non-canonical URLs

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

  • 1 page slow to respond

    https://www.volksbank.it/de/onlinebanking/mobilebanking-app-firmenkunden took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    28 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    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 social proof

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

  • A 25-field form

    Your longest form asks for 25 fields (17 required). Every extra field lowers completion.

  • No risk reducer

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

  • About 1,108 words of copy

    The homepage carries about 1,108 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Center”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at volksbank.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
Analytics
Google Analytics
Hosting
Irideos

Company

Founded
1840
Headquarters
Vienna

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 59 issues on volksbank.it, including 23 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25