Website review, no card needed
bancobari.com.br website review
Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 80 checks
This review found 33 issues worth fixing on bancobari.com.br, 15 of them high impact, across 80 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
73CClosest 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.1 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.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 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 | 230 ms |
| May 16, 2026 | 240 ms |
| May 23, 2026 | 254 ms |
| May 30, 2026 | 261 ms |
| Jun 6, 2026 | 264 ms |
| Jun 13, 2026 | 277 ms |
| Jun 20, 2026 | 279 ms |
| Jun 27, 2026 | 283 ms |
| Jul 4, 2026 | 284 ms |
| Jul 11, 2026 | 267 ms |
| Jul 18, 2026 | 253 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 242 ms |
| Aug 15, 2026 | 240 ms |
| Aug 22, 2026 | 238 ms |
| Aug 29, 2026 | 237 ms |
| Sep 5, 2026 | 235 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 222 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 222 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 231 ms |
| Oct 24, 2026 | 232 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Reduce unused JavaScript
33.2 s · 6.5 MBAbout 6.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 33.2 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
750 ms · 107 KiB1 image could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 424 ms. During a long task the page ignores taps.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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: 28 ms
28 msYour server sent the HTML in 28 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.
Largest Contentful Paint: 40.0 s
40.0 sYour largest element takes 40.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 40.2 s
40.2 sThe page becomes fully interactive after 40.2 s. Good is under 3.8 s.
Speed Index: 13.0 s
13.0 sVisually, the page fills in at 13.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 990 ms
990 msScripts block taps and scrolling for 990 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 226 ms
226 msReal visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 974 ms
974 msReal visitors wait 974 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 230 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 23 requests
7.5 MBYour homepage downloads 7.5 MB in 23 requests on a phone: scripts 7.1 MB (19), HTML 190 KiB (1) and images 135 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
68 KiB1 image is downloaded at several times the size a phone draws it, for example fundo-home-mobile.webp at 1,656 px wide, shown at 390 px. Resized copies would save about 68 KiB.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 4 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Banco Bari | Empréstimo com Juros Baixos, Investimentos e mais | Banco Bari”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
13 internal links, 1 external
The homepage links to 13 pages on bancobari.com.br and 1 external page.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Encontre empréstimo com garantia de imóvel, crédito consignado e as melhores opções de renda fixa no Banco Bari. Sua vi…”.
One H1 headline
Your main headline reads: “Especialistas em Empréstimo com Garantia de Imóvel”.
Canonical URL set
The canonical URL is https://bancobari.com.br/.
Structured data in place
Structured data found: BankOrCreditUnion, FAQPage, WebPage and WebSite.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://bancobari.com.br/sitemap-index.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.
3 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 (498 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bancobari.com.br/llms.txt (5 KiB, 18 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://bancobari.com.br/simulador-emprestimo-com-garantia has no <title>, so Google invents the link text in results.
1 page without a meta description
https://bancobari.com.br/simulador-emprestimo-com-garantia has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://bancobari.com.br/simulador-emprestimo-com-garantia and https://bancobari.com.br/investimentos-renda-fixa have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://bancobari.com.br/simulador-emprestimo-com-garantia has 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.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 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.
Best practices
12 small tap targets
12 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 417 words of copy
The homepage carries about 417 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Hotjar.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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 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 bancobari.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Hotjar
- Hosting
- CloudFront
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 bancobari.com.br, including 12 speed issues, 3 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.