Website review, no card needed
byrna.co.za website review
Visit site (opens in a new tab)Reviewed 16 November 202650 issues · 86 checks
This review found 50 issues worth fixing on byrna.co.za, 19 of them high impact, across 86 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
69D- #100,225 of 116,487 reviewed websitesbeats 12%
- #61,329 of 66,776 online storesbeats 7%
- #56,734 of 60,929 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 99 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 98 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 100 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 110 ms |
| Oct 31, 2026 | 107 ms |
| Nov 7, 2026 | 111 ms |
| Nov 14, 2026 | 113 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
Speed
Reduce unused JavaScript
9.5 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.5 s faster on a phone.
Use efficient cache lifetimes
2.6 s · 593 KiB24 files are served with short cache lifetimes, so returning visitors download them again (593 KiB).
Render-blocking requests
1.4 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and amaicdn.com and others), adding 3.8 MB and 1.8 s of main-thread time.
Improve image delivery
500 ms · 920 KiB16 images could be 920 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Minify JavaScript
900 ms · 55 KiB55 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 761 ms
761 msGoogle Tag Manager costs a phone 761 ms of main-thread work and 1.4 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.
Reduce unused CSS
580 ms · 182 KiBAbout 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.
YouTube adds 351 ms
351 msYouTube costs a phone 351 ms of main-thread work and 999 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.
Legacy JavaScript
300 ms · 103 KiBPolyfills for old browsers add 103 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
amaicdn.com adds 170 ms
170 msamaicdn.com costs a phone 170 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.
Yotpo adds 125 ms
125 msYotpo costs a phone 125 ms of main-thread work and 393 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.
Google CDN adds 79 ms
79 msGoogle CDN costs a phone 79 ms of main-thread work and 352 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 174 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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 30.6 s
30.6 sYour largest element takes 30.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Speed Index: 14.3 s
14.3 sVisually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 691 ms
691 msScripts block taps and scrolling for 691 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 103 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user TTFB: 396 ms
396 msReal visitors wait 396 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 257 requests
6.8 MBYour homepage downloads 6.8 MB in 257 requests on a phone: scripts 3.9 MB (76), images 1.7 MB (34) and other files 784 KiB (119). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Red_Grey_Pepper.webp weighs 525 KiB. On a phone connection a single image that size takes seconds.
7 images far larger than shown
836 KiB7 images are downloaded at several times the size a phone draws them, for example Red_Grey_Pepper.webp at 1,280 px wide, shown at 143 px. Resized copies would save about 836 KiB.
7 images below the first screen load straight away
7 images further down the page (1,014 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (525 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 1.9 g of CO₂ per visit
1.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.92 g of CO₂e: 230.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
ARIA tooltip nodes must have an accessible name (1 element)
ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
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.
1 checks passed
53 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: 53 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“<img src="//byrna.co.za/cdn/shop/files/Byrna_Tech…”, “BYRNA LESS-LETHAL” and “TCR”). One clear main headline is easier for people and search engines.
Meta description is long (320 characters)
Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://byrna.co.za{{ routes.search_url }}…”.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
43 internal links, 3 external
The homepage links to 43 pages on byrna.co.za and 3 external pages.
5 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “Byrna South Africa - Less Lethal Products”.
Canonical URL set
The canonical URL is https://byrna.co.za/.
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://byrna.co.za/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (644 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://byrna.co.za/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 linked pages are broken
Your homepage links to https://byrna.co.za/collections/non-lethal-self-defense-byrna-sd, https://byrna.co.za/products/byrna-sd-max-kit and https://byrna.co.za/products/byrna-max-intensity-self-defense-bad-guy-repellent-2-oz-spray-bottle, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page points its canonical at the homepage
https://byrna.co.za/products/byrna-banshee-personal-safety-alarm declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://byrna.co.za/products/byrna-banshee-personal-safety-alarm all use the title “Byrna South Africa - Less Lethal Products”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://byrna.co.za/collections/bad-guy-repellent-pepper-spray-tear-gas-self-defense-spray, https://byrna.co.za/collections/byrna-self-defense-projectiles, https://byrna.co.za/collections/accessories, https://byrna.co.za/blogs/byrna-nation and https://byrna.co.za/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://byrna.co.za/products/byrna-sd-xl-max-launcher-kit has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://byrna.co.za/collections/bad-guy-repellent-pepper-spray-tear-gas-self-defense-spray, https://byrna.co.za/pages/contact and https://byrna.co.za/products/byrna-sd-xl-max-launcher-kit have 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 17 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 929 words of copy
The homepage carries about 929 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
16 calls to action
The homepage has 16 calls to action, for example “CONTACT”, “LEARN MORE” and “SHOP NOW”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 3 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.
32 other companies contacted
Loading the homepage contacts 32 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 byrna.co.za, 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
Klaviyo Email Marketing Sms
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on byrna.co.za, including 24 speed issues, 4 SEO issues and 2 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.