Website review, no card needed
firsttactical.co.uk website review
Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 72 checks
This review found 29 issues worth fixing on firsttactical.co.uk, 9 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78C- #58,968 of 116,304 reviewed websitesbeats 44%
- #39,070 of 66,755 online storesbeats 36%
- #37,373 of 60,924 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 978 ms |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 994 ms |
| Jun 20, 2026 | 994 ms |
| Jun 27, 2026 | 975 ms |
| Jul 4, 2026 | 985 ms |
| Jul 11, 2026 | 975 ms |
| Jul 18, 2026 | 908 ms |
| Jul 25, 2026 | 904 ms |
| Aug 1, 2026 | 917 ms |
| Aug 8, 2026 | 917 ms |
| Aug 15, 2026 | 973 ms |
| Aug 22, 2026 | 971 ms |
| Aug 29, 2026 | 955 ms |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 80 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 93 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 81 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 87 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 98 ms |
| Sep 26, 2026 | 104 ms |
| Oct 10, 2026 | 101 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 106 ms |
| Nov 14, 2026 | 104 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.7 s · 609 KiBAbout 609 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 406 KiB8 images could be 406 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, roseperl.com and Shopify and others), adding 1.6 MB and 450 ms of main-thread time.
Google Tag Manager adds 392 ms
392 msGoogle Tag Manager costs a phone 392 ms of main-thread work and 831 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.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
2,212 HTML elements
The page has 2,212 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 15 ms
15 msShopify costs a phone 15 ms of main-thread work and 560 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.
Reduce unused CSS
150 ms · 31 KiBAbout 31 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
73 KiB9 files are served with short cache lifetimes, so returning visitors download them again (73 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.
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: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 549 ms of it running JavaScript. That is comfortably low.
Server response: 36 ms
36 msYour server sent the HTML in 36 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two male officers wearing the midnight navy V2 tactical pan…”.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 80 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 500 ms
500 msReal visitors wait 500 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 129 ms
129 msScripts block the page for only 129 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 182 requests
4.3 MBYour homepage downloads 4.3 MB in 182 requests on a phone: images 1.7 MB (36), scripts 1.2 MB (44) and other files 1.2 MB (87). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “First Tactical”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“First Tactical UK” and “First Tactical UK”). One clear main headline is easier for people and search engines.
Meta description is long (306 characters)
Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
133 internal links, 14 external
The homepage links to 133 pages on firsttactical.co.uk and 14 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.firsttactical.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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.firsttactical.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.firsttactical.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
7 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
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 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
19 calls to action
The homepage has 19 calls to action, for example “Shop All”, “Shop” and “SHOP NOW”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 52 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
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
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 firsttactical.co.uk, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
roseperl.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
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 firsttactical.co.uk, including 14 speed issues, 4 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.