Website review, no card needed
bancrea.com website review
Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 77 checks
This review found 39 issues worth fixing on bancrea.com, 17 of them high impact, across 77 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 4.8 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 5.6 s |
| Aug 29, 2026 | 7.0 s |
| Sep 5, 2026 | 7.2 s |
| Sep 12, 2026 | 7.0 s |
| Sep 19, 2026 | 6.9 s |
| Sep 26, 2026 | 6.4 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 119 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 122 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
Render-blocking requests
2.1 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
950 ms · 194 KiB2 files are served with short cache lifetimes, so returning visitors download them again (194 KiB).
Improve image delivery
150 ms · 869 KiB6 images could be 869 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.
Reduce unused JavaScript
620 ms · 215 KiBAbout 215 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.
Reduce unused CSS
600 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
3 third-party services on the page
3 third-party services load with your homepage (Google Maps, jQuery CDN and Google Fonts), adding 212 KiB and 145 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 119 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 730 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.34
0.34For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.385
0.385The layout shifts by 0.385 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 119 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.9 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 81 ms
81 msScripts block the page for only 81 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 93 requests
2.9 MBYour homepage downloads 2.9 MB in 93 requests on a phone: images 1.8 MB (22), fonts 499 KiB (6) and scripts 460 KiB (27). Under 2 MB keeps phones on slow connections fast.
10 images in older formats
10 images (1.3 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
unnamed-768x768.jpg 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 (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.3 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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail 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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 robots.txt
There is no robots.txt at bancrea.com/robots.txt, the first file search crawlers ask for.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
162 internal links, 22 external
The homepage links to 162 pages on bancrea.com and 22 external pages.
3 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “Bancrea – Institución de Banca Múltiple”.
Canonical URL set
The canonical URL is https://bancrea.com/.
XML sitemap found
Your XML sitemap is reachable at https://bancrea.com/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://bancrea.com/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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,058 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://bancrea.com/cuenta-soy-bancrea, https://bancrea.com/cuenta-soy-bancrea-empresarial, https://bancrea.com/soy-bancrea-dolares, https://bancrea.com/soy-bancrea-dolares-con-intereses-para-persona-moral, https://bancrea.com/pagare-bancrea-empresas and https://bancrea.com/cede-bancrea-empresas and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://bancrea.com/cuenta-soy-bancrea, https://bancrea.com/cuenta-soy-bancrea-empresarial, https://bancrea.com/soy-bancrea-dolares, https://bancrea.com/soy-bancrea-dolares-con-intereses-para-persona-moral, https://bancrea.com/pagare-bancrea-empresas and https://bancrea.com/cede-bancrea-empresas and 9 others 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 45 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “google is not defined”.
2 checks passed
Tap targets are thumb-sized
10 of 12 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 278 words of copy
The homepage carries about 278 words of visible text.
Privacy and tracking
17 cookies set on arrival
17Opening the homepage sets 17 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 bancrea.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Radware
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bancrea.com, including 16 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.