taser.com website review

About 891 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Curalate and others), adding 1.9 MB and 1.2 s of main-thread time.

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

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

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

ZenDesk costs a phone 163 ms of main-thread work and 431 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 long tasks block the main thread while loading, the longest for 225 ms. During a long task the page ignores taps.

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

46 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 19 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.

Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner image”.

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

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

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

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

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

Your homepage downloads 4.0 MB in 339 requests on a phone: scripts 2.2 MB (109), other files 1.0 MB (159) and images 392 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

There are 2 <h1> headlines (“” and “Aim. Deploy. Escape.”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 84 pages on taser.com and 11 external pages.

/collections/all, /policies/shipping-policy and /collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /pages/device-comparison and /pages/trainer-resources have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://media.sezzle.com/branding/2.0/Sezzle_Logo_FullColor_WhiteWM.svg.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://buy.axon.com/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

taser.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

taser.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 449 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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