Website review, no card needed

mrcat.com.br logo

mrcat.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202650 issues · 87 checks

This review found 50 issues worth fixing on mrcat.com.br, 28 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.9 s3.0 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
168 ms131 msMay 9Oct 24164 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026140 ms
May 16, 2026138 ms
May 23, 2026137 ms
May 30, 2026135 ms
Jun 6, 2026137 ms
Jun 13, 2026140 ms
Jun 20, 2026146 ms
Jun 27, 2026152 ms
Jul 4, 2026154 ms
Jul 11, 2026153 ms
Jul 18, 2026149 ms
Jul 25, 2026148 ms
Aug 1, 2026149 ms
Aug 8, 2026148 ms
Aug 15, 2026149 ms
Aug 22, 2026148 ms
Aug 29, 2026149 ms
Sep 5, 2026151 ms
Sep 12, 2026154 ms
Sep 19, 2026155 ms
Sep 26, 2026158 ms
Oct 3, 2026161 ms
Oct 10, 2026161 ms
Oct 17, 2026164 ms
Oct 24, 2026164 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 mrcat.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mrcat.com.br at 1.2 s1.2 s
  2. mrcat.com.br at 2.3 s2.3 s
  3. mrcat.com.br at 3.5 s3.5 s
  4. mrcat.com.br at 4.7 s4.7 s
  5. mrcat.com.br at 5.9 s5.9 s
  6. mrcat.com.br at 7.0 s7.0 s
  7. mrcat.com.br at 8.2 s8.2 s
  8. mrcat.com.br at 9.4 s9.4 s

Speed

6 to fix7
  • Reduce unused JavaScript

    2.7 s · 792 KiB

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

  • Avoid multiple page redirects

    2.4 s

    The page goes through 1 redirect before it starts loading, costing about 2.4 s. Link and advertise the final URL directly.

  • Mobile performance score: 7

    7/100

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

  • Main-thread work: 8.0 s

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

  • Reduce unused CSS

    610 ms · 144 KiB

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

  • 20 long tasks on the main thread

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (vteximg.com.br, Google Fonts and vtex.com.br and others), adding 237 KiB and 13 ms of main-thread time.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 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 LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.42

    0.42

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • First Contentful Paint: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 54.7 s

    54.7 s

    Your largest element takes 54.7 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 33.7 s

    33.7 s

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

  • Time to Interactive: 66.5 s

    66.5 s

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

  • Cumulative Layout Shift: 0.856

    0.856

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user INP: 211 ms

    211 ms

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

  • 18 images without width and height

    18 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-24, real Chrome visitors' tap response (inp) went from 140 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +15%

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

Images and page weight

4 to fix38
  • Page weight: 21.1 MB in 395 requests

    21.1 MB

    Your homepage downloads 21.1 MB in 395 requests on a phone: images 10.2 MB (163), media 5.9 MB (1) and scripts 2.6 MB (125). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (2.3 MB) 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.

  • 16 images below the first screen load straight away

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

  • About 6.0 g of CO₂ per visit

    5.98 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

14 to fixGoogle 7282
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Elements must only use permitted ARIA attributes (9 elements)

    Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

  • 5 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 89 form fields without a label

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 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.

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

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • 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.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 300 internal links, 18 external

    The homepage links to 300 pages on mrcat.com.br and 18 external pages.

7 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “Mr. Cat: Compre Sapatos Femininos, Masculinos e Acessórios. Pague em até 6x. Aproveite!”.

  • One H1 headline

    Your main headline reads: “Compre por categoria”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Mr. Cat | Sapatos Femininos, Masculinos e Mais”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.mrcat.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.

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (751 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://www.mrcat.com.br/busca declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 14 pages share 2 titles

    / and https://www.mrcat.com.br/busca all use the title “Mr. Cat | Sapatos Femininos, Masculinos e Mais”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.mrcat.com.br/politicas/politica-de-promocoes, https://www.mrcat.com.br/politicas/politica-de-cashback, https://www.mrcat.com.br/busca, https://www.mrcat.com.br/495, https://www.mrcat.com.br/495/33 and https://www.mrcat.com.br/495/34 and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

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

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

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

Best practices

3 to fixGoogle 9285
  • 150 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 706 words of visible text.

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

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

  • 23 cookies set on arrival

    23

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

  • 48 other companies contacted

    Loading the homepage contacts 48 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 mrcat.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on mrcat.com.br, including 19 speed issues, 2 SEO issues and 3 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