Website review, no card needed
cbnk.es website review
Visit site (opens in a new tab)Reviewed 26 October 202649 issues · 92 checks
This review found 49 issues worth fixing on cbnk.es, 21 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 151 ms |
| May 16, 2026 | 157 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 174 ms |
| Jul 11, 2026 | 167 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 168 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 158 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 165 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 158 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 147 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
Use efficient cache lifetimes
2.5 s · 8.4 MB43 files are served with short cache lifetimes, so returning visitors download them again (8.4 MB).
Reduce unused JavaScript
3.3 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,313 HTML elements
The page has 3,313 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
2.3 MB4 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Cookiebot and others), adding 2.0 MB and 1.7 s of main-thread time.
Google Tag Manager adds 933 ms
933 msGoogle Tag Manager costs a phone 933 ms of main-thread work and 817 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.
Reduce unused CSS
750 ms · 187 KiBAbout 187 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
YouTube adds 608 ms
608 msYouTube costs a phone 608 ms of main-thread work and 964 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 294 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.107
0.107The layout shifts by 0.107 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 151 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 607 ms
607 msReal visitors wait 607 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 11.7 MB in 78 requests
11.7 MBYour homepage downloads 11.7 MB in 78 requests on a phone: images 8.9 MB (35), scripts 2.2 MB (16) and fonts 315 KiB (7). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 6.0 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
821 KiB2 images are downloaded at several times the size a phone draws them, for example modulo web.png at 2,453 px wide, shown at 390 px. Resized copies would save about 821 KiB.
6 images in older formats
6 images (1.7 MB) 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.
An image on the first screen is lazy-loaded
Group 1000004777.png 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 below the first screen load straight away
1 image further down the page (164 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.3 g of CO₂ per visit
3.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.31 g of CO₂e: 396.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid names (4 elements)
ARIA attributes must conform to valid names: 4 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
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.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h3 and h1 → h3), 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. (2 elements).
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
46 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: 46 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “CBNK – Personas”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (46 characters)
Your meta description is only 46 characters: “CBNK - La banca para los colectivos esenciales”. 70 to 160 characters is enough to sell the click.
3 H1 headlines
There are 3 <h1> headlines (“CBNK - La banca para los colectivos esenciales”, “El depósito que necesitan tus ahorros” and “Iniciativa pionera para apoyar a mujeres emprende…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
251 internal links, 10 external
The homepage links to 251 pages on cbnk.es and 10 external pages.
3 checks passed
Canonical URL set
The canonical URL is http://cbnk.es/personas.
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.cbnk.es/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://cbnk.es/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 (2,837 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://cbnk.es/personas and / all use the title “CBNK – Personas”. 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://cbnk.es/personas/programa-mas-cbnk, https://cbnk.es/personas/depositos/Deposito-con-GDC and https://cbnk.es/personas/depositos/Deposito-con-fi have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://cbnk.es/personas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://cbnk.es/personas/programa-mas-cbnk, https://cbnk.es/personas/depositos/Deposito-con-GDC and https://cbnk.es/personas/depositos/Deposito-con-fi have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
80 of 95 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: 17 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 3,186 words of copy
The homepage carries about 3,186 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 cbnk.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on cbnk.es, including 19 speed issues, 5 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.