sjmradio.com website review

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

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

The HTML itself could arrive about 1.6 s sooner: redirects, a slow server response or missing compression delay everything after it.

About 222 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, embedsocial.com and Adroll and others), adding 2.2 MB and 701 ms of main-thread time.

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

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

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

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

embedsocial.com costs a phone 145 ms of main-thread work and 1.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.

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

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

Desktop scores 69 but mobile only 41. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 KiB could be saved by minifying CSS.

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

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOUR BEST SOURCE FOR MOTOROLA TWO-WAY RADIOS”. Most of its time is element render delay (2.8 s).

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

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

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 43.8 MB in 400 requests on a phone: images 40.7 MB (90), scripts 1.4 MB (141) and fonts 1.1 MB (15). Under 2 MB keeps phones on slow connections fast.

19 images weigh 31.2 MB together. On a phone connection a single image that size takes seconds.

40 images (36.4 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

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

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

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

Your title is only 21 characters: “Home Page | SJM Radio”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 160 pages on sjmradio.com and 9 external pages.

A phone browser shows 5,152 words, but the HTML your server sends has only 1,491. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://sjmradio.com/catalog, https://sjmradio.com/accessories and https://sjmradio.com/solutions are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sjmradio.com/locations, whose canonical is https://sjmradio.com/los-angeles-locations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sjmradio.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

https://sjmradio.com/contact, https://sjmradio.com/locations, https://sjmradio.com/promotions and https://sjmradio.com/free-consultation took over 3 s to send their HTML from our server.

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

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

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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 5,152 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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 6 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.