Website review, no card needed

berenberg.de logo

berenberg.de website review

Visit site (opens in a new tab)Reviewed 31 October 202630 issues · 82 checks

This review found 30 issues worth fixing on berenberg.de, 6 of them high impact, across 82 checks. The most urgent: font display. 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
3.0 s1.1 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.9 s
May 23, 20262.2 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.5 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.4 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
123 ms110 msMay 9Oct 24120 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026114 ms
May 16, 2026114 ms
May 23, 2026117 ms
May 30, 2026120 ms
Jun 6, 2026121 ms
Jun 13, 2026119 ms
Jun 20, 2026114 ms
Jun 27, 2026111 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026113 ms
Aug 1, 2026116 ms
Aug 8, 2026116 ms
Aug 15, 2026118 ms
Aug 22, 2026117 ms
Aug 29, 2026116 ms
Sep 5, 2026120 ms
Sep 12, 2026120 ms
Sep 19, 2026121 ms
Sep 26, 2026119 ms
Oct 3, 2026116 ms
Oct 10, 2026116 ms
Oct 17, 2026116 ms
Oct 24, 2026120 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 berenberg.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. berenberg.de at 1.1 s1.1 s
  2. berenberg.de at 2.3 s2.3 s
  3. berenberg.de at 3.4 s3.4 s
  4. berenberg.de at 4.6 s4.6 s
  5. berenberg.de at 5.7 s5.7 s
  6. berenberg.de at 6.8 s6.8 s
  7. berenberg.de at 8.0 s8.0 s
  8. berenberg.de at 9.1 s9.1 s

Speed

6 to fix83
  • Font display

    1.9 s

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

  • Use efficient cache lifetimes

    450 ms · 692 KiB

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

  • Mobile performance score: 83

    83/100

    Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    387 KiB

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

  • Reduce unused JavaScript

    300 ms · 24 KiB

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

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (cookiefirst.com), adding 92 KiB and 23 ms of main-thread time.

  • Legacy JavaScript

    28 KiB

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

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 270 ms of it running JavaScript. That is comfortably low.

  • Server response: 142 ms

    142 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 7.2 s

    7.2 s

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

  • Largest content (LCP) got 43% slower for real visitors

    +43%

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.3 s).

  • Tap response (INP) held steady for real visitors

    +4%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 130 ms

    130 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 651 ms

    651 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Time to Interactive: 3.4 s

    3.4 s

    The page is fully interactive after 3.4 s.

  • Cumulative Layout Shift: 0.067

    0.067

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix81
  • An image on the first screen is lazy-loaded

    iStock-2042540550_bearbeitet_7c7c0c922e898f87d8c3e610dae7bbd 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).

  • 1 image far larger than shown

    216 KiB

    1 image is downloaded at several times the size a phone draws it, for example Hamburg_600x375.jpg at 1,400 px wide, shown at 247 px. Resized copies would save about 216 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (300 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (300 KiB) is 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.

  • About 0.3 g of CO₂ per visit

    0.31 g

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

1 checks passed
  • Page weight: 1.1 MB in 38 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 38 requests on a phone: images 517 KiB (9), scripts 299 KiB (19) and fonts 222 KiB (4). That is a lean page.

Accessibility

4 to fixGoogle 8794
  • 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.

  • 4 text elements with low contrast

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

  • All page content should be contained by landmarks (3 elements)

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

  • 2 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Berenberg | Heute handeln, um das Morgen zu gestalten. - Berenberg”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Heute handeln,um das Morgenzu gestalten.” and “Unsere Fonds entdecken”). One clear main headline is easier for people and search engines.

  • 88 internal links, 14 external

    The homepage links to 88 pages on berenberg.de and 14 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Die Welt ist voller Ideen - doch erst Taten verändern sie. Bei Berenberg machen wir aus den Ambitionen unserer Kunden R…”.

  • Canonical URL set

    The canonical URL is https://www.berenberg.de/.

  • Structured data in place

    Structured data found: Article, LocalBusiness and Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.berenberg.de/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (527 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.berenberg.de/bereiche/wealth-management and https://www.berenberg.de/kunden/vermoegende-privatkunden all use the title “Private Wealth Management bei Berenberg – Vermögensaufbau - Berenberg”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.berenberg.de/ueber-uns, https://www.berenberg.de/unsere-kunden and https://www.berenberg.de/unsere-kunden/institutionelle-kunden have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.berenberg.de/bereiche/wealth-management and https://www.berenberg.de/kunden/vermoegende-privatkunden use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.berenberg.de/kunden/vermoegende-privatkunden, whose canonical is https://www.berenberg.de/bereiche/wealth-management. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 3 small tap targets

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No direct contact details

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

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

  • 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 538 words of copy

    The homepage carries about 538 words of visible text.

1 checks passed
  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • No consent tool detected

    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.

  • 2 other companies contacted

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

1 checks passed
  • 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 berenberg.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Azure

Company

Employees
1,331
Founded
1590
Headquarters
Hamburg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on berenberg.de, including 9 speed issues, 2 SEO issues and 6 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