mudmixer.ca website review

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 1.5 MB and 1.3 s of main-thread time.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

9 images could be 491 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

About 644 KiB of JavaScript is downloaded but never used on this page.

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

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

Klaviyo costs a phone 219 ms of main-thread work and 318 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.

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

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

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

Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need.

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.

4 KiB could be saved by minifying JavaScript.

2 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MudMixer Evolution Bundle with mixer, hopper extension and …”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.5 MB in 385 requests on a phone: scripts 2.0 MB (131), other files 1.0 MB (174) and images 758 KiB (24). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your canonical URL points to mudmixer.com, not mudmixer.ca, so Google may credit that host instead.

Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://mudmixer.com)”.

The homepage links to 79 pages on mudmixer.ca and 15 external pages.

https://mudmixer.ca/products/mudmixer and https://mudmixer.ca/products/mudmixer-evolution all use the title “MudMixer® Evolution | Portable & Electric Concrete Mixer”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mudmixer.ca/policies/shipping-policy, https://mudmixer.ca/collections/bfcm-sale, https://mudmixer.ca/pages/videos, https://mudmixer.ca/pages/support and https://mudmixer.ca/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://mudmixer.ca/products/mudmixer and https://mudmixer.ca/products/mudmixer-evolution use the same meta description. A description written for each page earns more clicks.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97087990&tm=gtm002&Ver=2&mid=aea4cbe2-cca9-47ac-8ee2-9b5feb5b0bdd&bo=1&sid=12d57360da4711f1b3bf336be00c8f48&vid=12d57ea0da4711f1a7232550b2903dcf&vids=1&msclkid=N&gtm_t.

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

3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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,113 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (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.

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

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.

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