Website review, no card needed

mandela.ac.za logo

mandela.ac.za website review

Visit site (opens in a new tab)Reviewed 28 October 202651 issues · 92 checks

This review found 51 issues worth fixing on mandela.ac.za, 21 of them high impact, across 92 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.6 s1.3 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.2 s
May 23, 20262.0 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20261.8 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
357 ms311 msMay 9Oct 24348 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026323 ms
May 16, 2026326 ms
May 23, 2026328 ms
May 30, 2026329 ms
Jun 6, 2026329 ms
Jun 13, 2026329 ms
Jun 20, 2026326 ms
Jun 27, 2026322 ms
Jul 4, 2026319 ms
Jul 11, 2026317 ms
Jul 18, 2026316 ms
Jul 25, 2026317 ms
Aug 1, 2026317 ms
Aug 8, 2026321 ms
Aug 15, 2026325 ms
Aug 22, 2026331 ms
Aug 29, 2026338 ms
Sep 5, 2026338 ms
Sep 12, 2026341 ms
Sep 19, 2026345 ms
Sep 26, 2026347 ms
Oct 3, 2026351 ms
Oct 10, 2026352 ms
Oct 17, 2026349 ms
Oct 24, 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 mandela.ac.za (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mandela.ac.za at 1.3 s1.3 s
  2. mandela.ac.za at 2.7 s2.7 s
  3. mandela.ac.za at 4.0 s4.0 s
  4. mandela.ac.za at 5.3 s5.3 s
  5. mandela.ac.za at 6.6 s6.6 s
  6. mandela.ac.za at 8.0 s8.0 s
  7. mandela.ac.za at 9.3 s9.3 s
  8. mandela.ac.za at 10.6 s10.6 s

Speed

9 to fix52
  • Reduce unused JavaScript

    1.8 s · 487 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    750 ms · 6.3 MB

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

  • Improve image delivery

    3.6 MB

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 45). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Facebook and others), adding 978 KiB and 851 ms of main-thread time.

  • Font display

    550 ms

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

  • Google Tag Manager adds 357 ms

    357 ms

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

  • jQuery CDN adds 279 ms

    279 ms

    jQuery CDN costs a phone 279 ms of main-thread work and 55 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

    150 ms · 59 KiB

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

  • Legacy JavaScript

    150 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

11 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 LCP: 4.6 s

    4.6 s

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Speed Index: 14.7 s

    14.7 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “No student registered with Mandela University may unlawfull…”. Most of its time is element render delay (4.4 s).

  • Time to Interactive: 17.8 s

    17.8 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user INP: 432 ms

    432 ms

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

  • 36 images without width and height

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

  • Total Blocking Time: 301 ms

    301 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user CLS: 0.09

    0.09

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

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

    -25%

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

  • Cumulative Layout Shift: 0.079

    0.079

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

Images and page weight

5 to fix18
  • Page weight: 7.1 MB in 105 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 105 requests on a phone: images 5.8 MB (39), scripts 969 KiB (20) and fonts 245 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    707 KiB

    1 image is downloaded at several times the size a phone draws it, for example Design-1_-Homepage-Website-Banner.png at 1,920 px wide, shown at 360 px. Resized copies would save about 707 KiB.

  • 10 images in older formats

    10 images (3.4 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.

  • 4 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    2.02 g

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

Accessibility

11 to fixGoogle 6783
  • 45 buttons without a name

    45 buttons have no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • 7 tap targets too small

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 37 images without alt text

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

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

    All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate 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.

  • 13 links without text

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

  • ARIA role should be appropriate for the element (16 elements)

    ARIA role should be appropriate for the element: 16 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (16 elements)

    Elements marked as presentational should be consistently ignored: 16 elements on the page fail this check, rated minor by axe-core.

  • No page language

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

  • Headings skip levels

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

5 to fixGoogle 8377
  • No H1 headline

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

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

    No XML sitemap at https://www.mandela.ac.za/sitemap.xml, so Google discovers your pages only by following links.

  • 14 links with vague text

    14 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 set, so this is minor.

  • 45 internal links, 44 external

    The homepage links to 45 pages on mandela.ac.za and 44 external pages.

4 checks passed
  • Meta description: 113 characters

    Your meta description is 113 characters: “Nelson Mandela University is a South African university with campuses in the cities of Port Elizabeth and George.”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Home - Nelson Mandela University”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.mandela.ac.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.

2 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,175 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.mandela.ac.za/Directory, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://www.mandela.ac.za/Giving, https://www.mandela.ac.za/Study-at-Mandela, https://www.mandela.ac.za/Learning-and-Teaching, https://www.mandela.ac.za/Research,-Innovation-and-Internationalisation, https://www.mandela.ac.za/Engagement-and-Transformation and https://www.mandela.ac.za/Leadership-and-Governance and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.mandela.ac.za/Giving, https://www.mandela.ac.za/Study-at-Mandela, https://www.mandela.ac.za/Learning-and-Teaching, https://www.mandela.ac.za/Research,-Innovation-and-Internationalisation, https://www.mandela.ac.za/Engagement-and-Transformation and https://www.mandela.ac.za/Leadership-and-Governance and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.mandela.ac.za/Research,-Innovation-and-Internationalisation, https://www.mandela.ac.za/Engagement-and-Transformation and https://www.mandela.ac.za/About-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 35 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 16 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “$(...).dotdotdot is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 1,057 words of copy

    The homepage carries about 1,057 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more about cookies”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn more” and “Learn more about cookies”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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 mandela.ac.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Tenet

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on mandela.ac.za, including 20 speed issues, 5 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