Website review, no card needed

etl.co.ls logo

etl.co.ls website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 73 checks

This review found 31 issues worth fixing on etl.co.ls, 11 of them high impact, across 73 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
3.9 s533 msMay 9Oct 103.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 2026952 ms
May 16, 2026966 ms
May 23, 2026973 ms
May 30, 20261.0 s
Jun 6, 2026975 ms
Jun 13, 2026985 ms
Jun 20, 2026975 ms
Jun 27, 2026922 ms
Jul 4, 2026925 ms
Jul 11, 2026940 ms
Jul 18, 2026969 ms
Oct 10, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
183 ms118 msMay 30Oct 10175 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026125 ms
Jun 6, 2026125 ms
Jun 13, 2026141 ms
Jun 20, 2026141 ms
Jun 27, 2026141 ms
Jul 4, 2026141 ms
Jul 11, 2026141 ms
Jul 18, 2026141 ms
Oct 10, 2026175 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 etl.co.ls (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. etl.co.ls at 1.4 s1.4 s
  2. etl.co.ls at 2.7 s2.7 s
  3. etl.co.ls at 4.1 s4.1 s
  4. etl.co.ls at 5.4 s5.4 s
  5. etl.co.ls at 6.8 s6.8 s
  6. etl.co.ls at 8.1 s8.1 s
  7. etl.co.ls at 9.5 s9.5 s
  8. etl.co.ls at 10.8 s10.8 s

Speed

5 to fix59
  • Render-blocking requests

    4.8 s

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

  • Font display

    1.6 s

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

  • Improve image delivery

    800 ms · 215 KiB

    8 images could be 215 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • Mobile performance score: 59

    59/100

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

  • Reduce unused CSS

    750 ms · 128 KiB

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

  • Reduce unused JavaScript

    104 KiB

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

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • 1 third-party service on the page

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 253 ms

    253 ms

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

Core Web Vitals

6 to fix69
  • Speed Index: 12.7 s

    12.7 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Lesotho's Best Data Network”. Most of its time is resource load delay (5.0 s).

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • Largest content (LCP) got 134% slower for real visitors

    +134%

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0.061

    0.061

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 2 images in older formats

    2 images (115 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 below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.50 g

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

2 checks passed
  • Page weight: 1.8 MB in 106 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 106 requests on a phone: images 907 KiB (20), scripts 394 KiB (34) and stylesheets 268 KiB (44). That is a lean page.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8891
  • 17 tap targets too small

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

  • 4 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

7 to fixGoogle 8561
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (28 characters)

    Your title is only 28 characters: “ETL – Econet Telecom Lesotho”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

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

  • No robots.txt

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

  • 1 link with vague text

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

  • No X (Twitter) card tag

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

  • 76 internal links, 16 external

    The homepage links to 76 pages on etl.co.ls and 16 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://etl.co.ls/.

  • XML sitemap found

    Your XML sitemap is reachable at https://etl.co.ls/sitemap.xml.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://etl.co.ls/mobile-data, https://etl.co.ls/mobile-voice, https://etl.co.ls/home-internet, https://etl.co.ls/home-internet-packages, https://etl.co.ls/digital-services and https://etl.co.ls/roaming and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://etl.co.ls/mobile-data, https://etl.co.ls/mobile-voice, https://etl.co.ls/home-internet, https://etl.co.ls/home-internet-packages, https://etl.co.ls/digital-services and https://etl.co.ls/business-solutions and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://etl.co.ls/mobile-voice, https://etl.co.ls/home-internet, https://etl.co.ls/home-internet-packages, https://etl.co.ls/digital-services, https://etl.co.ls/roaming and https://etl.co.ls/business-solutions and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 19 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    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 analytics detected

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

  • 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 573 words of copy

    The homepage carries about 573 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Apply for WIFI PLUS”, “Call” and “Visit an Econet Shop”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 2 trust badges.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 etl.co.ls, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Telecom Lesotho

Company

Headquarters
Maseru

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on etl.co.ls, including 11 speed issues, 7 SEO issues and 2 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