Analysis
Website
lemon.markets
Summary
About
Overall Score of Website
44
Analysis from
2026-03-17
Company
lemon.markets
Description
lemon.markets is a BaFin-licensed brokerage-as-a-service API platform enabling fintechs, banks, and software companies to launch compliant investment products in stocks, ETFs, and funds — now a wholly-owned subsidiary of dwpbank, Germany's central securities settlement bank.
Market
Brokerage-as-a-Service / Embedded Investing Infrastructure / European FinTech API
Audience
Fintech Founders, Bank Product Managers, Digital Wealth Managers, Neobank Product Teams, Embedded Finance Developers — primarily European market
HQ
Berlin, Germany
Summary
Spider Chart
Structure
28
Copy
50
Brand
45
SEO
42
Enterprise Readiness
38
UX
47
Freshness
48
Copy
52
Performance
58
Brand
35
Structure
Acquisition by dwpbank — Completely Absent from Site
Score
28
Severity
High
Finding
dwpbank — Germany's central securities settlement bank processing €2.2 trillion in assets — completed its acquisition of lemon.markets on September 30, 2025. This is arguably the most significant trust and credibility signal the company possesses: being a wholly-owned subsidiary of one of Germany's most systemically important financial market infrastructure providers. Yet the homepage, the About page, and every page on the site makes zero mention of dwpbank. A potential partner evaluating lemon.markets for brokerage infrastructure who does not already know the acquisition history has no way to discover this relationship from the website.
Recommendation
Add a 'Part of dwpbank' badge or footer callout immediately. A dedicated section on the homepage explaining the dwpbank relationship — its scale (€2.2 trillion in assets), the regulatory standing it provides, and the operational continuity it guarantees — is one of the most powerful conversion arguments available for risk-averse bank and fintech partners. The acquisition should be the lead trust story on every enterprise sales page, not an invisible fact buried in press coverage from October 2025.
Structure
Acquisition by dwpbank — Completely Absent from Site
Score
28
Severity
High
Finding
dwpbank — Germany's central securities settlement bank processing €2.2 trillion in assets — completed its acquisition of lemon.markets on September 30, 2025. This is arguably the most significant trust and credibility signal the company possesses: being a wholly-owned subsidiary of one of Germany's most systemically important financial market infrastructure providers. Yet the homepage, the About page, and every page on the site makes zero mention of dwpbank. A potential partner evaluating lemon.markets for brokerage infrastructure who does not already know the acquisition history has no way to discover this relationship from the website.
Recommendation
Add a 'Part of dwpbank' badge or footer callout immediately. A dedicated section on the homepage explaining the dwpbank relationship — its scale (€2.2 trillion in assets), the regulatory standing it provides, and the operational continuity it guarantees — is one of the most powerful conversion arguments available for risk-averse bank and fintech partners. The acquisition should be the lead trust story on every enterprise sales page, not an invisible fact buried in press coverage from October 2025.
Copy
Hero Headline — Generic Infrastructure Framing
Score
50
Severity
Medium
Finding
The German homepage headline 'Die Infrastruktur für Wertpapierhandel' (The infrastructure for securities trading) is descriptive but category-generic. The English version reads 'The Infrastructure to power investment products' — equally flat. Neither headline conveys the specific competitive advantage of lemon.markets: API-first architecture that reduces integration from months to weeks, BaFin-licensed infrastructure, the dwpbank backing, or the goal of opening 100 million brokerage accounts across Europe. The sub-headline is more specific but the H1 gives a prospect nothing to grab onto versus competitors like Upvest or Solarisbank.
Recommendation
Test a more outcome-anchored H1: 'Launch a compliant brokerage product in weeks, not months — powered by BaFin-licensed infrastructure.' Or lead with scale: 'The brokerage infrastructure behind 100 million European investment accounts.' The current headline is technically accurate but undifferentiated. For developer and product evaluators landing from search, the specific claim of weeks-to-launch and regulatory coverage is the conversion hook.
Copy
Hero Headline — Generic Infrastructure Framing
Score
50
Severity
Medium
Finding
The German homepage headline 'Die Infrastruktur für Wertpapierhandel' (The infrastructure for securities trading) is descriptive but category-generic. The English version reads 'The Infrastructure to power investment products' — equally flat. Neither headline conveys the specific competitive advantage of lemon.markets: API-first architecture that reduces integration from months to weeks, BaFin-licensed infrastructure, the dwpbank backing, or the goal of opening 100 million brokerage accounts across Europe. The sub-headline is more specific but the H1 gives a prospect nothing to grab onto versus competitors like Upvest or Solarisbank.
Recommendation
Test a more outcome-anchored H1: 'Launch a compliant brokerage product in weeks, not months — powered by BaFin-licensed infrastructure.' Or lead with scale: 'The brokerage infrastructure behind 100 million European investment accounts.' The current headline is technically accurate but undifferentiated. For developer and product evaluators landing from search, the specific claim of weeks-to-launch and regulatory coverage is the conversion hook.
Brand
Customer Logos — Anonymous and Unquantified
Score
45
Severity
Medium
Finding
The homepage has no visible customer logo strip. The partner section shows BNP Paribas, Tradegate, Deutsche Bank, and Allfunds as institutional partners — strong signals — but these are clearing and exchange partners, not end-customer logos. Known clients include Tomorrow Banking, Optio (Incentives), and Holvi (confirmed in press coverage), yet none appear on the homepage. For a B2B infrastructure API targeting fintech founders, bank product teams, and digital wealth managers, a customer reference section with recognisable names and use-case descriptions is the primary conversion signal.
Recommendation
Add a customer section with at minimum Tomorrow Banking, Optio, and Holvi logos alongside one-line use case descriptions: 'Optio — equity compensation infrastructure for German employees; Tomorrow Banking — sustainable investing product.' Source 2-3 more customer quotes for the website. A developer evaluating a brokerage API wants to know who else has trusted it with live customer money — currently the site provides zero evidence of live production deployments.
Brand
Customer Logos — Anonymous and Unquantified
Score
45
Severity
Medium
Finding
The homepage has no visible customer logo strip. The partner section shows BNP Paribas, Tradegate, Deutsche Bank, and Allfunds as institutional partners — strong signals — but these are clearing and exchange partners, not end-customer logos. Known clients include Tomorrow Banking, Optio (Incentives), and Holvi (confirmed in press coverage), yet none appear on the homepage. For a B2B infrastructure API targeting fintech founders, bank product teams, and digital wealth managers, a customer reference section with recognisable names and use-case descriptions is the primary conversion signal.
Recommendation
Add a customer section with at minimum Tomorrow Banking, Optio, and Holvi logos alongside one-line use case descriptions: 'Optio — equity compensation infrastructure for German employees; Tomorrow Banking — sustainable investing product.' Source 2-3 more customer quotes for the website. A developer evaluating a brokerage API wants to know who else has trusted it with live customer money — currently the site provides zero evidence of live production deployments.
SEO
German-Only Canonical Homepage — English Discoverability Gap
Score
42
Severity
Medium
Finding
The site uses /de-de and /en-de locale paths. The root domain www.lemon.markets redirects to /en-de (English) per the search result snippet, but the page audited is /de-de. More critically, the site's primary target audience — European fintech founders, bank product managers, and developers evaluating brokerage APIs — searches primarily in English ('brokerage API Europe', 'BaaS API securities', 'embedded brokerage infrastructure'). The English version of the site (/en-de) appears to exist but is not clearly canonical from the homepage structure. High-intent developer queries in English that would land a prospect directly on the product are potentially under-served.
Recommendation
Audit hreflang implementation across /de-de and /en-de to ensure correct canonical signalling. Ensure the English homepage at /en-de (or the root redirect) is the primary indexed version for English-language searches. Build dedicated English-language landing pages targeting 'brokerage API Europe', 'securities infrastructure API', and 'BaFin-licensed brokerage as a service' — the queries a UK fintech or Dutch neobank would use when evaluating lemon.markets.
SEO
German-Only Canonical Homepage — English Discoverability Gap
Score
42
Severity
Medium
Finding
The site uses /de-de and /en-de locale paths. The root domain www.lemon.markets redirects to /en-de (English) per the search result snippet, but the page audited is /de-de. More critically, the site's primary target audience — European fintech founders, bank product managers, and developers evaluating brokerage APIs — searches primarily in English ('brokerage API Europe', 'BaaS API securities', 'embedded brokerage infrastructure'). The English version of the site (/en-de) appears to exist but is not clearly canonical from the homepage structure. High-intent developer queries in English that would land a prospect directly on the product are potentially under-served.
Recommendation
Audit hreflang implementation across /de-de and /en-de to ensure correct canonical signalling. Ensure the English homepage at /en-de (or the root redirect) is the primary indexed version for English-language searches. Build dedicated English-language landing pages targeting 'brokerage API Europe', 'securities infrastructure API', and 'BaFin-licensed brokerage as a service' — the queries a UK fintech or Dutch neobank would use when evaluating lemon.markets.
Enterprise Readiness
Pricing — Completely Absent
Score
38
Severity
High
Finding
There is no pricing page, no pricing link in the nav or footer, no 'Request a quote' button beyond the generic 'Jetzt loslegen / Get started' CTA, and no pricing model indication anywhere on the site. For a B2B infrastructure API competing against Upvest and in-house builds, the absence of even a conceptual pricing framework (per-account, per-transaction, tiered by volume) forces every evaluation into a sales conversation before a prospect can even assess budget fit. This is particularly friction-heavy for fintech startups with limited procurement resources.
Recommendation
Add a /pricing page (or /preise for the German version) with at minimum a conceptual model: per-active-account pricing, or a tiered structure (startup / growth / enterprise) with volume-based discounts indicated. Even 'pricing available on request' with a stated minimum commitment level helps prospects self-qualify. For developer-led evaluations — which are the primary acquisition path for API-first infrastructure — pricing transparency at some level dramatically reduces time-to-first-conversation.
Enterprise Readiness
Pricing — Completely Absent
Score
38
Severity
High
Finding
There is no pricing page, no pricing link in the nav or footer, no 'Request a quote' button beyond the generic 'Jetzt loslegen / Get started' CTA, and no pricing model indication anywhere on the site. For a B2B infrastructure API competing against Upvest and in-house builds, the absence of even a conceptual pricing framework (per-account, per-transaction, tiered by volume) forces every evaluation into a sales conversation before a prospect can even assess budget fit. This is particularly friction-heavy for fintech startups with limited procurement resources.
Recommendation
Add a /pricing page (or /preise for the German version) with at minimum a conceptual model: per-active-account pricing, or a tiered structure (startup / growth / enterprise) with volume-based discounts indicated. Even 'pricing available on request' with a stated minimum commitment level helps prospects self-qualify. For developer-led evaluations — which are the primary acquisition path for API-first infrastructure — pricing transparency at some level dramatically reduces time-to-first-conversation.
UX
Single CTA Across All Entry Points — No Developer Path
Score
47
Severity
Medium
Finding
Every CTA on the homepage ('Jetzt loslegen', 'Get started') routes to the contact form (/de-de/kontakt). There is no self-serve sandbox, no API key generation, no 'Try the API' flow, and no interactive demo. For a developer-first infrastructure product, the absence of any self-serve technical evaluation path is a significant friction point. The footer links to developer documentation (developer.lemon.markets) but this is not surfaced in the primary nav or the hero CTA — a developer landing on the homepage cannot get to the docs in one click from above the fold.
Recommendation
Add a 'View Documentation' or 'Explore the API' CTA alongside the primary contact CTA — ideally in the hero section and in the nav. If a sandbox environment exists, add 'Try the sandbox' as a secondary hero CTA. Developer-led evaluation is the primary sales motion for API infrastructure products: a developer who can call the sandbox API before speaking to sales is far more likely to become a champion internally than one who has to schedule a discovery call to see any technical detail.
UX
Single CTA Across All Entry Points — No Developer Path
Score
47
Severity
Medium
Finding
Every CTA on the homepage ('Jetzt loslegen', 'Get started') routes to the contact form (/de-de/kontakt). There is no self-serve sandbox, no API key generation, no 'Try the API' flow, and no interactive demo. For a developer-first infrastructure product, the absence of any self-serve technical evaluation path is a significant friction point. The footer links to developer documentation (developer.lemon.markets) but this is not surfaced in the primary nav or the hero CTA — a developer landing on the homepage cannot get to the docs in one click from above the fold.
Recommendation
Add a 'View Documentation' or 'Explore the API' CTA alongside the primary contact CTA — ideally in the hero section and in the nav. If a sandbox environment exists, add 'Try the sandbox' as a secondary hero CTA. Developer-led evaluation is the primary sales motion for API infrastructure products: a developer who can call the sandbox API before speaking to sales is far more likely to become a champion internally than one who has to schedule a discovery call to see any technical detail.
Freshness
No Blog, Changelog, or Product Updates Visible on Homepage
Score
48
Severity
Low
Finding
The homepage has no blog section, no recent news callout, no changelog link, and no 'what's new' strip. The About page references a news item from 'October 7, 2025' (likely the dwpbank acquisition completion announcement) but it is not surfaced on the homepage. The footer has no blog or news link. For a B2B infrastructure product, a visible product changelog and company news section on the homepage signals active development and institutional momentum — especially critical post-acquisition when partners may be wondering whether lemon.markets is still investing in the product.
Recommendation
Add a 'Recent updates' or 'In the news' section to the homepage featuring 2-3 recent items: the dwpbank acquisition completion, a recent product launch, and a partner announcement. Link to a /blog or /news page from the footer and nav. A static website with no freshness signals reads as abandoned infrastructure — the opposite of what a prospective B2B partner needs to see when evaluating a long-term API dependency.
Freshness
No Blog, Changelog, or Product Updates Visible on Homepage
Score
48
Severity
Low
Finding
The homepage has no blog section, no recent news callout, no changelog link, and no 'what's new' strip. The About page references a news item from 'October 7, 2025' (likely the dwpbank acquisition completion announcement) but it is not surfaced on the homepage. The footer has no blog or news link. For a B2B infrastructure product, a visible product changelog and company news section on the homepage signals active development and institutional momentum — especially critical post-acquisition when partners may be wondering whether lemon.markets is still investing in the product.
Recommendation
Add a 'Recent updates' or 'In the news' section to the homepage featuring 2-3 recent items: the dwpbank acquisition completion, a recent product launch, and a partner announcement. Link to a /blog or /news page from the footer and nav. A static website with no freshness signals reads as abandoned infrastructure — the opposite of what a prospective B2B partner needs to see when evaluating a long-term API dependency.
Copy
Operating Model Section — Bundled/Unbundled Terminology Unexplained
Score
52
Severity
Low
Finding
The 'Operating Model' section introduces 'Bundled' and 'Unbundled' configurations without a summary headline or comparison table that quickly communicates what each means for a non-technical buyer. The Bundled description is reasonably clear, but a product manager at a bank reading 'Sie möchten Ihre eigenen Geldkonten nutzen' (You want to use your own cash accounts) as the first line of the Unbundled description may not immediately map this to their own architecture. The section lacks a decision-aid: 'Which model is right for you?'
Recommendation
Add a one-line summary under each model name: 'Bundled — full-stack, we handle everything' and 'Unbundled — bring your own cash accounts, we handle securities.' Add a comparison table or a 'Which model fits you?' selector linking to use-case-specific pages. For a bank evaluating whether to use lemon.markets for a bolt-on investment product or a full rebuild, this distinction is the most operationally critical decision on the page — it should be immediately scannable, not require reading two dense paragraphs.
Copy
Operating Model Section — Bundled/Unbundled Terminology Unexplained
Score
52
Severity
Low
Finding
The 'Operating Model' section introduces 'Bundled' and 'Unbundled' configurations without a summary headline or comparison table that quickly communicates what each means for a non-technical buyer. The Bundled description is reasonably clear, but a product manager at a bank reading 'Sie möchten Ihre eigenen Geldkonten nutzen' (You want to use your own cash accounts) as the first line of the Unbundled description may not immediately map this to their own architecture. The section lacks a decision-aid: 'Which model is right for you?'
Recommendation
Add a one-line summary under each model name: 'Bundled — full-stack, we handle everything' and 'Unbundled — bring your own cash accounts, we handle securities.' Add a comparison table or a 'Which model fits you?' selector linking to use-case-specific pages. For a bank evaluating whether to use lemon.markets for a bolt-on investment product or a full rebuild, this distinction is the most operationally critical decision on the page — it should be immediately scannable, not require reading two dense paragraphs.
Performance
Prismic CMS Image Pipeline — 3840w Requests on Homepage
Score
58
Severity
Low
Finding
All product section images are requested at ?fit=max&w=3840 from the Prismic CDN (e.g., image-broker.png?auto=format,compress&fit=max&w=3840). Serving 3840px-wide images for section illustrations that render at 400-600px viewport width on desktop — and far smaller on mobile — is a significant bandwidth waste. Three full-page-width product images at 3840px each can easily add 1-3MB to the page weight, degrading LCP on mobile devices where the primary B2B SaaS evaluation increasingly occurs.
Recommendation
Update all Prismic image query parameters to use responsive sizing: request images at the actual rendered width plus 2x DPR maximum. For section illustrations rendering at ~600px on desktop, request at &w=1200 maximum (600px × 2x DPR). Use the Prismic imgix integration to serve WebP format automatically. This single change can reduce homepage image payload by 60-70% with no visual quality degradation.
Performance
Prismic CMS Image Pipeline — 3840w Requests on Homepage
Score
58
Severity
Low
Finding
All product section images are requested at ?fit=max&w=3840 from the Prismic CDN (e.g., image-broker.png?auto=format,compress&fit=max&w=3840). Serving 3840px-wide images for section illustrations that render at 400-600px viewport width on desktop — and far smaller on mobile — is a significant bandwidth waste. Three full-page-width product images at 3840px each can easily add 1-3MB to the page weight, degrading LCP on mobile devices where the primary B2B SaaS evaluation increasingly occurs.
Recommendation
Update all Prismic image query parameters to use responsive sizing: request images at the actual rendered width plus 2x DPR maximum. For section illustrations rendering at ~600px on desktop, request at &w=1200 maximum (600px × 2x DPR). Use the Prismic imgix integration to serve WebP format automatically. This single change can reduce homepage image payload by 60-70% with no visual quality degradation.
Brand
Logo Download Prompt — Visible to All Visitors
Score
35
Severity
Medium
Finding
The homepage renders a visible 'Download Logo Pack' banner with the lemon.markets logo displayed prominently at the very top of the page — above the nav. This is a brand asset download prompt (with a link to a .zip of logo files) that is apparently intended for press and partners but is being shown to every visitor including prospective customers. A bank product manager or fintech founder arriving on the homepage sees a logo download prompt as the first above-fold element before the nav, the hero, or any product messaging. This is a classic asset that belongs on the /media or /press page, not on the public homepage.
Recommendation
Remove the 'Download Logo Pack' prompt from the homepage immediately and relocate it to the /PR-Medien (PR/Media) page where it belongs. A homepage that greets prospective B2B customers with a brand asset download — typically relevant only to journalists and conference organisers — signals a page that was built for press rather than prospects. The hero headline 'Die Infrastruktur für Wertpapierhandel' should be the first thing a visitor sees, not a logo zip download.
Brand
Logo Download Prompt — Visible to All Visitors
Score
35
Severity
Medium
Finding
The homepage renders a visible 'Download Logo Pack' banner with the lemon.markets logo displayed prominently at the very top of the page — above the nav. This is a brand asset download prompt (with a link to a .zip of logo files) that is apparently intended for press and partners but is being shown to every visitor including prospective customers. A bank product manager or fintech founder arriving on the homepage sees a logo download prompt as the first above-fold element before the nav, the hero, or any product messaging. This is a classic asset that belongs on the /media or /press page, not on the public homepage.
Recommendation
Remove the 'Download Logo Pack' prompt from the homepage immediately and relocate it to the /PR-Medien (PR/Media) page where it belongs. A homepage that greets prospective B2B customers with a brand asset download — typically relevant only to journalists and conference organisers — signals a page that was built for press rather than prospects. The hero headline 'Die Infrastruktur für Wertpapierhandel' should be the first thing a visitor sees, not a logo zip download.