jupiter-speakers.com website review

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

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

8 third-party services load with your homepage (YouTube, Google CDN and Shopify and others), adding 4.4 MB and 873 ms of main-thread time.

YouTube costs a phone 706 ms of main-thread work and 3.5 MB 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.

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

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

A phone's processor spends 3.2 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

Shopify costs a phone 33 ms of main-thread work and 760 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.

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

7 long tasks block the main thread while loading, the longest for 114 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).

30 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.

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

Your largest element takes 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “10LA-P 10" 25W Vintage American Alnico Guitar Speaker Paper…”.

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

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

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

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

Your homepage downloads 6.1 MB in 219 requests on a phone: scripts 3.6 MB (74), images 757 KiB (15) and other files 745 KiB (100). Under 2 MB keeps phones on slow connections fast.

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

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

2 dropdowns have no label.

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

6 elements hidden from screen readers can still receive keyboard focus.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

<td> elements in a large <table> do not have table headers. (1 element).

Your title is only 16 characters: “Jupiter Speakers”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 133 pages on jupiter-speakers.com and 9 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://jupiter-speakers.com/collections/all, https://jupiter-speakers.com/collections/guitar-speakers, https://jupiter-speakers.com/collections/alnico and https://jupiter-speakers.com/collections/ceramic have no meta description, so Google writes the search snippet from whatever text it finds.

https://jupiter-speakers.com/products/10la-10-50w-vintage-american-alnico-guitar-speaker, https://jupiter-speakers.com/products/10la-p-10-50w-vintage-american-alnico-guitar-speaker-paper-voice-coil, https://jupiter-speakers.com/products/10lc-10-50w-vintage-american-ceramic-guitar-speaker, https://jupiter-speakers.com/products/copy-of-10lc-10-50w-vintage-american-ceramic-guitar-speaker and https://jupiter-speakers.com/products/10sc-10-25w-vintage-american-ceramic-guitar-speaker use the same meta description. A description written for each page earns more clicks.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

Social proof on the homepage: 21 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

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