Website review, no card needed
bluesecurity.co.za website review
Visit site (opens in a new tab)Reviewed 27 October 202635 issues · 86 checks
This review found 35 issues worth fixing on bluesecurity.co.za, 12 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 244 ms |
| May 16, 2026 | 244 ms |
| May 23, 2026 | 247 ms |
| May 30, 2026 | 261 ms |
| Jun 6, 2026 | 258 ms |
| Jun 13, 2026 | 264 ms |
| Jun 20, 2026 | 286 ms |
| Jun 27, 2026 | 269 ms |
| Jul 4, 2026 | 288 ms |
| Jul 11, 2026 | 281 ms |
| Jul 18, 2026 | 262 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 256 ms |
| Aug 8, 2026 | 258 ms |
| Aug 15, 2026 | 278 ms |
| Aug 22, 2026 | 290 ms |
| Aug 29, 2026 | 298 ms |
| Sep 5, 2026 | 295 ms |
| Sep 12, 2026 | 285 ms |
| Sep 19, 2026 | 271 ms |
| Sep 26, 2026 | 259 ms |
| Oct 3, 2026 | 268 ms |
| Oct 10, 2026 | 270 ms |
| Oct 17, 2026 | 276 ms |
| Oct 24, 2026 | 281 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.7 s
1.3 s
2.0 s
2.7 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Render-blocking requests
4.7 s50 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 70). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 969 KiB and 595 ms of main-thread time.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Reduce unused JavaScript
533 KiBAbout 533 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 356 ms
356 msGoogle Tag Manager costs a phone 356 ms of main-thread work and 623 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
234 KiB5 images could be 234 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
208 KiB5 files are served with short cache lifetimes, so returning visitors download them again (208 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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: 186 ms
186 msYour server sent the HTML in 186 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.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FOR PEACE OF MIND UPGRADE TO BLUE SECURITY”. Most of its time is element render delay (2.8 s).
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 233 ms
233 msReal visitors wait 233 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 209 ms
209 msScripts block taps and scrolling for 209 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 244 ms to 281 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-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 130 requests
3.2 MBYour homepage downloads 3.2 MB in 130 requests on a phone: images 1.6 MB (18), scripts 1.2 MB (45) and fonts 216 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
6 KiB1 image is downloaded at several times the size a phone draws it, for example Section2.webp at 1,122 px wide, shown at 360 px. Resized copies would save about 6 KiB.
2 images in older formats
2 images (80 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.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.5 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
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
31 images without alt text
31 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
40 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: 40 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
101 internal links, 7 external
The homepage links to 101 pages on bluesecurity.co.za and 7 external pages.
8 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Experience cutting-edge protection backed by South Africa’s most trusted security experts - Blue Security. Best footpri…”.
One H1 headline
Your main headline reads: “For peace of mind upgrade to Blue Security”.
Title: 60 characters
Your title is a healthy 60 characters: “Blue Security - South Africa’s Most Trusted Security Experts”.
Canonical URL set
The canonical URL is https://bluesecurity.co.za/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://bluesecurity.co.za/sitemap_index.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, 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://bluesecurity.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
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 (1,147 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without an H1
https://bluesecurity.co.za/area-vehicles, https://bluesecurity.co.za/dedicated-vehicles, https://bluesecurity.co.za/community-crime-prevention-unit, https://bluesecurity.co.za/areas-of-operation, https://bluesecurity.co.za/alarm-systems and https://bluesecurity.co.za/access-control-security and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://bluesecurity.co.za/areas-of-operation took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
A 8-field form
Your longest form asks for 8 fields (3 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 705 words of copy
The homepage carries about 705 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Contact Us” and “Sign Up Now”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 5 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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
6Opening 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.
16 other companies contacted
Loading the homepage contacts 16 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 bluesecurity.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Vultr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on bluesecurity.co.za, including 18 speed issues, 1 SEO issue 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.