mbusa.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user CLS: 0.36

  0.36

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

• Real-user LCP: 3.3 s

  3.3 s

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

• Real-user INP: 222 ms

  222 ms

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

• Real-user TTFB: 928 ms

  928 ms

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

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

  +16%

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

• Page weight: 6.5 MB

  6.5 MB

  Your homepage downloads 6.5 MB on a phone, 2.1 MB of it images (32%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  US-SF3-Homepage-Hero-S.jpg weighs 824 KiB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 10 images below the first screen load straight away

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

  Elements (5)

• About 1.8 g of CO₂ per visit

  1.84 g

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

• Invalid ARIA attributes

  7 elements use ARIA attributes their role does not allow, which confuses screen readers.

  Elements (3)

• 4 buttons without a name

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

  Elements (3)

• 8 tap targets too small

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

  Elements (3)

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

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• ARIA role should be appropriate for the element (3 elements)

  ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

  Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  View sourceElements (1)

• 6 H1 headlines

  There are 6 <h1> headlines (“Vehicles”, “” and “Great things come to those who act.”). One clear main headline is easier for people and search engines.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 150 internal links, 15 external

  The homepage links to 150 pages on mbusa.com and 15 external pages.

• No llms.txt

  There is no https://www.mbusa.com/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 pages with very little text

  https://www.mbusa.com/en/vehicles/build and https://www.mbusa.com/en/all-vehicles 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.

• 15 internal pages checked

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

• 2 broken images

  2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5061642&Ver=2&mid=6e673b0a-a254-4453-89e9-e2120958bfe2&bo=2&sid=af553000c5f411f1beaad541d8331396&vid=af555450c5f411f18146d16e68791d9e&vids=1&msclkid=N&pi=918639831&lg=.

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Refused to execute script from 'https://www.mbusa.com/content/dam/mb-nafta/hooks/us/home/pre-home.js' because its MIME …”.

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

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

  The homepage carries about 460 words of visible text.

• 10 trackers load before any consent

  10

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

• 19 cookies set on arrival

  19

  Opening the homepage sets 19 cookies, 3 of them by other companies (measured from a US location before any click).

• 43 other companies contacted

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