Programmable

Website review, no card needed

kangu.com.br logo

kangu.com.br website review

Visit site (opens in a new tab)Reviewed 1 November 202628 issues · 64 checks

This review found 28 issues worth fixing on kangu.com.br, 10 of them high impact, across 64 checks. The most urgent: render-blocking requests. 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

Site score

85B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.3 s2.2 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
189 ms139 msMay 9Oct 24151 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026176 ms
May 16, 2026177 ms
May 23, 2026178 ms
May 30, 2026180 ms
Jun 6, 2026183 ms
Jun 13, 2026182 ms
Jun 20, 2026181 ms
Jun 27, 2026176 ms
Jul 4, 2026167 ms
Jul 11, 2026158 ms
Jul 18, 2026149 ms
Jul 25, 2026146 ms
Aug 1, 2026145 ms
Aug 8, 2026145 ms
Aug 15, 2026145 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026146 ms
Sep 12, 2026149 ms
Sep 19, 2026150 ms
Sep 26, 2026151 ms
Oct 3, 2026150 ms
Oct 10, 2026151 ms
Oct 17, 2026151 ms
Oct 24, 2026151 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

www.mercadolivre.com.br (opens in a new tab)
Full-page screenshot of kangu.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix97

  • Render-blocking requests

    1.1 s

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

  • Reduce unused CSS

    300 ms · 72 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (mlstatic.com, mercadolibre.com and meli.com), adding 265 KiB and 62 ms of main-thread time.

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

3 checks passed

  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 129 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100

  • 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 FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

9 checks passed

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 117 ms

    117 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Speed Index: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “CNPJ n.º 03.007.331/0001-41 / Av. das Nações Unidas, nº 3.0…”.

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100

  • About 0.08 g of CO₂ per visit

    0.08 g

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

1 checks passed

  • Page weight: 300 KiB in 33 requests

    300 KiB

    Your homepage downloads 300 KiB in 33 requests on a phone: scripts 136 KiB (16), stylesheets 63 KiB (2) and fonts 44 KiB (3). That is a lean page.

Accessibility

3 to fixGoogle 9294

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

  • 3 tap targets too small

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

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

1 checks passed

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 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 9265

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (11 characters)

    Your title is only 11 characters: “Ajuda Kangu”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 12 internal links, 3 external

    The homepage links to 12 pages on kangu.com.br and 3 external pages.

2 checks passed

  • Canonical URL set

    The canonical URL is https://www.mercadolivre.com.br/ajuda/38279.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

2 to fix37

  • robots.txt blocks 4 AI answer engine crawlers

    4 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

5 to fix70

  • 1 linked page hidden from search

    https://www.mercadolivre.com.br/ajuda/991 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.mercadolivre.com.br/l/promocoes and https://www.mercadolivre.com.br/l/afiliados-home all use the title “Mercado Libre”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.mercadolivre.com.br/acessibilidade/feedback, https://www.mercadolivre.com.br/ajuda, https://www.mercadolivre.com.br/l/promocoes, https://www.mercadolivre.com.br/privacidade, https://www.mercadolivre.com.br/acessibilidade and https://www.mercadolivre.com.br/l/afiliados-home have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.mercadolivre.com.br/ajuda/23303, whose canonical is https://www.mercadolivre.com.br/ajuda/informacoes-sobre-seguros_23303. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.mercadolivre.com.br/ajuda, https://www.mercadolivre.com.br/ajuda/991, https://www.mercadolivre.com.br/l/promocoes, https://www.mercadolivre.com.br/privacidade, https://www.mercadolivre.com.br/ajuda/23303 and https://www.mercadolivre.com.br/l/afiliados-home have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.mercadolivre.com.br/acessibilidade/feedback, https://www.mercadolivre.com.br/ajuda, https://www.mercadolivre.com.br/l/promocoes, https://www.mercadolivre.com.br/ajuda/23303 and https://www.mercadolivre.com.br/l/afiliados-home 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.

  • 9 internal pages checked

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

2 checks passed

  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 9 small tap targets

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

2 checks passed

  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 130 words

    The homepage has only about 130 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.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

  • 7 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on kangu.com.br, including 6 speed issues, 5 SEO issues and 6 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