productsourceguys.com website review

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

12 images could be 378 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

Google Tag Manager costs a phone 261 ms of main-thread work and 479 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 1,516 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

6 third-party services load with your homepage (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 579 KiB and 263 ms of main-thread time.

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

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

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.

5 KiB could be saved by minifying CSS.

1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

Your largest element takes 9.4 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.5 s. Good is under 3.8 s.

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

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

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 2.5 MB in 152 requests on a phone: images 884 KiB (46), other files 710 KiB (75) and scripts 680 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image (36 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.70 g of CO₂e: 83.5 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.

4 tap targets are too small or too close together to hit reliably with a finger.

Some list items are not inside a list.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

Your <h1> is empty.

The homepage links to 206 pages on productsourceguys.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://productsourceguys.com/collections/music, https://productsourceguys.com/collections/stringed-instruments-all, https://productsourceguys.com/collections/guitars, https://productsourceguys.com/collections/stringed-instruments-violins-banjos-ukuleles, https://productsourceguys.com/collections/guitar-stringed-instrument-accessories and https://productsourceguys.com/collections/instrument-cases and 9 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 120 found) and read each the way a search engine does.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

The homepage carries about 273 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 11 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.