Website review, no card needed

tacticalworld.ca logo

tacticalworld.ca website review

Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 77 checks

This review found 20 issues worth fixing on tacticalworld.ca, 3 of them high impact, across 77 checks. The most urgent: hidden but focusable. 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
727 ms483 msMay 23Nov 7511 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026649 ms
May 30, 2026641 ms
Jun 6, 2026637 ms
Jun 13, 2026631 ms
Jun 20, 2026644 ms
Jun 27, 2026664 ms
Jul 4, 2026676 ms
Jul 11, 2026682 ms
Jul 18, 2026677 ms
Jul 25, 2026672 ms
Aug 1, 2026668 ms
Aug 8, 2026675 ms
Aug 15, 2026687 ms
Aug 22, 2026689 ms
Aug 29, 2026699 ms
Sep 5, 2026691 ms
Sep 12, 2026671 ms
Sep 19, 2026649 ms
Sep 26, 2026616 ms
Oct 3, 2026578 ms
Oct 10, 2026555 ms
Oct 17, 2026539 ms
Oct 24, 2026524 ms
Oct 31, 2026517 ms
Nov 7, 2026511 ms
Real-visitor tap response (INP)75th percentile, phones
107 ms84 msMay 23Nov 7102 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202688 ms
Jun 13, 202691 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202697 ms
Aug 22, 202697 ms
Aug 29, 202697 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202697 ms
Oct 3, 202699 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026103 ms
Nov 7, 2026102 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 tacticalworld.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix100
  • Improve image delivery

    454 KiB

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

  • Shopify adds 2 ms

    2 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, Klaviyo and codeblackbelt.com and others), adding 481 KiB and 2 ms of main-thread time.

  • Reduce unused CSS

    31 KiB

    About 31 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    22 KiB

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

1 to fix100
  • 18 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

13 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: 0.6 s

    0.6 s

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

  • Real-user INP: 89 ms

    89 ms

    Real visitors wait 89 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: 0.6 s

    0.6 s

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

  • Real-user TTFB: 558 ms

    558 ms

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

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

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Speed Index: 1.2 s

    1.2 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.1 s

    1.1 s

    The page is fully interactive after 1.1 s.

Images and page weight

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

    7035d8ff-4a1f-42ef-8563-74ca1b047a3b.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).

  • 1 image in older formats

    1 image (32 KiB) is 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.

  • About 0.5 g of CO₂ per visit

    0.50 g

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

2 checks passed
  • Page weight: 1.8 MB in 57 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 57 requests on a phone: images 1.0 MB (26), scripts 600 KiB (22) and HTML 65 KiB (1). That is a lean page.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9295
  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

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

  • 2 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

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

2 checks passed
  • Every image has alt text

    All 57 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 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 (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Tactical World Store Canada | Professional Tactical Gear & Clothing”.

  • 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 (272 characters)

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

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

  • 109 internal links, 4 external

    The homepage links to 109 pages on tacticalworld.ca and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Tactical World Store Canada”.

  • Canonical URL set

    The canonical URL is https://tacticalworld.ca/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://tacticalworld.ca/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 (504 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 11 pages without a meta description

    https://tacticalworld.ca/collections/all, https://tacticalworld.ca/pages/fall-collection, https://tacticalworld.ca/collections/top, https://tacticalworld.ca/collections/tactical-shirts, https://tacticalworld.ca/collections/tactical-polo-shirt and https://tacticalworld.ca/collections/pants and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://tacticalworld.ca/pages/fall-collection and https://tacticalworld.ca/collections/combat-clothing have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://tacticalworld.ca/collections/combat-clothing has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

  • About 272 words of copy

    The homepage carries about 272 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Learn more”, “Contact Us” and “Newsletter Signup”.

  • 4 short forms

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 tacticalworld.ca, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Snap Cart Drawer · Also Bought · Judge Me Reviews · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Frequently Bought · Bundle Products By Thimatic

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on tacticalworld.ca, including 3 speed issues, 4 SEO issues and 4 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