mweb.co.za website review

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

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

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

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

Reduce initial server response time. Google estimates savings of 818 ms on a phone.

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Google Maps costs a phone 160 ms of main-thread work and 393 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.

Your server takes 918 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

8 third-party services load with your homepage (Google Maps, TikTok and connexone.co.uk and others), adding 837 KiB and 436 ms of main-thread time.

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

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

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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

Your 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 “Better Internet. Proven.”.

Real visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 2.1 MB in 96 requests on a phone: scripts 1.7 MB (45), images 318 KiB (15) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.

5 images (249 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.

1 image further down the page (87 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

2 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

4 frames have no title, so screen-reader users cannot tell what they contain.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 8 <h1> headlines (“Better Starts Here”, “Better Internet” and “Better Experience”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 37 pages on mweb.co.za and 18 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

https://www.mweb.co.za/web-hosting/capped and https://www.mweb.co.za/web-hosting all use the title “Mweb Capped Hosting”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mweb.co.za/fibre and https://www.mweb.co.za/business-fibre use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mweb.co.za/web-hosting, whose canonical is https://www.mweb.co.za/web-hosting/capped. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mweb.co.za/premium-mailbox and https://www.mweb.co.za/web-hosting took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “useAuth: No JWT and RT received”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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 319 words of visible text.

Before a visitor clicks anything, the page loads Microsoft Clarity (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.

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