Website review, no card needed

strikeman.io logo

strikeman.io website review

Visit site (opens in a new tab)Reviewed 7 November 202631 issues · 87 checks

This review found 31 issues worth fixing on strikeman.io, 9 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
1.9 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
181 ms131 msMay 16Oct 31161 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026171 ms
May 23, 2026175 ms
May 30, 2026170 ms
Jun 6, 2026165 ms
Jun 13, 2026155 ms
Jun 20, 2026146 ms
Jun 27, 2026145 ms
Jul 4, 2026138 ms
Jul 11, 2026138 ms
Jul 18, 2026138 ms
Jul 25, 2026138 ms
Aug 1, 2026137 ms
Aug 8, 2026142 ms
Aug 15, 2026147 ms
Aug 22, 2026150 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026153 ms
Sep 19, 2026153 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026154 ms
Oct 31, 2026161 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 strikeman.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. strikeman.io at 0.8 s0.8 s
  2. strikeman.io at 1.6 s1.6 s
  3. strikeman.io at 2.3 s2.3 s
  4. strikeman.io at 3.1 s3.1 s
  5. strikeman.io at 3.9 s3.9 s
  6. strikeman.io at 4.7 s4.7 s
  7. strikeman.io at 5.5 s5.5 s
  8. strikeman.io at 6.2 s6.2 s

Speed

9 to fix67
  • Improve image delivery

    1.1 s · 807 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 67

    67/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 2.5 MB and 663 ms of main-thread time.

  • Reduce unused JavaScript

    551 KiB

    About 551 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.8 s

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

  • Shopify adds 176 ms

    176 ms

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

  • Google Tag Manager adds 219 ms

    219 ms

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

  • 2,451 HTML elements

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

  • Reduce unused CSS

    150 ms · 62 KiB

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

  • Use efficient cache lifetimes

    202 KiB

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

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    40 KiB

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

  • Minify CSS

    16 KiB

    16 KiB could be saved by minifying CSS.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 40 ms

    40 ms

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

Core Web Vitals

6 to fix100
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 10.4 s

    10.4 s

    Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Strikeman Standard Kit with a red gift ribbon, target, trip…”.

  • Time to Interactive: 18.7 s

    18.7 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user TTFB: 828 ms

    828 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

7 checks passed
  • 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: 163 ms

    163 ms

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (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.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.046

    0.046

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

  • Total Blocking Time: 64 ms

    64 ms

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

Images and page weight

4 to fix35
  • Page weight: 5.8 MB in 341 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 341 requests on a phone: images 2.3 MB (34), other files 1.6 MB (156) and scripts 1.3 MB (119). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    laser-cartridge-how-to-2024.jpg weighs 583 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (740 KiB) 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.

  • 4 images far larger than shown

    404 KiB

    4 images are downloaded at several times the size a phone draws them, for example strikeman-holiday-santa-sleigh.png at 2,172 px wide, shown at 90 px. Resized copies would save about 404 KiB.

  • About 1.7 g of CO₂ per visit

    1.66 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9495
  • 15 text elements with low contrast

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 59 form fields without a label

    59 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 23 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • 2 H1 headlines

    There are 2 <h1> headlines (“Give the gift of training at home.” and “The complete kit for training anywhere”). One clear main headline is easier for people and search engines.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 1 link with vague text

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

  • 155 internal links, 6 external

    The homepage links to 155 pages on strikeman.io and 6 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Explore Strikeman dry-fire training kits, laser cartridges, and the free app for practice at home. Compare setups and c…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Strikeman Dry Fire Training – Save on Ammo & Improve Accuracy”.

  • Canonical URL set

    The canonical URL is https://www.strikeman.io/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.strikeman.io/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.strikeman.io/pages/shop-dry-fire-systems-gift-bundles-strikeman-dry-fire-training-gifts-for-shooters and https://www.strikeman.io/pages/shop-all-strikeman-dry-fire-training-products have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.strikeman.io/cdn/shop/t/170/assets/homepage-migration.css?v=271250' because it…”.

2 checks passed
  • Tap targets are thumb-sized

    23 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • No direct contact details

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

  • About 1,825 words of copy

    The homepage carries about 1,825 words of visible text.

  • Urgency cues

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Standard Kit” and “Shop Marksman Kit”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “Shop All Dry-Fire Systems”, “Shop All Laser Cartridges” and “Shop All”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 24 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 2 of them by other companies (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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 strikeman.io, 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 28 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

The Rave · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Pro Auto Activate · Judge Me Reviews · Tolstoy · Regios Discounts · Mbc Bundle Builder · Maestra · Pcc52fnn4 Opensend · Ufe · Countdown Timer · Upsell Funnel Engine Upsells · Sea Survey · Navidium Shipping Protection · Twitter Multi Pixels · Appstle Bundles · hulkapps.com · kilatechapps.com · automizely.com · govx.com · printful.com · elfsight.com · jsdelivr.net · luckyorange.com · 9gtb.com · klck.dev

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Employees
16
Headquarters
Henderson

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on strikeman.io, including 15 speed issues, 3 SEO issues and 1 conversion gap. 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