Website review, no card needed
commerzbank.pl website review
Visit site (opens in a new tab)Reviewed 19 November 202633 issues · 75 checks
This review found 33 issues worth fixing on commerzbank.pl, 16 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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
58FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Render-blocking requests
8.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.9 s.
Reduce unused CSS
4.7 s · 836 KiBAbout 836 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Reduce unused JavaScript
4.0 s · 719 KiBAbout 719 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Minify JavaScript
980 ms · 203 KiB203 KiB could be saved by minifying JavaScript.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Improve image delivery
150 ms · 144 KiB6 images could be 144 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 72 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 third-party service on the page
1 third-party service load with your homepage (commerzbank.com), adding 2 KiB and 1 ms of main-thread time.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 215 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.6 s
9.6 sThe first text or image appears after 9.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 12.4 s
12.4 sYour largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Cumulative Layout Shift: 0.871
0.871The layout shifts by 0.871 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 12 ms
12 msScripts block the page for only 12 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 35 requests
2.2 MBYour homepage downloads 2.2 MB in 35 requests on a phone: scripts 1,012 KiB (9), stylesheets 864 KiB (3) and images 290 KiB (10). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (194 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.
4 images below the first screen load straight away
4 images further down the page (194 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 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
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “mBank SA in Polen – polnische Tochtergesellschaft der Commerzbank Gruppe - Commerzbank”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.commerzbank.pl/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at commerzbank.pl/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
8 internal links, 14 external
The homepage links to 8 pages on commerzbank.pl and 14 external pages.
3 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Wir sind Ihr Partner für Corporate Banking in Polen. Profitieren Sie von unserer langjährigen Erfahrung und einem einhe…”.
One H1 headline
Your main headline reads: “mBank SA in Polen – polnische Tochtergesellschaft der Commerzbank Gruppe”.
Canonical URL set
The canonical URL is http://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/home/polen.html.
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.commerzbank.pl/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (255 words), so crawlers that don't run JavaScript still read it.
Other pages
5 linked pages hidden from search
https://www.commerzbank.pl/portal/en/cb/pl/firmenkunden/home/polen.html, https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/home/polen.html, https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/online-banking/redirect.html, https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/recht-1/disclaimer_17.html and https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/impressum/impressum.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/home/polen.html all use the title “mBank SA in Polen – polnische Tochtergesellschaft der Commerzbank Gru…”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/impressum/impressum.html has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/our_presence_your_benefits_pl.html and https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/sicherheit-12/security.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 pages slow to respond
https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/online-banking/redirect.html, https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/recht-1/disclaimer_17.html, https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/impressum/impressum.html and https://www.commerzbank.pl/portal/de/cb/pl/firmenkunden/footer/sicherheit-12/security.html took over 3 s to send their HTML from our server.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 7 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
12 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 253 words of copy
The homepage carries about 253 words of visible text.
1 checks passed
1 short form
A short form (0 fields at most) is right on the homepage.
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.
1 other company contacted
Loading the homepage contacts 1 host 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 commerzbank.pl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Joomla
- Hosting
- Commerzbank Aktiengesellschaft
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on commerzbank.pl, including 12 speed issues, 7 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.