masseyferguson.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google Maps and TrustArc and others), adding 1.7 MB and 636 ms of main-thread time.

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

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

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

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

Google Maps costs a phone 174 ms of main-thread work and 391 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.

site.com costs a phone 11 ms of main-thread work and 706 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.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Desktop scores 78 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Your homepage downloads 45.2 MB in 157 requests on a phone: images 42.9 MB (82), scripts 1.7 MB (40) and stylesheets 195 KiB (7). Under 2 MB keeps phones on slow connections fast.

28 images weigh 32.9 MB together. On a phone connection a single image that size takes seconds.

27 images are downloaded at several times the size a phone draws them, for example mf-implements-1800x933.jpg at 1,800 px wide, shown at 360 px. Resized copies would save about 20.5 MB.

40 images (37.9 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.

29 images further down the page (31.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 dropdown has no label.

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

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

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

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

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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

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

Your meta description is only 68 characters: “Massey Ferguson is a Global Leading Brand of Agricultural Machinery.”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

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

The homepage links to 170 pages on masseyferguson.com and 22 external pages.

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.

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

https://www.masseyferguson.com/en_us and https://www.masseyferguson.com/en_us.html all use the title “Massey Ferguson United States official website”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.masseyferguson.com/en_us/products/tractors/high-horse-power.html, https://www.masseyferguson.com/en_us/products/tractors/mid-range.html, https://www.masseyferguson.com/en_us/products/tractors/utility.html, https://www.masseyferguson.com/en_us/products/tractors/compact.html, https://www.masseyferguson.com/en_us/products/tractors/utility/mf-3-specialty.html and https://www.masseyferguson.com/en_us/products/hay-and-forage/round-balers.html and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.masseyferguson.com/en_us.html, https://www.masseyferguson.com/en_us/products/tractors/utility/mf-3-specialty.html, https://www.masseyferguson.com/en_us/products/hay-and-forage/mowers-conditioners.html, https://www.masseyferguson.com/en_us/products/hay-and-forage/rakes-tedders.html, https://www.masseyferguson.com/en_us/products/hay-and-forage/self-propelled-windrowers.html and https://www.masseyferguson.com/en_us/products/sprayers/mf-500r-series.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.masseyferguson.com/en_us/.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://agcocorp.my.site.com/ESWContactUsSalesAIAg1761818695455/assets/styles/bootstrap.mi…”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Quantcast (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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