musiciansfriend.com website review

104 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

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

audioeye.com costs a phone 1.6 s of main-thread work and 329 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 11.2 s on main-thread work while loading, 7.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Quantum Metric and others), adding 1.6 MB and 3.7 s of main-thread time.

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

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

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

Facebook costs a phone 398 ms of main-thread work and 268 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.

Quantum Metric costs a phone 402 ms of main-thread work and 153 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,926 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

31 KiB could be saved by minifying JavaScript.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rocktober. Up to 50% Off. Deals on premium brands for all m…”.

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

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

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

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

Real visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors wait 840 ms for your server to start answering (75th percentile). Good is under 800 ms.

The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.

3 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-03, real Chrome visitors' tap response (inp) went from 187 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.4 MB in 289 requests on a phone: scripts 2.9 MB (70), images 2.1 MB (88) and other files 918 KiB (70). Under 2 MB keeps phones on slow connections fast.

12 images (1.2 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.

15 images further down the page (973 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images are downloaded at several times the size a phone draws them, for example gibson-les-paul-standard-50s-honeyburst.jpg at 1,024 px wide, shown at 169 px. Resized copies would save about 341 KiB.

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

8 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

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

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

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

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

The homepage links to 594 pages on musiciansfriend.com and 9 external pages.

There is no https://www.musiciansfriend.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.musiciansfriend.com/trackorder is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.musiciansfriend.com/returns has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.musiciansfriend.com/returns, whose canonical is https://www.musiciansfriend.com/pages/45-day-returns. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.musiciansfriend.com/trackorder, https://www.musiciansfriend.com/faq, https://www.musiciansfriend.com/rewards and https://www.musiciansfriend.com/thehub have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.musiciansfriend.com/guitars, https://www.musiciansfriend.com/electric-guitars and https://www.musiciansfriend.com/acoustic-guitars took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://quhdnr.musiciansfriend.com/g/uids?pld=JGcaTsfDLVa9TO2CPTYPM6Bct6SX27AmlYqUcA2W5SYHE2y8oJID4drofY2ELMebSYuxZEsVtQQd_r-ngFTAQ4uh_YECIll19Z9nmzOp3aCBV-qWN0XBntSiKbw9gvpjVZgdNbQnM8YGqGz7nhnUL60pmT.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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