Website review, no card needed

mwm.com.br logo

mwm.com.br website review

Visit site (opens in a new tab)Reviewed 19 November 202648 issues · 84 checks

This review found 48 issues worth fixing on mwm.com.br, 16 of them high impact, across 84 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
5.4 s3.1 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.2 s
Jun 6, 20265.1 s
Jun 13, 20264.8 s
Jun 20, 20264.7 s
Jun 27, 20265.0 s
Jul 4, 20265.1 s
Jul 11, 20265.0 s
Jul 18, 20265.0 s
Jul 25, 20264.9 s
Aug 1, 20264.8 s
Aug 8, 20264.8 s
Aug 15, 20264.8 s
Aug 22, 20264.8 s
Aug 29, 20264.8 s
Sep 5, 20264.7 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.5 s
Oct 10, 20264.3 s
Oct 17, 20263.9 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Nov 7, 20263.3 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
319 ms138 msMay 30Nov 14192 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026171 ms
Jun 6, 2026171 ms
Jun 13, 2026177 ms
Jun 20, 2026174 ms
Jun 27, 2026191 ms
Jul 4, 2026202 ms
Jul 11, 2026203 ms
Jul 18, 2026207 ms
Jul 25, 2026208 ms
Aug 1, 2026205 ms
Aug 8, 2026199 ms
Aug 15, 2026198 ms
Aug 22, 2026178 ms
Aug 29, 2026171 ms
Sep 5, 2026165 ms
Sep 12, 2026159 ms
Sep 19, 2026206 ms
Sep 26, 2026235 ms
Oct 3, 2026277 ms
Oct 10, 2026298 ms
Oct 17, 2026241 ms
Oct 24, 2026212 ms
Oct 31, 2026191 ms
Nov 7, 2026182 ms
Nov 14, 2026192 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 mwm.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mwm.com.br at 0.6 s0.6 s
  2. mwm.com.br at 1.3 s1.3 s
  3. mwm.com.br at 1.9 s1.9 s
  4. mwm.com.br at 2.5 s2.5 s
  5. mwm.com.br at 3.2 s3.2 s
  6. mwm.com.br at 3.8 s3.8 s
  7. mwm.com.br at 4.4 s4.4 s
  8. mwm.com.br at 5.1 s5.1 s

Speed

10 to fix47
  • Reduce unused JavaScript

    17.1 s · 2.7 MB

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

  • Render-blocking requests

    3.5 s

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

  • Improve image delivery

    1.4 s · 539 KiB

    5 images could be 539 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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 (YouTube, Google Tag Manager and JSDelivr CDN and others), adding 5.1 MB and 1.6 s of main-thread time.

  • YouTube adds 972 ms

    972 ms

    YouTube costs a phone 972 ms of main-thread work and 3.9 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.

  • Reduce unused CSS

    750 ms · 241 KiB

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

  • Use efficient cache lifetimes

    550 ms · 128 KiB

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

  • Google Tag Manager adds 469 ms

    469 ms

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

  • Main-thread work: 3.9 s

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

  • Minify CSS

    150 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • 12 long tasks on the main thread

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 470 ms

    470 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 33.2 s

    33.2 s

    Your largest element takes 33.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Clicando em "Aceito todos os Cookies", você concorda com o …”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 39.3 s

    39.3 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

    The first text or image appears after 4.2 s on a phone. Good is under 1.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 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.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 972 ms

    972 ms

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

  • Total Blocking Time: 413 ms

    413 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 34% faster for real visitors

    -34%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 7.2 MB in 174 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 174 requests on a phone: scripts 4.8 MB (60), images 1.1 MB (34) and stylesheets 513 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.1 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.

  • An image on the first screen is lazy-loaded

    MWM_ADAPT_KV_375X574-1.png 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).

  • About 2.0 g of CO₂ per visit

    2.04 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.04 g of CO₂e: 244.9 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

7 to fixGoogle 8591
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Malformed lists

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

  • 7 images without alt text

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

  • All page content should be contained by landmarks (12 elements)

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

  • 13 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 9279
  • Title is short (10 characters)

    Your title is only 10 characters: “MWM – Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“SOLUÇÕES QUE MOVIMENTAM O FUTURO”, “SOLUÇÕES QUE MOVIMENTAM O FUTURO” and “”). One clear main headline is easier for people and search engines.

  • Meta description is long (224 characters)

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

  • Structured data has 1 problem

    Structured data found (CollectionPage, Organization, SearchAction and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 190 internal links, 12 external

    The homepage links to 190 pages on mwm.com.br and 12 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://mwm.com.br/pt/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://mwm.com.br/llms.txt (28 KiB, 134 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix75
  • 7 linked pages hidden from search

    https://mwm.com.br/pt/contratos-de-manufatura, https://mwm.com.br/pt/motores/motores-etanol, https://mwm.com.br/pt/motores/motores-diesel, https://mwm.com.br/pt/motores/motores-oem, https://mwm.com.br/pt/geradores-e-torres/geradores/gerador-a-diesel and https://mwm.com.br/pt/geradores-e-torres/geradores/gerador-a-gas-natural and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://mwm.com.br/pt and / all use the title “MWM – Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://mwm.com.br/pt/geradores-e-torres/geradores-maritimos/geradores-maritimos-para-aplicacoes-de-lazer and https://mwm.com.br/pt/geradores-e-torres/geradores-maritimos/geradores-maritimos-para-aplicacoes-de-trabalho 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 /, whose canonical is https://mwm.com.br/pt. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages slow to respond

    https://mwm.com.br/pt/motores/motores-maritimos/aplicacoes-de-trabalho, https://mwm.com.br/pt/geradores-e-torres/geradores/gerador-a-biogas, https://mwm.com.br/pt/geradores-e-torres/geradores/gerador-a-gas-natural, https://mwm.com.br/pt/geradores-e-torres/geradores-maritimos/geradores-maritimos-para-aplicacoes-de-lazer and https://mwm.com.br/pt/descarbonizacao/torre-de-iluminacao-fotovoltaica took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6588
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://mwm.com.br/wp-content/themes/mwm/assets/fonts/SofiaSansExtraCondensed-VariableFont…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    39 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 257 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 mwm.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

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Hostinger

Company

Headquarters
Sao Paulo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on mwm.com.br, including 21 speed issues, 4 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