sudatel.sd website review

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

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

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

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

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

2 third-party services load with your homepage (cloudflare.com and preprod-stg.com), adding 35 KiB and 29 ms of main-thread time.

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering the Region with Connectivity”. Most of its time is element render delay (2.2 s).

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 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.

hero-bg.png weighs 623 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example hero-bg.png at 1,440 px wide, shown at 390 px. Resized copies would save about 636 KiB.

Your homepage downloads 3.0 MB in 48 requests on a phone: images 2.0 MB (13), scripts 559 KiB (23) and HTML 209 KiB (2). Under 2 MB keeps phones on slow connections fast.

6 images (1.3 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.

hero-bg.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

6 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.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 24 pages on sudatel.sd and 4 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://sudatel.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.

https://sudatel.sd/en/contact-us and https://sudatel.sd/contact-us all use the title “Contact Us | Sudatel Telecom Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sudatel.sd/en/contact-us and https://sudatel.sd/contact-us use the same meta description. A description written for each page earns more clicks.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://sudatel.sd/en/about-us, whose canonical is https://sudatel.sd/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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.

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

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