kwv.co.za website review

72 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.1 s.

About 893 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics and others), adding 1.4 MB and 789 ms of main-thread time.

Google Tag Manager costs a phone 788 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.

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

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

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

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

13 KiB could be saved by minifying JavaScript.

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

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 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KWV Brands”. Most of its time is resource load delay (7.4 s).

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

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

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

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

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

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

Your homepage downloads 4.5 MB in 202 requests on a phone: images 2.1 MB (18), scripts 1.9 MB (106) and stylesheets 255 KiB (67). Under 2 MB keeps phones on slow connections fast.

6 images (1.0 MB) 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.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Structured data found (Article, BreadcrumbList, ImageObject and Organization) but with 2 problems, for example “Article: missing datePublished”.

1 link has no real href, so search engines can't follow it.

The homepage links to 159 pages on kwv.co.za and 3 external pages.

There is no /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.

/our-company/our-history and /our-company/our-history-mobile all use the title “Our History - KWV”. Search engines can't tell which page to show for a search, so each competes with the others.

/our-company/global-distribution, /our-company/sustainability, /our-company/awards and /our-company/executive-team have no meta description, so Google writes the search snippet from whatever text it finds.

/our-company/about-us and /our-company/careers-at-kwv took over 3 s to send their HTML from our server.

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

4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 images are served at too low a resolution for sharp phone screens.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

kwv.co.za has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 367 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

Opening the homepage sets 11 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.