Website review, no card needed
abc.co.za website review
Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 84 checks
This review found 31 issues worth fixing on abc.co.za, 16 of them high impact, across 84 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
81B- #39,672 of 117,548 reviewed websitesbeats 61%
- #26,538 of 66,918 online storesbeats 54%
- #504 of 2,698 WooCommerce storesbeats 77%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 5.2 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.7 s |
| Oct 31, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 132 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 130 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 132 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 151 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
Render-blocking requests
4.2 s63 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Reduce unused JavaScript
600 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, leadconnectorhq.com and Facebook and others), adding 2.5 MB and 824 ms of main-thread time.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
759 KiB5 images could be 759 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 430 ms
430 msGoogle Tag Manager costs a phone 430 ms of main-thread work and 720 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.
leadconnectorhq.com adds 155 ms
155 msleadconnectorhq.com costs a phone 155 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.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
202 KiB5 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
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: 516 ms
516 msYour server sent the HTML in 516 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.
Real-user LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 18.6 s
18.6 sThe page becomes fully interactive after 18.6 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “South Africa’s contractor and equipment supplier to the bio…”. Most of its time is element render delay (4.5 s).
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 96% slower for real visitors
+96%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 267 ms
267 msScripts block taps and scrolling for 267 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 132 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 151 ms
151 msReal visitors wait 151 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 4.5 MB in 247 requests
4.5 MBYour homepage downloads 4.5 MB in 247 requests on a phone: scripts 2.6 MB (125), images 1.4 MB (10) and stylesheets 258 KiB (82). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
15XPC-PTO-Copy-scaled.jpeg.webp weighs 645 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
551 KiB1 image is downloaded at several times the size a phone draws it, for example 15XPC-PTO-Copy-scaled.jpeg.webp at 2,560 px wide, shown at 326 px. Resized copies would save about 551 KiB.
1 image in older formats
1 image (141 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.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 151.9 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
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
126 internal links, 8 external
The homepage links to 126 pages on abc.co.za and 8 external pages.
8 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Africa Biomass Company supplies wood chippers, mulchers and earth-moving equipment across South Africa, plus woodchips,…”.
One H1 headline
Your main headline reads: “Africa Biomass Company”.
Title: 46 characters
Your title is a healthy 46 characters: “Wood Chippers, Mulchers & Stump Grinders | ABC”.
Canonical URL set
The canonical URL is https://abc.co.za/.
Structured data in place
Structured data found: ImageObject, Organization, Place, WebPage and WebSite.
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://abc.co.za/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://abc.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,366 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages slow to respond
https://abc.co.za/product-category/bandit/horizontal-wood-grinders, https://abc.co.za/earthmoving-equipment-motor-graders, https://abc.co.za/earthmoving-equipment, https://abc.co.za/pre-owned-equipment, https://abc.co.za/brands and https://abc.co.za/brands/bandit took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 57 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
3 small tap targets
3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,136 words of copy
The homepage carries about 1,136 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
5 calls to action
The homepage has 5 calls to action, for example “Contact us”, “Learn More” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 42 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 8 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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 Meta Pixel (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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 1 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.
14 other companies contacted
Loading the homepage contacts 14 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 abc.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 © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Technologies PTY LTD - Telasera Technologies PTY LTD
Company
- Headquarters
- Worcester
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on abc.co.za, including 19 speed issues, 1 SEO issue 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.