mxprostoreparts.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Trust Pilot and JSDelivr CDN and others), adding 581 KiB and 149 ms of main-thread time.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

8 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK FRIDAY.”.

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

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

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

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

Your homepage downloads 2.4 MB in 271 requests on a phone: other files 1,004 KiB (122), images 696 KiB (27) and scripts 480 KiB (83). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example mxpro-store-logo.png at 1,717 px wide, shown at 88 px. Resized copies would save about 78 KiB.

2 images (76 KiB) 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.

1 image further down the page (88 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

Your title is 74 characters, so Google will cut it off around 60: “Motocross Shop for Dirt Bike Parts and Motocross Apparel – MxProStoreParts”.

2 links have no real href, so search engines can't follow them.

The homepage links to 384 pages on mxprostoreparts.com and 8 external pages.

https://mxprostoreparts.com/en/pages/partsfinder, https://mxprostoreparts.com/en/collections/all and https://mxprostoreparts.com/en/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://mxprostoreparts.com/en/pages/partsfinder has no <h1> headline, so visitors and search engines get no clear main topic.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 14 cookies (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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.