Website review, no card needed

bnsir.com.br logo

bnsir.com.br website review

Visit site (opens in a new tab)Reviewed 26 October 202655 issues · 94 checks

This review found 55 issues worth fixing on bnsir.com.br, 21 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.3 s3.1 sMay 2Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20264.1 s
Aug 1, 20264.9 s
Aug 8, 20265.0 s
Aug 15, 20265.0 s
Aug 22, 20264.5 s
Aug 29, 20264.0 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
372 ms312 msMay 2Oct 17330 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026347 ms
May 9, 2026353 ms
May 16, 2026346 ms
May 23, 2026330 ms
May 30, 2026319 ms
Jun 6, 2026330 ms
Jun 13, 2026335 ms
Jun 20, 2026348 ms
Jun 27, 2026355 ms
Jul 4, 2026363 ms
Jul 11, 2026364 ms
Jul 18, 2026363 ms
Jul 25, 2026363 ms
Aug 1, 2026347 ms
Aug 8, 2026349 ms
Aug 15, 2026353 ms
Aug 22, 2026355 ms
Aug 29, 2026363 ms
Sep 5, 2026365 ms
Sep 12, 2026363 ms
Sep 19, 2026359 ms
Sep 26, 2026350 ms
Oct 3, 2026340 ms
Oct 10, 2026335 ms
Oct 17, 2026330 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

Full-page screenshot of bnsir.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bnsir.com.br at 1.5 s1.5 s
  2. bnsir.com.br at 3.1 s3.1 s
  3. bnsir.com.br at 4.6 s4.6 s
  4. bnsir.com.br at 6.1 s6.1 s
  5. bnsir.com.br at 7.7 s7.7 s
  6. bnsir.com.br at 9.2 s9.2 s
  7. bnsir.com.br at 10.8 s10.8 s
  8. bnsir.com.br at 12.3 s12.3 s

Speed

14 to fix22
  • Reduce unused JavaScript

    5.2 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Use efficient cache lifetimes

    2.1 s · 2.0 MB

    22 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • 30,174 HTML elements

    The page has 30,174 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • zohocdn.com adds 2.0 s

    2.0 s

    zohocdn.com costs a phone 2.0 s of main-thread work and 40 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.4 s

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Main-thread work: 12.1 s

    A phone's processor spends 12.1 s on main-thread work while loading, 7.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 22

    22/100

    Your mobile performance score is 22 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (zohocdn.com, Google Tag Manager and PageSense and others), adding 1.0 MB and 3.5 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

  • Reduce unused CSS

    600 ms · 110 KiB

    About 110 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.

  • Google Tag Manager adds 542 ms

    542 ms

    Google Tag Manager costs a phone 542 ms of main-thread work and 498 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.

  • Improve image delivery

    150 ms · 348 KiB

    6 images could be 348 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.

  • PageSense adds 484 ms

    484 ms

    PageSense costs a phone 484 ms of main-thread work and 80 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.

  • Facebook adds 250 ms

    250 ms

    Facebook costs a phone 250 ms of main-thread work and 224 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.

  • Legacy JavaScript

    150 ms · 62 KiB

    Polyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 63 ms

    63 ms

    Your server sent the HTML in 63 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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: 22.0 s

    22.0 s

    Your largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Apartamento”.

  • Time to Interactive: 25.5 s

    25.5 s

    The page becomes fully interactive after 25.5 s. Good is under 3.8 s.

  • Speed Index: 13.7 s

    13.7 s

    Visually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 3.2 s

    3.2 s

    Scripts block taps and scrolling for 3.2 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 398 ms

    398 ms

    Real visitors wait 398 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • First Contentful Paint: 2.9 s

    2.9 s

    The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.193

    0.193

    The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 347 ms to 330 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 534 ms

    534 ms

    Real visitors wait 534 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

2 to fix60
  • Page weight: 4.3 MB in 108 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 108 requests on a phone: scripts 2.2 MB (32), images 1.8 MB (18) and stylesheets 129 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    21 KiB

    1 image is downloaded at several times the size a phone draws it, for example sothesby.webp at 1,280 px wide, shown at 351 px. Resized copies would save about 21 KiB.

  • About 1.2 g of CO₂ per visit

    1.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.7 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

10 to fixGoogle 7586
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 58 text elements with low contrast

    58 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <svg> elements with an img or image role must have alternative text (21 elements)

    <svg> elements with an img or image role must have alternative text: 21 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (28 elements)

    All page content should be contained by landmarks: 28 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 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 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 8569
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Bossa Nova Sotheby’s International Realty - Imóveis de alto padrão”.

  • 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.bnsir.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • Only 4 internal links

    The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 5 links crawlers can't follow

    5 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 incomplete here.

3 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Imobiliária de Alto Padrão, focada nos melhores bairros de São Paulo, Rio de Janeiro, Litoral e no Campo. Confira també…”.

  • Canonical URL set

    The canonical URL is https://www.bnsir.com.br/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    51%

    The HTML your server sends has 254 of the 497 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.bnsir.com.br/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
  • 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.

Other pages

2 to fix93
  • 3 pages share a meta description

    https://www.bnsir.com.br/politica-de-privacidade, https://www.bnsir.com.br/sobre-nos/a-bossa-nova and https://www.bnsir.com.br/para-quem-anuncia/seu-imovel-na-bnsir use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.bnsir.com.br/politica-de-privacidade has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.bnsir.com.br/sobre-nos/a-bossa-nova 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.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 3 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 a meta description

    All 3 pages that loaded have a meta description.

  • 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 3 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6988
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.bnsir.com.br' has been blo…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 497 words of copy

    The homepage carries about 497 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 bnsir.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
Nuxt
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 55 issues on bnsir.com.br, including 24 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25