Website review, no card needed

ooba.co.za logo

ooba.co.za website review

Visit site (opens in a new tab)Reviewed 18 November 202633 issues · 86 checks

This review found 33 issues worth fixing on ooba.co.za, 14 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
3.6 s2.7 sMay 30Nov 142.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.2 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.1 s
Oct 31, 20262.9 s
Nov 7, 20262.9 s
Nov 14, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
296 ms236 msMay 30Nov 14289 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026246 ms
Jun 6, 2026252 ms
Jun 13, 2026247 ms
Jun 20, 2026247 ms
Jun 27, 2026245 ms
Jul 4, 2026243 ms
Jul 11, 2026246 ms
Jul 18, 2026248 ms
Jul 25, 2026252 ms
Aug 1, 2026251 ms
Aug 8, 2026250 ms
Aug 15, 2026252 ms
Aug 22, 2026254 ms
Aug 29, 2026252 ms
Sep 5, 2026252 ms
Sep 12, 2026254 ms
Sep 19, 2026250 ms
Sep 26, 2026252 ms
Oct 3, 2026254 ms
Oct 10, 2026250 ms
Oct 17, 2026251 ms
Oct 24, 2026257 ms
Oct 31, 2026265 ms
Nov 7, 2026275 ms
Nov 14, 2026289 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 ooba.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ooba.co.za at 2.0 s2.0 s
  2. ooba.co.za at 4.1 s4.1 s
  3. ooba.co.za at 6.1 s6.1 s
  4. ooba.co.za at 8.1 s8.1 s
  5. ooba.co.za at 10.2 s10.2 s
  6. ooba.co.za at 12.2 s12.2 s
  7. ooba.co.za at 14.2 s14.2 s
  8. ooba.co.za at 16.3 s16.3 s

Speed

9 to fix36
  • Render-blocking requests

    4.6 s

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

  • Reduce unused JavaScript

    2.9 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Font display

    2.3 s

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.3 s

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

  • 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 2.6 MB and 2.0 s of main-thread time.

  • Google Tag Manager adds 839 ms

    839 ms

    Google Tag Manager costs a phone 839 ms of main-thread work and 867 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 CDN adds 558 ms

    558 ms

    Google CDN costs a phone 558 ms of main-thread work and 1.1 MB 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

    300 ms · 93 KiB

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

  • Use efficient cache lifetimes

    244 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    20 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 88 ms

    88 ms

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

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.

  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get your home sweet home loan Imagine finding the perfect p…”. Most of its time is resource load delay (7.3 s).

  • Speed Index: 19.3 s

    19.3 s

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

  • Time to Interactive: 25.1 s

    25.1 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • 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 LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 220 ms

    220 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

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

    +13%

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

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

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

    -13%

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

  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 153 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 153 requests on a phone: scripts 3.1 MB (67), other files 368 KiB (32) and fonts 235 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9494
  • 6 text elements with low contrast

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

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

    All page content should be contained by landmarks: 15 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.

  • 1 form field without a label

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4 and h2 → h5), 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 18 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

Google 100100
  • 31 internal links, 14 external

    The homepage links to 31 pages on ooba.co.za and 14 external pages.

8 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “Let ooba ‘shop around’ for the best deal on your home loan. Thousands of homeowners have secured finance through ooba.”.

  • One H1 headline

    Your main headline reads: “Get your home sweet home loan”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “ooba Home Loans – South Africa’s Home Finance Experts”.

  • Canonical URL set

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

  • Structured data in place

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

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

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

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

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.ooba.co.za/terms-conditions has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ooba.co.za/calculators/bond-and-transfer-costs-calculator, whose canonical is https://www.ooba.co.za/home-loan/transfer-cost-calculator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages slow to respond

    https://www.ooba.co.za/calculators/bond-and-transfer-costs-calculator, https://www.ooba.co.za/resources, https://www.ooba.co.za/home-loan/prequalify, https://www.ooba.co.za/insurance and https://www.ooba.co.za/privacy-statement took over 3 s to send their HTML from our server.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 867 words of copy

    The homepage carries about 867 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: “APPLY NOW”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact”, “Get a Home Loan” and “Apply Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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
  • 7 trackers load before any consent

    7

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 ooba.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
jQuery
Analytics
Google Tag Manager
Hosting
(Pty) Ltd - Xneelo (Pty) Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ooba.co.za, including 19 speed 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