Website review, no card needed

etv.co.za logo

etv.co.za website review

Visit site (opens in a new tab)Reviewed 30 October 202646 issues · 83 checks

This review found 46 issues worth fixing on etv.co.za, 15 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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
4.5 s3.9 sMay 9Oct 244.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.2 s
May 23, 20264.1 s
May 30, 20264.2 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20264.1 s
Jun 27, 20264.1 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20264.0 s
Jul 25, 20264.0 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.2 s
Oct 3, 20264.2 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Oct 24, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
208 ms165 msMay 9Oct 24203 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026175 ms
May 16, 2026171 ms
May 23, 2026170 ms
May 30, 2026172 ms
Jun 6, 2026172 ms
Jun 13, 2026173 ms
Jun 20, 2026174 ms
Jun 27, 2026174 ms
Jul 4, 2026174 ms
Jul 11, 2026174 ms
Jul 18, 2026178 ms
Jul 25, 2026180 ms
Aug 1, 2026186 ms
Aug 8, 2026189 ms
Aug 15, 2026188 ms
Aug 22, 2026184 ms
Aug 29, 2026184 ms
Sep 5, 2026186 ms
Sep 12, 2026189 ms
Sep 19, 2026194 ms
Sep 26, 2026195 ms
Oct 3, 2026195 ms
Oct 10, 2026197 ms
Oct 17, 2026198 ms
Oct 24, 2026203 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 etv.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. etv.co.za at 0.4 s0.4 s
  2. etv.co.za at 0.8 s0.8 s
  3. etv.co.za at 1.1 s1.1 s
  4. etv.co.za at 1.5 s1.5 s
  5. etv.co.za at 1.9 s1.9 s
  6. etv.co.za at 2.3 s2.3 s
  7. etv.co.za at 2.6 s2.6 s
  8. etv.co.za at 3.0 s3.0 s

Speed

9 to fix58
  • Use efficient cache lifetimes

    2.5 s · 2.2 MB

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

  • Improve image delivery

    1.6 s · 1.6 MB

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

  • Reduce unused JavaScript

    1.1 s · 155 KiB

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

  • Mobile performance score: 58

    58/100

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

  • Render-blocking requests

    900 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and Twitter Online Conversion Tracking and others), adding 906 KiB and 538 ms of main-thread time.

  • Reduce unused CSS

    310 ms · 47 KiB

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

  • Facebook adds 316 ms

    316 ms

    Facebook costs a phone 316 ms of main-thread work and 338 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.

  • Font display

    300 ms

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

  • Minify JavaScript

    150 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    22 KiB

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

13 to fix0
  • 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: 4.9 s

    4.9 s

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

  • Real-user CLS: 0.37

    0.37

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

  • Largest Contentful Paint: 10.8 s

    10.8 s

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

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Real-user INP: 239 ms

    239 ms

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.169

    0.169

    The layout shifts by 0.169 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 4.2 s

    4.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Total Blocking Time: 266 ms

    266 ms

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

  • 4 images without width and height

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

Images and page weight

4 to fix31
  • Page weight: 20.0 MB in 108 requests

    20.0 MB

    Your homepage downloads 20.0 MB in 108 requests on a phone: media 17.0 MB (3), images 1.9 MB (29) and scripts 727 KiB (60). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    546 KiB

    4 images are downloaded at several times the size a phone draws them, for example jurassic_world_fallen_kingdom.png at 560 px wide, shown at 117 px. Resized copies would save about 546 KiB.

  • 9 images in older formats

    9 images (1.9 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.

  • An image on the first screen is lazy-loaded

    1920x1080_c.jpg 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).

  • About 5.7 g of CO₂ per visit

    5.67 g

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

Accessibility

4 to fixGoogle 9295
  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

    14 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8565
  • 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 (11 characters)

    Your title is only 11 characters: “Home | e.tv”. 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • No X (Twitter) card tag

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

  • 56 internal links, 7 external

    The homepage links to 56 pages on etv.co.za and 7 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.etv.co.za/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.etv.co.za/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix85
  • 12 pages without a meta description

    https://www.etv.co.za/shows, https://www.etv.co.za/movies, https://www.etv.co.za/scoop, https://www.etv.co.za/magazine/pages, https://www.etv.co.za/ecommunity and https://www.etv.co.za/Snap-e_Page and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

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

  • 4 pages without an H1

    https://www.etv.co.za/magazine/pages, https://www.etv.co.za/ecommunity, https://www.etv.co.za/Snap-e_Page and https://www.etv.co.za/eVODpage have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.etv.co.za/magazine/pages, https://www.etv.co.za/Land_of_Mills_Money and https://www.etv.co.za/tvguide 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.

  • 2 pages slow to respond

    https://www.etv.co.za/EmziniPage and https://www.etv.co.za/tvguide took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

Best practices

1 to fixGoogle 8893
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    59 of 66 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 social proof

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

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

  • Only about 147 words

    The homepage has only about 147 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact us”, “Outcome of Request & Of Fees Payable” and “Request for Access to Record”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) Ads (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 35 other companies contacted

    Loading the homepage contacts 35 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 etv.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on etv.co.za, including 22 speed issues, 6 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