mtn.co.rw website review

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

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

8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.

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

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

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

About 550 KiB of JavaScript is downloaded but never used on this page.

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

125 KiB could be saved by minifying JavaScript.

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

2 third-party services load with your homepage (Cloudflare CDN and Google Fonts), adding 54 KiB and 4 ms of main-thread time.

6 KiB could be saved by minifying CSS.

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

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EXPLORE NOW”.

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

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

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

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

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

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

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

Your homepage downloads 5.1 MB in 167 requests on a phone: images 2.3 MB (14), scripts 2.0 MB (45) and stylesheets 501 KiB (100). Under 2 MB keeps phones on slow connections fast.

deals-4x4-07-600x851.png weighs 781 KiB. On a phone connection a single image that size takes seconds.

6 images (1.5 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.43 g of CO₂e: 172.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 21 characters: “Personal - MTN Rwanda”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Prestige”, “combo” and “Ni Dilu”). One clear main headline is easier for people and search engines.

Structured data found (Article, ImageObject, Organization and Person) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.mtn.co.rw/wp-content/uploads/2026/02/new-mtn-logo-2.jpg")”.

No XML sitemap at https://www.mtn.co.rw/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 106 pages on mtn.co.rw and 7 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description 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://www.mtn.co.rw/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.mtn.co.rw/momo, https://www.mtn.co.rw/new-voice-and-data, https://www.mtn.co.rw/deal, https://www.mtn.co.rw/how-it-works, https://www.mtn.co.rw/gwamon-2 and https://www.mtn.co.rw/voice-packs-2 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mtn.co.rw/play, https://www.mtn.co.rw/momo, https://www.mtn.co.rw/about and https://www.mtn.co.rw/new-voice-and-data took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 48 found) 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”.

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.

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.

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

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