Website review, no card needed

abcsecurity.co.za logo

abcsecurity.co.za website review

Visit site (opens in a new tab)Reviewed 18 October 202621 issues · 73 checks

This review found 21 issues worth fixing on abcsecurity.co.za, 5 of them high impact, across 73 checks. The most urgent: font display. 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
3.3 s869 msMay 2Sep 261.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
Jun 6, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Aug 1, 20261.8 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.4 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.2 s

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 abcsecurity.co.za (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abcsecurity.co.za at 0.6 s0.6 s
  2. abcsecurity.co.za at 1.1 s1.1 s
  3. abcsecurity.co.za at 1.6 s1.6 s
  4. abcsecurity.co.za at 2.2 s2.2 s
  5. abcsecurity.co.za at 2.8 s2.8 s
  6. abcsecurity.co.za at 3.3 s3.3 s
  7. abcsecurity.co.za at 3.9 s3.9 s
  8. abcsecurity.co.za at 4.4 s4.4 s

Speed

4 to fix70
  • Font display

    1.4 s

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

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 950 ms.

  • Reduce unused JavaScript

    300 ms · 69 KiB

    About 69 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Improve image delivery

    188 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 192 KiB and 134 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    8 KiB

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

1 checks passed
  • Main-thread work: 0.3 s

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Local Security Company Top Security Solutions for Stel…”.

  • Cumulative Layout Shift: 0.258

    0.258

    The layout shifts by 0.258 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 3.9 s

    3.9 s

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

  • Time to Interactive: 4.5 s

    4.5 s

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

8 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: 1.2 s

    1.2 s

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

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 626 ms

    626 ms

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

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

    -41%

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Total Blocking Time: 27 ms

    27 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    51 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-hero2.webp at 1,832 px wide, shown at 468 px. Resized copies would save about 51 KiB.

  • About 0.2 g of CO₂ per visit

    0.15 g

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

3 checks passed
  • Page weight: 543 KiB in 26 requests

    543 KiB

    Your homepage downloads 543 KiB in 26 requests on a phone: images 318 KiB (14), scripts 192 KiB (2) and fonts 25 KiB (6). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

Accessibility

2 to fixGoogle 8695
  • 2 text elements with low contrast

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

5 to fixGoogle 10078
  • Title is short (19 characters)

    Your title is only 19 characters: “Home - ABC Security”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

    Your meta description is only 60 characters: “Top Security Solutions for Stellenbosch and the Western Cape”. 70 to 160 characters is enough to sell the click.

  • No robots.txt

    There is no robots.txt at abcsecurity.co.za/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 19 internal links, 5 external

    The homepage links to 19 pages on abcsecurity.co.za and 5 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Your Local Security Company”.

  • Canonical URL set

    The canonical URL is https://abcsecurity.co.za/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://abcsecurity.co.za/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.

  • No llms.txt

    There is no https://abcsecurity.co.za/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix74
  • 1 linked page is broken

    Your homepage links to https://abcsecurity.co.za/faq, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 9 pages share a meta description

    https://abcsecurity.co.za/meet-the-team, https://abcsecurity.co.za/community, https://abcsecurity.co.za/gallery, https://abcsecurity.co.za/join-our-team, https://abcsecurity.co.za/contact and https://abcsecurity.co.za/armed-response and 3 others use the same meta description. A description written for each page earns more clicks.

  • 5 pages with very little text

    https://abcsecurity.co.za/meet-the-team, https://abcsecurity.co.za/gallery, https://abcsecurity.co.za/join-our-team, https://abcsecurity.co.za/opb-project and https://abcsecurity.co.za/contact 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.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 10 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 10 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

    13 of 13 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
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 299 words of copy

    The homepage carries about 299 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN OUR TEAM” and “CLICK TO REQUEST A QUOTE”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “JOIN OUR TEAM”, “CLICK TO REQUEST A QUOTE” and “CLICK TO CALL 021 887 4777”.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 4 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 abcsecurity.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on abcsecurity.co.za, including 8 speed issues, 5 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