bcv.ch website review

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

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

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

16 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

1 file is served with short cache lifetimes, so returning visitors download them again (394 KiB).

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

1 third-party service load with your homepage (Adobe Tag Manager), adding 1 KiB and 0 ms of main-thread time.

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

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BCV - Solutions patrimoniales”.

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

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

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

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

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

Your homepage downloads 8.2 MB in 61 requests on a phone: images 5.4 MB (24), scripts 1.9 MB (11) and stylesheets 522 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example PIB romand 2026.jpg at 4,096 px wide, shown at 370 px. Resized copies would save about 2.8 MB.

18 images (5.3 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.

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

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

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

3 links inside paragraphs rely on colour alone to stand out.

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

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

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.

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

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

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

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

No XML sitemap at https://www.bcv.ch/fr/home.sitemap.xml, so Google discovers your pages only by following links.

Your hreflang tags are invalid, so Google may show the wrong language version.

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

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

The homepage links to 75 pages on bcv.ch and 9 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 /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.

/vfh is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, /fr/home.html and /vfh all use the title “BCV - Banque Cantonale Vaudoise”. Search engines can't tell which page to show for a search, so each competes with the others.

/fr/home/particuliers/produits/e-banking/cybersecurite.html, /fr/home/particuliers.html, /fr/home/private-banking.html, /fr/home/entreprises-et-institutions.html, /fr/home/la-bcv/a-propos-de-nous/ou-nous-trouver.html and /vfh and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /de/home.html, whose canonical is /de/home/die-bcv.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/vfh has no <h1> headline, so visitors and search engines get no clear main topic.

/fr/home/particuliers/produits/e-banking/cybersecurite.html, /fr/home.html, /fr/home/particuliers.html, /fr/home/private-banking.html, /vfh and /de/home.html and 2 others took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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.

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

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