Website review, no card needed
pbsa.co.za website review
Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 80 checks
This review found 32 issues worth fixing on pbsa.co.za, 7 of them high impact, across 80 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 11, 2026 | 5.8 s |
| Jul 18, 2026 | 6.0 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 6.1 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.7 s |
| Oct 3, 2026 | 5.8 s |
| Oct 24, 2026 | 5.7 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
Speed
Render-blocking requests
4.7 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Use efficient cache lifetimes
1.1 s · 1.7 MB103 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 766 KiBAbout 766 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and mjt.lu and others), adding 604 KiB and 622 ms of main-thread time.
Google Tag Manager adds 596 ms
596 msGoogle Tag Manager costs a phone 596 ms of main-thread work and 469 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.
Improve image delivery
580 KiB26 images could be 580 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
450 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 457 ms
457 msScripts block taps and scrolling for 457 ms in total while the page loads. Good is under 200 ms.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For more than two decades, PBSA has helped businesses acros…”. Most of its time is element render delay (6.5 s).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.8 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.03
0.03The layout barely moves while loading (CLS 0.03, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 123 requests
3.1 MBYour homepage downloads 3.1 MB in 123 requests on a phone: scripts 1.6 MB (38), images 1.3 MB (41) and stylesheets 160 KiB (34). Under 2 MB keeps phones on slow connections fast.
26 images below the first screen load straight away
26 images further down the page (976 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
17 images in older formats
17 images (758 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.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
256 internal links, 6 external
The homepage links to 256 pages on pbsa.co.za and 6 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Powering Businesses through Smart Automation. PBSA is a leading distributor of advanced automation equipment and techno…”.
One H1 headline
Your main headline reads: “Powering Business through Smart Automation (PBSA)”.
Title: 51 characters
Your title is a healthy 51 characters: “Powering Businesses through Smart Automation | PBSA”.
Canonical URL set
The canonical URL is https://pbsa.co.za/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, Organization, WebPage 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://pbsa.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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,629 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pbsa.co.za/llms.txt (62 KiB, 263 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
15 pages slow to respond
https://pbsa.co.za/about-us, https://pbsa.co.za/automation/healthcare-automation, https://pbsa.co.za/automation/healthcare-automation/health-automation-storage/apd-athos-dosys-medication-cabinet-storage, https://pbsa.co.za/automation/healthcare-automation/health-automation-storage/apd-athos-dosys-rfid-smart-cabinet-storage, https://pbsa.co.za/automation/healthcare-automation/health-automation-storage/apd-athos-storage-horizontal-carousel-storage and https://pbsa.co.za/automation/healthcare-automation/health-automation-storage/apd-athos-vertical-carousel-storage and 9 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 112 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
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 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 639 words of copy
The homepage carries about 639 words of visible text.
8 checks passed
7 calls to action
The homepage has 7 calls to action, for example “SHOP”, “CONTACT” and “Start search”.
2 short forms
2 short forms (6 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 24 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
10 other companies contacted
Loading the homepage contacts 10 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 pbsa.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
- Hosting
- (Pty) Ltd - Xneelo (Pty) Ltd
Company
- Headquarters
- Midrand
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on pbsa.co.za, including 16 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.