Website review, no card needed

alllife.co.za logo

alllife.co.za website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 86 checks

This review found 44 issues worth fixing on alllife.co.za, 12 of them high impact, across 86 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
4.3 s3.9 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20263.9 s
May 30, 20264.0 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20264.0 s
Aug 22, 20264.0 s
Aug 29, 20264.2 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.2 s
Oct 3, 20264.3 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Oct 31, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
354 ms299 msMay 16Oct 31348 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026306 ms
May 23, 2026307 ms
May 30, 2026316 ms
Jun 6, 2026323 ms
Jun 13, 2026323 ms
Jun 20, 2026321 ms
Jun 27, 2026317 ms
Jul 4, 2026313 ms
Jul 11, 2026312 ms
Jul 18, 2026312 ms
Jul 25, 2026310 ms
Aug 1, 2026305 ms
Aug 8, 2026309 ms
Aug 15, 2026315 ms
Aug 22, 2026322 ms
Aug 29, 2026324 ms
Sep 5, 2026325 ms
Sep 12, 2026324 ms
Sep 19, 2026327 ms
Sep 26, 2026335 ms
Oct 3, 2026339 ms
Oct 10, 2026345 ms
Oct 17, 2026348 ms
Oct 24, 2026348 ms
Oct 31, 2026348 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 alllife.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alllife.co.za at 1.1 s1.1 s
  2. alllife.co.za at 2.1 s2.1 s
  3. alllife.co.za at 3.2 s3.2 s
  4. alllife.co.za at 4.2 s4.2 s
  5. alllife.co.za at 5.3 s5.3 s
  6. alllife.co.za at 6.3 s6.3 s
  7. alllife.co.za at 7.4 s7.4 s
  8. alllife.co.za at 8.4 s8.4 s

Speed

16 to fix64
  • Render-blocking requests

    2.4 s

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

  • Font display

    2.0 s

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

  • Use efficient cache lifetimes

    400 ms · 2.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.5 MB and 1.2 s of main-thread time.

  • Mobile performance score: 64

    64/100

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

  • Reduce unused JavaScript

    190 ms · 707 KiB

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

  • Improve image delivery

    758 KiB

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

  • Reduce initial server response time

    623 ms

    Reduce initial server response time. Google estimates savings of 623 ms on a phone.

  • Document request latency

    600 ms

    The HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Google CDN adds 435 ms

    435 ms

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

  • Google Tag Manager adds 454 ms

    454 ms

    Google Tag Manager costs a phone 454 ms of main-thread work and 379 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

    320 ms · 114 KiB

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

  • 11 long tasks on the main thread

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

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,710 HTML elements

    The page has 1,710 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 723 ms

    723 ms

    Your server takes 723 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    41 KiB

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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

Core Web Vitals

10 to fix33
  • 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 FCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Speed Index: 13.8 s

    13.8 s

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

  • Time to Interactive: 21.9 s

    21.9 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 296 ms

    296 ms

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

  • Total Blocking Time: 597 ms

    597 ms

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

    Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You are guaranteed a minimum of R3 Million Life Cover witho…”. Most of its time is element render delay (6.3 s).

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 4.1 MB in 85 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 85 requests on a phone: scripts 1.7 MB (39), images 953 KiB (16) and fonts 827 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    alllife_logo.svg 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).

  • 1 image far larger than shown

    297 KiB

    1 image is downloaded at several times the size a phone draws it, for example All-Life-20-Nov-2024-5D__0901-222-scaled.jpg at 2,560 px wide, shown at 339 px. Resized copies would save about 297 KiB.

  • 1 image in older formats

    1 image (353 KiB) is 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.

  • About 1.2 g of CO₂ per visit

    1.15 g

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

Accessibility

3 to fixGoogle 9296
  • 8 text elements with low contrast

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

  • 4 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 16 H1 headlines

    There are 16 <h1> headlines (“We believe all South Africans should have Life Co…”, “We believe all South Africans should have Life Co…” and “Get Your FREE Quote”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 5 links with vague text

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

  • 43 internal links, 6 external

    The homepage links to 43 pages on alllife.co.za and 6 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Get affordable life insurance in South Africa, even if you’re living with HIV, diabetes or a chronic illness. Get a fre…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “AllLife | Life Insurance for HIV, Diabetes & Chronic Illness”.

  • Canonical URL set

    The canonical URL is https://alllife.co.za/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://alllife.co.za/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://alllife.co.za/llms.txt (74 KiB, 300 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://alllife.co.za/real_people_real_stories and https://alllife.co.za/category/real_people_real_stories all use the title “Real People, Real Stories - AllLife | Life Insurance for HIV, Diabete…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://alllife.co.za/in-the-news has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://alllife.co.za/real_people_real_stories and https://alllife.co.za/category/real_people_real_stories use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

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

  • 4 pages slow to respond

    https://alllife.co.za/solutions/diabetes-life-insurance, https://alllife.co.za/solutions/chronic-life-insurance, https://alllife.co.za/solutions/standard-life-insurance and https://alllife.co.za/solutions/funeral-cover took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97268903&tm=gtm002&Ver=2&mid=62fe866a-2da5-4c45-bd83-c72309d4459b&bo=1&sid=a4fb5be0d7bd11f1aaadcb923badc74a&vid=a4fb8be0d7bd11f18c827fbbcbf8c70e&vids=1&msclkid=N&pi=91.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • About 610 words of copy

    The homepage carries about 610 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get your Free Quote”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact” and “Get your Free Quote”.

  • 13 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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

  • 8 cookies set on arrival

    8

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 alllife.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
WordPress
Framework
Vue.js
Analytics
Google Tag Manager
Hosting
Africa (Pty) Ltd - Host Africa (Pty) Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on alllife.co.za, including 26 speed issues, 3 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