Website review, no card needed

alobebe.com.br logo

alobebe.com.br website review

Visit site (opens in a new tab)Reviewed 6 November 202649 issues · 88 checks

This review found 49 issues worth fixing on alobebe.com.br, 16 of them high impact, across 88 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.7 s3.0 sMay 16Oct 313.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
112 ms96 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026100 ms
May 23, 202698 ms
May 30, 2026101 ms
Jun 6, 2026104 ms
Jun 13, 2026106 ms
Jun 20, 2026110 ms
Jun 27, 2026110 ms
Jul 4, 2026108 ms
Jul 11, 2026107 ms
Jul 18, 2026105 ms
Jul 25, 2026105 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026102 ms
Aug 29, 2026101 ms
Sep 5, 2026100 ms
Sep 12, 2026100 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 2026106 ms
Oct 10, 2026108 ms
Oct 17, 2026108 ms
Oct 24, 2026107 ms
Oct 31, 2026105 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 alobebe.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alobebe.com.br at 0.4 s0.4 s
  2. alobebe.com.br at 0.8 s0.8 s
  3. alobebe.com.br at 1.1 s1.1 s
  4. alobebe.com.br at 1.5 s1.5 s
  5. alobebe.com.br at 1.9 s1.9 s
  6. alobebe.com.br at 2.3 s2.3 s
  7. alobebe.com.br at 2.6 s2.6 s
  8. alobebe.com.br at 3.0 s3.0 s

Speed

13 to fix38
  • Reduce unused JavaScript

    1.8 s · 449 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 324 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (324 KiB).

  • Mobile performance score: 38

    38/100

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

  • vtexassets.com adds 884 ms

    884 ms

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

  • Google Tag Manager adds 594 ms

    594 ms

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

    450 ms · 52 KiB

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

  • Render-blocking requests

    400 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • Main-thread work: 3.6 s

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

  • Legacy JavaScript

    300 ms · 49 KiB

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

  • Improve image delivery

    285 KiB

    1 image could be 285 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 9 long tasks on the main thread

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

  • 1,654 HTML elements

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

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 24 ms

    24 ms

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

Core Web Vitals

10 to fix67
  • 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: 15.9 s

    15.9 s

    Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cadeirinha de Bebê”.

  • Time to Interactive: 16.8 s

    16.8 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 643 ms

    643 ms

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

  • Real-user CLS: 0.16

    0.16

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

  • Real-user TTFB: 838 ms

    838 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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.

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 144 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 144 requests on a phone: scripts 1.5 MB (74), fonts 463 KiB (3) and images 381 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.74 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8387
  • 3 buttons without a name

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

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • 4 tap targets too small

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

  • 3 text elements with low contrast

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

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

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

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

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

SEO

5 to fixGoogle 10071
  • No H1 headline

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

  • Title is short (8 characters)

    Your title is only 8 characters: “Alô Bebê”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (171 characters)

    Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (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 X (Twitter) card tag

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

  • 15 internal links, 3 external

    The homepage links to 15 pages on alobebe.com.br and 3 external pages.

3 checks passed
  • Canonical URL set

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

  • 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.alobebe.com.br/sitemap.xml.

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.alobebe.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
  • 2 pages share a meta description

    https://www.alobebe.com.br/wishlist and https://www.alobebe.com.br/ofertas use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.alobebe.com.br/wishlist has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.alobebe.com.br/wishlist 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.

  • 9 pages slow to respond

    https://www.alobebe.com.br/kit-berco/kit-de-berco-e-protetor, https://www.alobebe.com.br/quarto-e-enxoval, https://www.alobebe.com.br/alimentacao, https://www.alobebe.com.br/banho-e-higiene, https://www.alobebe.com.br/saude and https://www.alobebe.com.br/brinquedos and 3 others took over 3 s to send their HTML from our server.

  • 13 internal pages checked

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

6 checks passed
  • Linked pages load

    12 pages of 13 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 12 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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 119 words

    The homepage has only about 119 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 and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 2 of them by other companies (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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 alobebe.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
React
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 49 issues on alobebe.com.br, including 23 speed issues, 5 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