Website review, no card needed
apobank.de website review
Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 78 checks
This review found 32 issues worth fixing on apobank.de, 11 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 151 ms |
| May 16, 2026 | 151 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 149 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 165 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 175 ms |
| Oct 17, 2026 | 173 ms |
| Oct 24, 2026 | 172 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
Speed
Reduce unused JavaScript
2.2 s · 400 KiBAbout 400 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Reduce unused CSS
1.6 s · 260 KiBAbout 260 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Improve image delivery
1.1 s · 717 KiB8 images could be 717 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.4 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
800 ms · 140 KiBPolyfills for old browsers add 140 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 800 ms faster on a phone.
2,256 HTML elements
The page has 2,256 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (piwik.pro, cookieinformation.com and JSDelivr CDN), adding 150 KiB and 146 ms of main-thread time.
Document request latency
142 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 484 ms of it running JavaScript. That is comfortably low.
Server response: 443 ms
443 msYour server sent the HTML in 443 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Um Ihnen ein optimales Nutzererlebnis zu bieten verwenden w…”.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 151 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 169 ms
169 msReal visitors wait 169 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 657 ms
657 msReal visitors wait 657 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 100 ms
100 msScripts block the page for only 100 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 60 requests
2.8 MBYour homepage downloads 2.8 MB in 60 requests on a phone: images 1.5 MB (42), scripts 738 KiB (5) and HTML 288 KiB (4). Under 2 MB keeps phones on slow connections fast.
12 images below the first screen load straight away
12 images further down the page (993 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (674 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.
2 images far larger than shown
261 KiB2 images are downloaded at several times the size a phone draws them, for example girokonto-apobank-frau-an-laptop-mit-bankkarte-1920-1080-16- at 1,920 px wide, shown at 310 px. Resized copies would save about 261 KiB.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 48 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
262 internal links, 19 external
The homepage links to 262 pages on apobank.de and 19 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Für Angehörige der Heilberufe sowie ihre Organisationen bietet die apoBank Beratung und alle Bankprodukte wie Konto, Fi…”.
One H1 headline
Your main headline reads: “Ihre Patienten werden immer älter. Sie übrigens auch.”.
Title: 43 characters
Your title is a healthy 43 characters: “Deutsche Apotheker- und Ärztebank - apoBank”.
Canonical URL set
The canonical URL is https://www.apobank.de/.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.apobank.de/sitemap.xml.
AI search readiness
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.apobank.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.
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 (1,455 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.apobank.de/service/video-beratung, which answers with an error. Visitors hit a dead end and search engines drop it.
6 pages share 3 titles
https://www.apobank.de/unsere-leistungen/konto-karte/online-banking and https://www.apobank.de/unsere-leistungen/weiterleitungsseite-online-banking all use the title “Allgemeine Informationen zum Online-Banking”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.apobank.de/unsere-leistungen/konto-karte/online-banking and https://www.apobank.de/unsere-leistungen/weiterleitungsseite-online-banking have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.apobank.de/unsere-leistungen/konto-karte and https://www.apobank.de/unsere-leistungen/konto-karte/konto-heilberufler use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.apobank.de/unsere-leistungen/konto-karte/online-banking, whose canonical is https://www.apobank.de/onlinebanking. 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 194 found) and read each the way a search engine does.
3 checks passed
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 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Executing inline event handler violates the following Content Security Policy directive 'script-src 'self' 'nonce-6ff31…”.
2 checks passed
Tap targets are thumb-sized
11 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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 940 words of copy
The homepage carries about 940 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
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.
4 other companies contacted
Loading the homepage contacts 4 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 apobank.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
- Technology Services Group
Company
- Employees
- 2,563
- Founded
- 1902
- Headquarters
- Düsseldorf
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on apobank.de, including 12 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.