merchmountain.com website review

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

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, rise-ai.com and Shopify and others), adding 557 KiB and 263 ms of main-thread time.

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

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

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

8 KiB could be saved by minifying JavaScript.

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 9.6 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 9.7 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 2.3 MB in 171 requests on a phone: images 803 KiB (17), other files 719 KiB (73) and scripts 626 KiB (52). Under 2 MB keeps phones on slow connections fast.

1 image (72 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 0.64 g of CO₂e: 76.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Your title is only 14 characters: “Merch Mountain”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 317 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.

Your <h1> is empty.

The homepage links to 71 pages on merchmountain.com and 17 external pages.

https://www.merchmountain.com/pages/bands-brands, https://www.merchmountain.com/pages/service, https://www.merchmountain.com/collections/allman-brothers-band-museum-at-the-big-house, https://www.merchmountain.com/collections/bag-men, https://www.merchmountain.com/collections/capricorn-sound-studios and https://www.merchmountain.com/collections/chris-robinson-brotherhood and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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.

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

The homepage has only about 190 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads 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 9 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.