savannah.co.za website review

56 files are served with short cache lifetimes, so returning visitors download them again (6.0 MB).

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

About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

About 945 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

1 long task block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.

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

Desktop scores 76 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

1 third-party service load with your homepage (Google Fonts), adding 88 KiB and 0 ms of main-thread time.

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.

3 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At the nexus of the health & wellness and cosmetics markets…”. Most of its time is element render delay (4.2 s).

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

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

4 images have no width and height attributes, so the layout jumps as each one loads.

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

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.

Your homepage downloads 6.1 MB in 64 requests on a phone: media 3.7 MB (2), scripts 1.5 MB (18) and images 561 KiB (14). Under 2 MB keeps phones on slow connections fast.

4 images (201 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.

3 images further down the page (146 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

ARIA tab nodes must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Your title is only 8 characters: “Savannah”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 7 characters: “Welcome”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Welcome to Savannah” and “LATEST NEWS”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.savannah.co.za")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at savannah.co.za/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 28 pages on savannah.co.za and 2 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

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

Your homepage links to https://savannah.co.za/nutrtition, which answers with an error. Visitors hit a dead end and search engines drop it.

https://savannah.co.za/food-and-beverage, https://savannah.co.za/personal-care, https://savannah.co.za/nutrition, https://savannah.co.za/home-care-industrial, https://savannah.co.za/a-shift-towards-bolder-more-expressive-tastes and https://savannah.co.za/dairy-proteins-powering-nutrition-change have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://savannah.co.za/food-and-beverage, whose canonical is https://savannah.co.za/food-and-beverage/www.savannah.co.za/food-and-beverage. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://savannah.co.za/home-care-industrial, https://savannah.co.za/a-shift-towards-bolder-more-expressive-tastes and https://savannah.co.za/dairy-proteins-powering-nutrition-change took over 3 s to send their HTML from our server.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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.

The homepage carries about 451 words of visible text.

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