Website review, no card needed

mtn.sd logo

mtn.sd website review

Visit site (opens in a new tab)Reviewed 25 October 202630 issues · 79 checks

This review found 30 issues worth fixing on mtn.sd, 11 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.4 s5.3 sMay 2Oct 175.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.8 s
May 9, 20265.8 s
May 16, 20265.8 s
May 23, 20266.0 s
May 30, 20266.1 s
Jun 6, 20266.0 s
Jun 13, 20266.0 s
Jun 20, 20265.9 s
Jun 27, 20265.8 s
Jul 4, 20266.0 s
Jul 11, 20265.9 s
Jul 18, 20265.9 s
Jul 25, 20265.9 s
Aug 1, 20265.9 s
Aug 8, 20266.0 s
Aug 15, 20266.0 s
Aug 22, 20266.2 s
Aug 29, 20266.3 s
Sep 5, 20266.2 s
Sep 12, 20266.3 s
Sep 19, 20266.2 s
Sep 26, 20266.0 s
Oct 3, 20265.9 s
Oct 10, 20265.6 s
Oct 17, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
202 ms159 msMay 2Oct 17173 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026197 ms
May 9, 2026196 ms
May 16, 2026197 ms
May 23, 2026189 ms
May 30, 2026180 ms
Jun 6, 2026177 ms
Jun 13, 2026177 ms
Jun 20, 2026173 ms
Jun 27, 2026175 ms
Jul 4, 2026172 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026173 ms
Aug 1, 2026178 ms
Aug 8, 2026177 ms
Aug 15, 2026172 ms
Aug 22, 2026169 ms
Aug 29, 2026167 ms
Sep 5, 2026164 ms
Sep 12, 2026172 ms
Sep 19, 2026166 ms
Sep 26, 2026169 ms
Oct 3, 2026170 ms
Oct 10, 2026173 ms
Oct 17, 2026173 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mtn.sd (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mtn.sd at 0.5 s0.5 s
  2. mtn.sd at 1.0 s1.0 s
  3. mtn.sd at 1.5 s1.5 s
  4. mtn.sd at 2.0 s2.0 s
  5. mtn.sd at 2.5 s2.5 s
  6. mtn.sd at 3.0 s3.0 s
  7. mtn.sd at 3.5 s3.5 s
  8. mtn.sd at 4.0 s4.0 s

Speed

7 to fix69
  • Render-blocking requests

    1.6 s

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

  • Improve image delivery

    5.1 MB

    8 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    630 ms · 150 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, superbo.ai and socket.io and others), adding 1.8 MB and 133 ms of main-thread time.

  • superbo.ai adds 13 ms

    13 ms

    superbo.ai costs a phone 13 ms of main-thread work and 1.0 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.

  • sheenvalue.com adds 1 ms

    1 ms

    sheenvalue.com costs a phone 1 ms of main-thread work and 592 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.

  • Reduce unused CSS

    180 ms · 46 KiB

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

  • Chained critical requests

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 529 ms of it running JavaScript. That is comfortably low.

  • Server response: 324 ms

    324 ms

    Your server sent the HTML in 324 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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-user LCP: 5.5 s

    5.5 s

    Real visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Landing Popup”.

  • Time to Interactive: 8.7 s

    8.7 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

6 checks passed
  • Real-user INP: 163 ms

    163 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.019

    0.019

    The layout barely moves while loading (CLS 0.019, good is under 0.1).

  • Total Blocking Time: 57 ms

    57 ms

    Scripts block the page for only 57 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 7.7 MB in 95 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 95 requests on a phone: images 6.2 MB (22), other files 610 KiB (17) and scripts 559 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.19 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10099
  • All page content should be contained by landmarks (32 elements)

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10081
  • Title is short (9 characters)

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“About”, “Business Services” and “Personal Services”). One clear main headline is easier for people and search engines.

  • Meta description is long (249 characters)

    Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 17 internal links, 5 external

    The homepage links to 17 pages on mtn.sd and 5 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.mtn.sd/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mtn.sd/sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

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

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (327 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix80
  • 9 pages point its canonical at the homepage

    https://www.mtn.sd/personal-services, https://www.mtn.sd/business-services, https://www.mtn.sd/about, https://www.mtn.sd/blogs, https://www.mtn.sd/faq and https://www.mtn.sd/terms and 3 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 1 page without a meta description

    https://www.mtn.sd/blogs/A-al-manassa has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.mtn.sd/personal-services, https://www.mtn.sd/business-services, https://www.mtn.sd/blogs, https://www.mtn.sd/faq and https://www.mtn.sd/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.mtn.sd/personal-services, https://www.mtn.sd/business-services, https://www.mtn.sd/blogs, https://www.mtn.sd/faq, https://www.mtn.sd/terms and https://www.mtn.sd/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 9 internal pages checked

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

4 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 4 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

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

  • About 375 words of copy

    The homepage carries about 375 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 6 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mtn.sd, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on mtn.sd, including 14 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25