koodoo.co.za website review

The page has 8,286 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

A phone's processor spends 4.1 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, loox.io and TikTok and others), adding 1.1 MB and 802 ms of main-thread time.

6 images could be 161 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.

About 385 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.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

Google Tag Manager costs a phone 227 ms of main-thread work and 329 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.

About 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 523 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Grand Theft Auto VI (PS5) - Code in Box - KOODOO”.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 252 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 262 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 3.0 MB in 234 requests on a phone: scripts 1.3 MB (85), other files 749 KiB (98) and images 660 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

14 elements hidden from screen readers can still receive keyboard focus.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“KOODOO KOODOO” and “Grand Theft Auto VI (PS5) - Code in Box”). One clear main headline is easier for people and search engines.

The homepage links to 513 pages on koodoo.co.za and 8 external pages.

We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'innerHTML')”.

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 25 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.