Website review, no card needed

bebece.com.br logo

bebece.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202653 issues · 87 checks

This review found 53 issues worth fixing on bebece.com.br, 18 of them high impact, across 87 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
3.8 s3.3 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.7 s
May 16, 20263.7 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
356 ms312 msMay 9Oct 24320 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026340 ms
May 16, 2026336 ms
May 23, 2026329 ms
May 30, 2026325 ms
Jun 6, 2026325 ms
Jun 13, 2026331 ms
Jun 20, 2026336 ms
Jun 27, 2026336 ms
Jul 4, 2026340 ms
Jul 11, 2026336 ms
Jul 18, 2026336 ms
Jul 25, 2026341 ms
Aug 1, 2026340 ms
Aug 8, 2026342 ms
Aug 15, 2026344 ms
Aug 22, 2026346 ms
Aug 29, 2026351 ms
Sep 5, 2026348 ms
Sep 12, 2026340 ms
Sep 19, 2026331 ms
Sep 26, 2026322 ms
Oct 3, 2026319 ms
Oct 10, 2026317 ms
Oct 17, 2026319 ms
Oct 24, 2026320 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 bebece.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bebece.com.br at 0.9 s0.9 s
  2. bebece.com.br at 1.8 s1.8 s
  3. bebece.com.br at 2.8 s2.8 s
  4. bebece.com.br at 3.7 s3.7 s
  5. bebece.com.br at 4.6 s4.6 s
  6. bebece.com.br at 5.5 s5.5 s
  7. bebece.com.br at 6.4 s6.4 s
  8. bebece.com.br at 7.4 s7.4 s

Speed

14 to fix22
  • Reduce unused JavaScript

    5.7 s · 984 KiB

    About 984 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

  • Use efficient cache lifetimes

    5.4 s · 1.1 MB

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

  • Render-blocking requests

    1.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

  • Mobile performance score: 22

    22/100

    Your mobile performance score is 22. 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 (vtexassets.com, Google Tag Manager and Facebook and others), adding 3.7 MB and 1.6 s of main-thread time.

  • Improve image delivery

    900 ms · 270 KiB

    7 images could be 270 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • vtexassets.com adds 494 ms

    494 ms

    vtexassets.com costs a phone 494 ms of main-thread work and 1.9 MB 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

    450 ms · 101 KiB

    About 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 57 KiB

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

  • Google Tag Manager adds 420 ms

    420 ms

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

  • Main-thread work: 3.9 s

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

  • Facebook adds 263 ms

    263 ms

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

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.

  • Google CDN adds 63 ms

    63 ms

    Google CDN costs a phone 63 ms of main-thread work and 352 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.

  • Minify JavaScript

    150 ms · 33 KiB

    33 KiB could be saved by minifying JavaScript.

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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 39 ms

    39 ms

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

Core Web Vitals

13 to fix0
  • 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 CLS: 0.75

    0.75

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

  • Largest Contentful Paint: 26.2 s

    26.2 s

    Your largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “O melhor do verão”.

  • Time to Interactive: 26.2 s

    26.2 s

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

  • Speed Index: 11.4 s

    11.4 s

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

  • Cumulative Layout Shift: 0.725

    0.725

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

  • Total Blocking Time: 704 ms

    704 ms

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 274 ms

    274 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 12 images without width and height

    12 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-24, real Chrome visitors' tap response (inp) went from 340 ms to 320 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-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 168 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 168 requests on a phone: scripts 2.8 MB (82), images 637 KiB (22) and stylesheets 192 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    172 KiB

    1 image is downloaded at several times the size a phone draws it, for example e5b40400-6776-46e7-a2bd-12285b373bf7___c8bab360bbdf428b12e65 at 1,562 px wide, shown at 390 px. Resized copies would save about 172 KiB.

  • 1 image in older formats

    1 image (392 KiB) is 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 (119 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8691
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • 7 text elements with low contrast

    7 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 (3 elements)

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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 61 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.lojavazia.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 94 internal links, 1 external

    The homepage links to 94 pages on bebece.com.br and 1 external page.

4 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Sapatos femininos com os melhores preços você encontra na Bebecê Calçados. São diversos modelos de sandálias, scarpins,…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Bebecê Calçados | Calçados Femininos com moda e conforto”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix83
  • 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.bebece.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

5 to fix69
  • 1 page without a title

    https://www.bebece.com.br/tamanco-translucido-thong-sandal-metalizado/p has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.bebece.com.br/tamanco-translucido-thong-sandal-metalizado/p has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.bebece.com.br/bmais, https://www.bebece.com.br/sol-de-dentro, https://www.bebece.com.br/couro, https://www.bebece.com.br/lancamentos, https://www.bebece.com.br/outlet and https://www.bebece.com.br/wishlist use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bebece.com.br/couro, whose canonical is https://www.bebece.com.br/calcados-femininos-em-couro. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.bebece.com.br/bmais and https://www.bebece.com.br/tamanco-translucido-thong-sandal-metalizado/p have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.bebece.com.br/sol-de-dentro, https://www.bebece.com.br/couro, https://www.bebece.com.br/wishlist and https://www.bebece.com.br/tamanco-bebece-salto-bloco-tira-com-enfeite/p 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.bebece.com.br/scarpin-classico-com-biqueira-metalizada-986836/p, https://www.bebece.com.br/scarpin-slingback-elegante-com-maxi-fivela-982918/p, https://www.bebece.com.br/scarpin-semiaberto-com-biqueira-metalizada-984923/p and https://www.bebece.com.br/tamanco-translucido-thong-sandal-metalizado/p took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 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.

  • 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

2 to fixGoogle 9687
  • 20 small tap targets

    20 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • Only about 101 words

    The homepage has only about 101 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 31 cookies set on arrival

    31

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

  • 43 other companies contacted

    Loading the homepage contacts 43 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 bebece.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

Analytics
Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on bebece.com.br, including 27 speed issues, 4 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

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