morrisontradingpost.com website review

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

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

About 336 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

5 third-party services load with your homepage (Shopify, cloudfront.net and shop.app and others), adding 1.1 MB and 315 ms of main-thread time.

Shopify costs a phone 250 ms of main-thread work and 998 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.2 s on main-thread work while loading, 778 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 24 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.

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

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

Polyfills for old browsers add 11 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.

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

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

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

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

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

Your homepage downloads 3.9 MB in 318 requests on a phone: images 1.4 MB (18), other files 1.2 MB (140) and scripts 989 KiB (141). Under 2 MB keeps phones on slow connections fast.

Sports_Singles_Slider_MOBILE.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).

1 image (48 KiB) is 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 element hidden from screen readers can still receive keyboard focus.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 21 characters: “Morrison Trading Post”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 131 pages on morrisontradingpost.com and 6 external pages.

https://morrisontradingpost.com/pages/sell-your-collection, https://morrisontradingpost.com/pages/contact-us, https://morrisontradingpost.com/collections/hockey-wax, https://morrisontradingpost.com/collections/baseball-wax, https://morrisontradingpost.com/collections/football-wax and https://morrisontradingpost.com/collections/basketball-wax and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://morrisontradingpost.com/pages/events and https://morrisontradingpost.com/pages/sell-your-collection have no <h1> headline, so visitors and search engines get no clear main topic.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 316 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.