Website review, no card needed

ensafrica.com logo

ensafrica.com website review

Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 81 checks

This review found 41 issues worth fixing on ensafrica.com, 13 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
2.0 s1.2 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
102 ms87 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202689 ms
May 16, 202691 ms
May 23, 202693 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202693 ms
Jun 20, 202694 ms
Jun 27, 202693 ms
Jul 4, 202693 ms
Jul 11, 202695 ms
Jul 18, 202697 ms
Jul 25, 202697 ms
Aug 1, 2026100 ms
Aug 8, 202697 ms
Aug 15, 202693 ms
Aug 22, 202693 ms
Aug 29, 202690 ms
Sep 5, 202694 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 202698 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202692 ms
Oct 24, 202690 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 ensafrica.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ensafrica.com at 1.1 s1.1 s
  2. ensafrica.com at 2.3 s2.3 s
  3. ensafrica.com at 3.4 s3.4 s
  4. ensafrica.com at 4.6 s4.6 s
  5. ensafrica.com at 5.7 s5.7 s
  6. ensafrica.com at 6.8 s6.8 s
  7. ensafrica.com at 8.0 s8.0 s
  8. ensafrica.com at 9.1 s9.1 s

Speed

8 to fix60
  • Reduce unused JavaScript

    3.3 s · 762 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Use efficient cache lifetimes

    700 ms · 681 KiB

    44 files are served with short cache lifetimes, so returning visitors download them again (681 KiB).

  • Mobile performance score: 60

    60/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.1 MB and 593 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 56 KiB

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

  • Google CDN adds 249 ms

    249 ms

    Google CDN costs a phone 249 ms of main-thread work and 701 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.

  • Improve image delivery

    276 KiB

    2 images could be 276 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 long tasks on the main thread

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

  • Minify CSS

    150 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 611 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

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

  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (5.5 s).

  • Speed Index: 11.5 s

    11.5 s

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

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Real-user TTFB: 871 ms

    871 ms

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

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Total Blocking Time: 178 ms

    178 ms

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

  • Cumulative Layout Shift: 0.078

    0.078

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

Images and page weight

1 to fix67
  • Page weight: 2.2 MB in 94 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 94 requests on a phone: scripts 1.3 MB (18), images 873 KiB (30) and stylesheets 76 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

Accessibility

7 to fixGoogle 7786
  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (7 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 1 link without text

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

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

SEO

6 to fixGoogle 8570
  • No H1 headline

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

  • Title is short (10 characters)

    Your title is only 10 characters: “ENS - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (187 characters)

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

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'i', ..." "email": info@ENSaf"... is not va)”.

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

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

  • 23 internal links, 6 external

    The homepage links to 23 pages on ensafrica.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.ensafrica.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.ensafrica.com/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.ensafrica.com/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

4 to fix64
  • 1 linked page is broken

    Your homepage links to https://www.ensafrica.com/enside/report, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://www.ensafrica.com/people, https://www.ensafrica.com/expertise, https://www.ensafrica.com/videos, https://www.ensafrica.com/subscribe, https://www.ensafrica.com/trainees and https://www.ensafrica.com/access-to-information have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.ensafrica.com/privacy-policy, https://www.ensafrica.com/enside/travel and https://www.ensafrica.com/enside/personal use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.ensafrica.com/experiens, https://www.ensafrica.com/enside/travel and https://www.ensafrica.com/enside/personal have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.ensafrica.com/privacy-policy, https://www.ensafrica.com/subscribe, https://www.ensafrica.com/trainees, https://www.ensafrica.com/enside/travel, https://www.ensafrica.com/enside/personal and https://www.ensafrica.com/access-to-information 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.

  • 4 pages slow to respond

    https://www.ensafrica.com/about-us, https://www.ensafrica.com/experiens, https://www.ensafrica.com/expertise and https://www.ensafrica.com/awards took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • 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 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 11 small tap targets

    11 of 14 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 “reCAPTCHA placeholder element must be an element or id”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • Only about 41 words

    The homepage has only about 41 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.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “contact us” and “subscribe”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Microsoft Clarity
Hosting
IS

Company

Founded
1905

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on ensafrica.com, including 15 speed issues, 6 SEO issues and 3 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