pocketradar.com website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Clarity and Accessibe Accessibility Overlay and others), adding 1.2 MB and 530 ms of main-thread time.

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

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

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

Klaviyo costs a phone 127 ms of main-thread work and 313 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.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

Your homepage downloads 3.4 MB in 259 requests on a phone: scripts 1.4 MB (107), images 852 KiB (23) and other files 727 KiB (108). Under 2 MB keeps phones on slow connections fast.

Mobile_Banner_7e6cd0dc-bfe7-4f23-b06e-853edba82b70.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example Mobile_Banner_7e6cd0dc-bfe7-4f23-b06e-853edba82b70.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 34 KiB.

3 images further down the page (128 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 0.96 g of CO₂e: 115.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Pocket Radar | Baseball Radar Gun | Speed Radar – Pocket Radar Inc.”.

There are 2 <h1> headlines (“Pocket Radar Inc.” and “Smart Coach Radar™ (Model SR1100)”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 82 pages on pocketradar.com and 31 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://www.pocketradar.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.pocketradar.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.pocketradar.com/customer_authentication/redirect, https://www.pocketradar.com/pages/pocket-radar-for-players, https://www.pocketradar.com/pages/pocket-radar-for-coaches, https://www.pocketradar.com/pages/pocket-radar-for-parents, https://www.pocketradar.com/community/help-center and https://www.pocketradar.com/collections/all and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pocketradar.com/customer_authentication/redirect, https://www.pocketradar.com/pages/how-to-use, https://www.pocketradar.com/pages/product-warranty-and-registration, https://www.pocketradar.com/pages/become-a-reseller and https://www.pocketradar.com/pages/gamechanger have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Cart fetch error: TypeError: Cannot read properties of null (reading 'style')”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

The homepage carries about 888 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 24 cookies (measured from a US location before any click).

Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.