Website review, no card needed

mambo.com.br logo

mambo.com.br website review

Visit site (opens in a new tab)Reviewed 20 November 202651 issues · 89 checks

This review found 51 issues worth fixing on mambo.com.br, 22 of them high impact, across 89 checks. The most urgent: vtexassets.com adds 1.1 s. 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.0 s2.5 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20262.9 s
Nov 7, 20262.9 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
229 ms161 msMay 30Nov 14215 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026169 ms
Jun 6, 2026174 ms
Jun 13, 2026180 ms
Jun 20, 2026186 ms
Jun 27, 2026184 ms
Jul 4, 2026184 ms
Jul 11, 2026185 ms
Jul 18, 2026182 ms
Jul 25, 2026181 ms
Aug 1, 2026183 ms
Aug 8, 2026188 ms
Aug 15, 2026195 ms
Aug 22, 2026202 ms
Aug 29, 2026202 ms
Sep 5, 2026205 ms
Sep 12, 2026205 ms
Sep 19, 2026208 ms
Sep 26, 2026218 ms
Oct 3, 2026221 ms
Oct 10, 2026220 ms
Oct 17, 2026220 ms
Oct 24, 2026219 ms
Oct 31, 2026215 ms
Nov 7, 2026217 ms
Nov 14, 2026215 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 mambo.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mambo.com.br at 0.8 s0.8 s
  2. mambo.com.br at 1.5 s1.5 s
  3. mambo.com.br at 2.3 s2.3 s
  4. mambo.com.br at 3.1 s3.1 s
  5. mambo.com.br at 3.8 s3.8 s
  6. mambo.com.br at 4.6 s4.6 s
  7. mambo.com.br at 5.4 s5.4 s
  8. mambo.com.br at 6.1 s6.1 s

Speed

11 to fix39
  • vtexassets.com adds 1.1 s

    1.1 s

    vtexassets.com costs a phone 1.1 s of main-thread work and 1.3 MB 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.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 1.5 MB 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.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 6.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google CDN and Google Tag Manager and others), adding 3.6 MB and 3.3 s of main-thread time.

  • Reduce unused JavaScript

    1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    450 ms · 117 KiB

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

  • Google Tag Manager adds 497 ms

    497 ms

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

  • 20 long tasks on the main thread

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

  • Facebook adds 334 ms

    334 ms

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

  • Use efficient cache lifetimes

    344 KiB

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

  • Improve image delivery

    150 ms · 131 KiB

    4 images could be 131 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.

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    15 KiB

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

1 checks passed
  • Server response: 31 ms

    31 ms

    Your server sent the HTML in 31 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.

  • Real-user CLS: 0.49

    0.49

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

  • Time to Interactive: 26.2 s

    26.2 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Começou o Esquenta Black”.

  • Real-user INP: 204 ms

    204 ms

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • Cumulative Layout Shift: 0.214

    0.214

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

  • 3 images without width and height

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

4 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 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: 772 ms

    772 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

4 to fix33
  • Page weight: 4.6 MB in 151 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 151 requests on a phone: scripts 3.1 MB (85), other files 726 KiB (33) and HTML 247 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    687 KiB

    4 images are downloaded at several times the size a phone draws them, for example 235899.png at 1,200 px wide, shown at 168 px. Resized copies would save about 687 KiB.

  • 7 images below the first screen load straight away

    7 images further down the page (819 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (666 KiB) 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.

  • About 1.3 g of CO₂ per visit

    1.30 g

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

Accessibility

11 to fixGoogle 8985
  • 8 buttons without a name

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

  • 80 text elements with low contrast

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

  • 43 tap targets too small

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 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 (29 elements)

    All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 5 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails 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).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • 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 (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.

  • 17 internal links, 1 external

    The homepage links to 17 pages on mambo.com.br and 1 external page.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Compre no Supermercados Mambo produtos e ingredientes sempre frescos e de alta qualidade. Descubra ofertas irresistívei…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Mambo | Supermercado Online, Hortifruti e Açougue em São Paulo”.

  • Canonical URL set

    The canonical URL is https://www.mambo.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.mambo.com.br/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    5%

    A phone browser shows 454 words, but the HTML your server sends has only 23. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

3 to fix63
  • 10 linked pages are broken

    Your homepage links to https://www.mambo.com.br/881, https://www.mambo.com.br/162, https://www.mambo.com.br/1671, https://www.mambo.com.br/2213, https://www.mambo.com.br/686 and https://www.mambo.com.br/2552 and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    / and https://www.mambo.com.br/lista-rapida all use the title “Mambo | Supermercado Online, Hortifruti e Açougue em São Paulo”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without an H1

    https://www.mambo.com.br/lista-rapida, https://www.mambo.com.br/mambo/momento-mambo and https://www.mambo.com.br/mambo/churrasco have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.mambo.com.br/lista-rapida, https://www.mambo.com.br/mambo/momento-mambo, https://www.mambo.com.br/mambo/churrasco and https://www.mambo.com.br/azeite-portugues-extra-virgem-classico-oliveira-da-serra-500ml/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.

  • 3 pages slow to respond

    https://www.mambo.com.br/mambo/churrasco, https://www.mambo.com.br/azeite-portugues-extra-virgem-classico-oliveira-da-serra-500ml/p and https://www.mambo.com.br/cerveja-lager-puro-malte-ultimate-sem-gluten-heineken-lata-350ml/p took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 47 small tap targets

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

  • 4 JavaScript errors while loading

    4 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

4 to fix40
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 454 words of copy

    The homepage carries about 454 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, 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.

  • 20 cookies set on arrival

    20

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 mambo.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 51 issues on mambo.com.br, including 21 speed issues, 3 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