Website review, no card needed

policescanneroutlet.com logo

policescanneroutlet.com website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 83 checks

This review found 29 issues worth fixing on policescanneroutlet.com, 8 of them high impact, across 83 checks. The most urgent: 2 linked pages are broken. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.2 sMay 23Nov 72.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
119 ms91 msMay 23Nov 794 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026108 ms
May 30, 2026110 ms
Jun 6, 2026111 ms
Jun 13, 2026113 ms
Jun 20, 2026116 ms
Jun 27, 2026116 ms
Jul 4, 2026115 ms
Jul 11, 2026108 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026102 ms
Aug 8, 2026104 ms
Aug 15, 2026110 ms
Aug 22, 2026112 ms
Aug 29, 2026114 ms
Sep 5, 2026114 ms
Sep 12, 2026111 ms
Sep 19, 2026108 ms
Sep 26, 2026105 ms
Oct 3, 2026104 ms
Oct 10, 2026102 ms
Oct 17, 202697 ms
Oct 24, 202696 ms
Oct 31, 202694 ms
Nov 7, 202694 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of policescanneroutlet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. policescanneroutlet.com at 0.4 s0.4 s
  2. policescanneroutlet.com at 0.8 s0.8 s
  3. policescanneroutlet.com at 1.1 s1.1 s
  4. policescanneroutlet.com at 1.5 s1.5 s
  5. policescanneroutlet.com at 1.9 s1.9 s
  6. policescanneroutlet.com at 2.3 s2.3 s
  7. policescanneroutlet.com at 2.6 s2.6 s
  8. policescanneroutlet.com at 3.0 s3.0 s

Speed

5 to fix73
  • Mobile performance score: 73

    73/100

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

  • Render-blocking requests

    750 ms

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

  • Use efficient cache lifetimes

    300 ms · 85 KiB

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

  • Reduce unused JavaScript

    300 ms · 56 KiB

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

  • Shopify adds 1 ms

    1 ms

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • Improve image delivery

    79 KiB

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

  • 2 long tasks on the main thread

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 138 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 9.1 s

    9.1 s

    Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Free CB Ant banner.png__PID:b1284ec0-e382-4dbf-bf25-5604a20…”.

  • Time to Interactive: 9.2 s

    9.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 90 ms

    90 ms

    Real visitors wait 90 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 602 ms

    602 ms

    Real visitors wait 602 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.015

    0.015

    The layout barely moves while loading (CLS 0.015, good is under 0.1).

  • Total Blocking Time: 32 ms

    32 ms

    Scripts block the page for only 32 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    Free_CB_Ant_banner_648a9edf-1b41-40d2-9653-da03969b6bae.png 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).

  • About 0.4 g of CO₂ per visit

    0.44 g

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

3 checks passed
  • Page weight: 1.5 MB in 97 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 97 requests on a phone: scripts 833 KiB (43), images 422 KiB (33) and fonts 144 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8289
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links must have discernible text (9 elements)

    Links must have discernible text: 9 elements on the page fail this check, rated serious by axe-core.

  • 3 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (2 elements)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9282
  • Title is long (149 characters)

    Your title is 149 characters, so Google will cut it off around 60: “Top Police Scanner Radio Online Store, Expert Scanner Programming – Bearcat Warehouse | A…”.

  • No structured data

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

  • Meta description is long (240 characters)

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

  • 9 links with vague text

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

  • 121 internal links, 8 external

    The homepage links to 121 pages on policescanneroutlet.com and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Collections”.

  • Canonical URL set

    The canonical URL is https://bearcatwarehouse.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://bearcatwarehouse.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (443 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://bearcatwarehouse.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70
  • 2 linked pages are broken

    Your homepage links to https://bearcatwarehouse.com/products/bcd536hp-digital-police-scanner-free-programming and https://bearcatwarehouse.com/products/uniden-replacement-battery-for-sds150-bps150-bt-972, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 6 pages without an H1

    https://bearcatwarehouse.com/collections/police-scanner-programming, https://bearcatwarehouse.com/collections/cb-radios, https://bearcatwarehouse.com/collections/marine, https://bearcatwarehouse.com/pages/uniden-scanner-questions-and-videos, https://bearcatwarehouse.com/products/uniden-sds150-digital-police-scanner and https://bearcatwarehouse.com/products/uniden-sds200-police-scanner have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 6 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • No call to action on the first screen

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

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • Only about 237 words

    The homepage has only about 237 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

4 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Register / Login”, “Learn More” and “Shop All Radio Scanners”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    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.

  • 14 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at policescanneroutlet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Smart Filter Search · Judge Me Reviews · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Powerful Form Builder · Also Bought · Smart Product Filters · Avada Faqs · Accessibly App · Restockrocket · Freegifts · Compareder · jsdelivr.net · reputon.com · chimpstatic.com · govx.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Analytics
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on policescanneroutlet.com, including 8 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25