Website review, no card needed

mundoverde.com.br logo

mundoverde.com.br website review

Visit site (opens in a new tab)Reviewed 3 November 202633 issues · 78 checks

This review found 33 issues worth fixing on mundoverde.com.br, 12 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
4.2 s3.6 sMay 16Oct 313.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20263.8 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.0 s
Oct 31, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
508 ms363 msMay 16Oct 31422 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026387 ms
May 23, 2026382 ms
May 30, 2026391 ms
Jun 6, 2026390 ms
Jun 13, 2026390 ms
Jun 20, 2026389 ms
Jun 27, 2026383 ms
Jul 4, 2026380 ms
Jul 11, 2026389 ms
Jul 18, 2026410 ms
Jul 25, 2026422 ms
Aug 1, 2026425 ms
Aug 8, 2026419 ms
Aug 15, 2026408 ms
Aug 22, 2026387 ms
Aug 29, 2026389 ms
Sep 5, 2026417 ms
Sep 12, 2026429 ms
Sep 19, 2026441 ms
Sep 26, 2026455 ms
Oct 3, 2026465 ms
Oct 10, 2026481 ms
Oct 17, 2026491 ms
Oct 24, 2026483 ms
Oct 31, 2026422 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 mundoverde.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix61
  • Improve image delivery

    2.3 s · 1.6 MB

    26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • 6,230 HTML elements

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

  • Main-thread work: 5.2 s

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

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

  • 3 third-party services on the page

    3 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Google Analytics), adding 2.8 MB and 602 ms of main-thread time.

  • cloudfront.net adds 380 ms

    380 ms

    cloudfront.net costs a phone 380 ms of main-thread work and 2.6 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.

  • Use efficient cache lifetimes

    300 ms · 266 KiB

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

  • 15 long tasks on the main thread

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

  • Reduce unused JavaScript

    163 KiB

    About 163 KiB of JavaScript is downloaded but never used on this page.

  • Minify JavaScript

    9 KiB

    9 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: 35 ms

    35 ms

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

Core Web Vitals

10 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 INP: 584 ms

    584 ms

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

  • Real-user CLS: 0.40

    0.40

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Veja mais: Saúde do Homem”.

  • Total Blocking Time: 847 ms

    847 ms

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 2 images without width and height

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix69
  • Page weight: 2.9 MB in 69 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 69 requests on a phone: images 2.2 MB (55), scripts 458 KiB (7) and fonts 124 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    150_banner639292011049195819.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images far larger than shown

    74 KiB

    4 images are downloaded at several times the size a phone draws them, for example 26_banner639264425855540239.webp at 500 px wide, shown at 140 px. Resized copies would save about 74 KiB.

  • 1 image in older formats

    1 image (45 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.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

Accessibility

3 to fixGoogle 9695
  • 51 text elements with low contrast

    51 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 (20 elements)

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

  • 3 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 94 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • 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 X (Twitter) card tag

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

  • 318 internal links, 11 external

    The homepage links to 318 pages on mundoverde.com.br and 11 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Compre suplementos, cosméticos, vitaminas e alimentos no Mundo Verde, a maior rede de lojas no Brasil! Para uma vida co…”.

  • One H1 headline

    Your main headline reads: “Mundo Verde”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Mundo Verde - A maior rede de produtos saudáveis do Brasil”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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.mundoverde.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.

2 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 (1,887 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 8 pages without an H1

    https://www.mundoverde.com.br/alimentos, https://www.mundoverde.com.br/alimentos/snacks, https://www.mundoverde.com.br/alimentos/snacks/snacks-doces, https://www.mundoverde.com.br/alimentos/snacks/snacks-salgados, https://www.mundoverde.com.br/alimentos/snacks/pipocas and https://www.mundoverde.com.br/alimentos/snacks/biscoitos and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.mundoverde.com.br/alimentos, https://www.mundoverde.com.br/alimentos/snacks/snacks-doces, https://www.mundoverde.com.br/alimentos/snacks/snacks-salgados, https://www.mundoverde.com.br/alimentos/snacks/biscoitos and https://www.mundoverde.com.br/alimentos/snacks/bolos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    82 of 83 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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 1,438 words of copy

    The homepage carries about 1,438 words of visible text.

2 checks passed
  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 mundoverde.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Azure

Company

Founded
1987
Headquarters
Petrópolis

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 mundoverde.com.br, including 18 speed issues, 2 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