radiodepot.com website review

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

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

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

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

6 images could be 133 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 third-party services load with your homepage (Klaviyo, 9gtb.com and Shopify and others), adding 314 KiB and 70 ms of main-thread time.

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

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

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

1 image 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 79 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.2 MB in 172 requests on a phone: other files 986 KiB (100), images 684 KiB (18) and scripts 382 KiB (45). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example emotorola-empower-circle_long_full-color.png at 8,554 px wide, shown at 137 px. Resized copies would save about 90 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Radio Depot | Buy Motorola, Icom, and Kenwood radios and accessories”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 61 pages on radiodepot.com and 0 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description 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://www.radiodepot.com/pages/two-way-radio-promotions-rebates-and-limited-offers and https://www.radiodepot.com/collections/kenwood-two-way-radios have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.radiodepot.com/pages/two-way-radio-promotions-rebates-and-limited-offers and https://www.radiodepot.com/pages/our-policies have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.radiodepot.com/collections/radio-infrastructure, https://www.radiodepot.com/pages/motorola-minitor-vi-and-7-fire-pagers and https://www.radiodepot.com/pages/radio-depot-motorola-solutions-2025-empower-circle-winner took over 3 s to send their HTML from our server.

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

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

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

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.

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.

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.

The homepage carries about 460 words of visible text.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (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 10 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.