Website review, no card needed

mannheimer.de logo

mannheimer.de website review

Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 85 checks

This review found 37 issues worth fixing on mannheimer.de, 17 of them high impact, across 85 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
3.8 s3.2 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.5 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
147 ms131 msMay 16Oct 31137 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026135 ms
May 30, 2026133 ms
Jun 6, 2026138 ms
Jun 13, 2026142 ms
Jun 20, 2026142 ms
Jun 27, 2026143 ms
Jul 4, 2026143 ms
Jul 11, 2026139 ms
Jul 18, 2026137 ms
Jul 25, 2026139 ms
Aug 1, 2026137 ms
Aug 8, 2026141 ms
Aug 15, 2026140 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026141 ms
Sep 12, 2026139 ms
Sep 19, 2026137 ms
Sep 26, 2026135 ms
Oct 3, 2026134 ms
Oct 10, 2026138 ms
Oct 17, 2026136 ms
Oct 24, 2026136 ms
Oct 31, 2026137 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 mannheimer.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mannheimer.de at 2.3 s2.3 s
  2. mannheimer.de at 4.5 s4.5 s
  3. mannheimer.de at 6.8 s6.8 s
  4. mannheimer.de at 9.1 s9.1 s
  5. mannheimer.de at 11.3 s11.3 s
  6. mannheimer.de at 13.6 s13.6 s
  7. mannheimer.de at 15.9 s15.9 s
  8. mannheimer.de at 18.1 s18.1 s

Speed

9 to fix52
  • Use efficient cache lifetimes

    5.3 s · 1.1 MB

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

  • Render-blocking requests

    4.3 s

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

  • Reduce unused JavaScript

    1.7 s · 401 KiB

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

  • Font display

    1.9 s

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

  • Reduce unused CSS

    1.1 s · 247 KiB

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

  • Mobile performance score: 52

    52/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Usercentrics CMP, piwik.pro and eye-able.com and others), adding 577 KiB and 624 ms of main-thread time.

  • Usercentrics CMP adds 423 ms

    423 ms

    Usercentrics CMP costs a phone 423 ms of main-thread work and 262 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.

  • Main-thread work: 2.9 s

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

  • Improve image delivery

    226 KiB

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

  • 10 long tasks on the main thread

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

  • Minify CSS

    150 ms · 35 KiB

    35 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    11 KiB

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

  • 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: 120 ms

    120 ms

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

Core Web Vitals

9 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: 17.9 s

    17.9 s

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

  • Speed Index: 24.5 s

    24.5 s

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

  • Time to Interactive: 18.2 s

    18.2 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Total Blocking Time: 253 ms

    253 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 749 ms

    749 ms

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

  • Cumulative Layout Shift: 0.039

    0.039

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 124 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 124 requests on a phone: scripts 1.1 MB (75), fonts 1,007 KiB (7) and images 889 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (473 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.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8895
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 15 tap targets too small

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

4 to fixGoogle 9278
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Sind Sie von Unwetterereignissen betroffen?”, “Boots­ver­sicherung NAUTIMA” and “Mannheimer? Ausgezeichnet!”). One clear main headline is easier for people and search engines.

  • 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 XML sitemap

    No XML sitemap at https://www.mannheimer.de/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 155 internal links, 8 external

    The homepage links to 155 pages on mannheimer.de and 8 external pages.

4 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Privat - Mannheimer Versicherung AG”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.mannheimer.de/privat declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.mannheimer.de/privat all use the title “Privat - Mannheimer Versicherung AG”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.mannheimer.de/privat, https://www.mannheimer.de/gewerbe, https://www.mannheimer.de/transport, https://www.mannheimer.de/karriere, https://www.mannheimer.de/leidenschaft and https://www.mannheimer.de/wohnen-eigentum have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.mannheimer.de/service-kontakt, https://www.mannheimer.de/leidenschaft, https://www.mannheimer.de/wohnen-eigentum and https://www.mannheimer.de/vorsorge-gesundheit have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.mannheimer.de/oldtimer, https://www.mannheimer.de/klassische-musik, https://www.mannheimer.de/musik-am-stromkreis and https://www.mannheimer.de/yachten-sportboote took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10093
  • 17 small tap targets

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

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

5 to fix50
  • 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 social proof

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

  • Local business without LocalBusiness data

    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 detected

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

  • No opening hours

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

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

    The homepage carries about 337 words of visible text.

3 checks passed
  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

  • 9 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) 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 mannheimer.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Hosting
Continentale Krankenversicherung a.G.

Company

Founded
1879
Headquarters
Mannheim

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on mannheimer.de, including 18 speed issues, 4 SEO issues and 5 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