Website review, no card needed

juta.co.za logo

juta.co.za website review

Visit site (opens in a new tab)Reviewed 4 November 202653 issues · 87 checks

This review found 53 issues worth fixing on juta.co.za, 24 of them high impact, across 87 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
5.3 s3.8 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.1 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20264.8 s
Jun 13, 20265.0 s
Jun 20, 20265.1 s
Jun 27, 20265.1 s
Jul 4, 20264.8 s
Jul 11, 20264.5 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.5 s
Aug 8, 20264.6 s
Aug 15, 20264.8 s
Aug 22, 20264.8 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.6 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.3 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Oct 31, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
283 ms212 msMay 16Oct 31235 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026259 ms
May 23, 2026246 ms
May 30, 2026253 ms
Jun 6, 2026235 ms
Jun 13, 2026240 ms
Jun 20, 2026246 ms
Jun 27, 2026235 ms
Jul 4, 2026235 ms
Jul 11, 2026227 ms
Jul 18, 2026220 ms
Jul 25, 2026242 ms
Aug 1, 2026253 ms
Aug 8, 2026260 ms
Aug 15, 2026266 ms
Aug 22, 2026255 ms
Aug 29, 2026252 ms
Sep 5, 2026254 ms
Sep 12, 2026252 ms
Sep 19, 2026259 ms
Sep 26, 2026275 ms
Oct 3, 2026269 ms
Oct 10, 2026271 ms
Oct 17, 2026259 ms
Oct 24, 2026243 ms
Oct 31, 2026235 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 juta.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. juta.co.za at 1.5 s1.5 s
  2. juta.co.za at 3.0 s3.0 s
  3. juta.co.za at 4.5 s4.5 s
  4. juta.co.za at 6.0 s6.0 s
  5. juta.co.za at 7.6 s7.6 s
  6. juta.co.za at 9.1 s9.1 s
  7. juta.co.za at 10.6 s10.6 s
  8. juta.co.za at 12.1 s12.1 s

Speed

11 to fix34
  • Use efficient cache lifetimes

    30.6 s · 13.3 MB

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

  • Reduce unused JavaScript

    12.2 s · 2.3 MB

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

  • Improve image delivery

    8.2 s · 1.9 MB

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

  • Reduce unused CSS

    1.8 s · 324 KiB

    About 324 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Mobile performance score: 34

    34/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, LivePerson and Facebook and others), adding 2.3 MB and 878 ms of main-thread time.

  • Render-blocking requests

    700 ms

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

  • Main-thread work: 4.0 s

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

  • Google Tag Manager adds 346 ms

    346 ms

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

  • 14 long tasks on the main thread

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

  • LivePerson adds 212 ms

    212 ms

    LivePerson costs a phone 212 ms of main-thread work and 1.3 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.

  • Legacy JavaScript

    39 KiB

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

1 checks passed
  • 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: 5.0 s

    5.0 s

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

  • Real-user CLS: 0.33

    0.33

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 54.0 s

    54.0 s

    Your largest element takes 54.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Learn more”.

  • Time to Interactive: 57.7 s

    57.7 s

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

  • Speed Index: 14.4 s

    14.4 s

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

  • Total Blocking Time: 872 ms

    872 ms

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

  • Real-user INP: 388 ms

    388 ms

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.205

    0.205

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

  • 14 images without width and height

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

Images and page weight

3 to fix45
  • Page weight: 15.7 MB in 203 requests

    15.7 MB

    Your homepage downloads 15.7 MB in 203 requests on a phone: images 10.1 MB (82), scripts 4.6 MB (29) and other files 386 KiB (84). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Property-Practice-Laptop.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (1.8 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.

  • About 4.4 g of CO₂ per visit

    4.45 g

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

2 checks passed
  • 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

8 to fixGoogle 7987
  • 16 buttons without a name

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

  • Interactive controls must not be nested (9 elements)

    Interactive controls must not be nested: 9 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • 3 text elements with low contrast

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

  • 2 tap targets too small

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

  • 26 images without alt text

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h4 and h1 → h4), 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).

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 7777
  • Title is short (16 characters)

    Your title is only 16 characters: “Juta And Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 11 H1 headlines

    There are 11 <h1> headlines (“SOLUTIONS TO ADVANCE YOUR BUSINESS”, “SOLUTIONS TO ADVANCE YOUR BUSINESS” and “REIMAGINE THE FUTURE OF LEGAL RESEARCH”). 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.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at juta.co.za/robots.txt, the first file search crawlers ask for.

  • 20 internal links, 12 external

    The homepage links to 20 pages on juta.co.za and 12 external pages.

3 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Juta and Company is a leading provider of quality legal, regulatory, business and academic content across Africa”.

  • Canonical URL set

    The canonical URL is http://juta.co.za/.

  • Structured data in place

    Structured data found: Website.

AI search readiness

1 to fix81
  • 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://juta.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
  • Text is in the HTML

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

Other pages

4 to fix68
  • 1 page without a title

    https://juta.co.za/contact-us has no <title>, so Google invents the link text in results.

  • 9 pages share 2 titles

    / and https://juta.co.za/home all use the title “Juta And Company”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://juta.co.za/about, https://juta.co.za/faq, https://juta.co.za/blog, https://juta.co.za/rights-and-permissions, https://juta.co.za/pages/paia-manual and https://juta.co.za/pages/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://juta.co.za/about, https://juta.co.za/blog, https://juta.co.za/pages/paia-manual, https://juta.co.za/pages/privacy-policy and https://juta.co.za/pages/terms-and-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://juta.co.za/blog, https://juta.co.za/pages/paia-manual, https://juta.co.za/pages/privacy-policy and https://juta.co.za/pages/terms-and-conditions 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.

  • 7 pages slow to respond

    https://juta.co.za/faq, https://juta.co.za/contact-us, https://juta.co.za/blog, https://juta.co.za/rights-and-permissions, https://juta.co.za/pages/paia-manual and https://juta.co.za/pages/privacy-policy and 1 other took over 3 s to send their HTML from our server.

  • 9 internal pages checked

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

3 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

4 to fixGoogle 7370
  • 4 broken images

    4 images failed to load on a phone, for example https://d.adroll.com/uev/YTKXYSJNK5GGDPXU3ZJ4ZW/4IUC2WEPLFH63IHWHRWWON/?pv=47761841113.67662&arrfrr=https%3A%2F%2Fjuta.co.za%2F&event_name=productView&adroll_version=2.0.

  • 10 small tap targets

    10 of 33 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.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Subresource Integrity: The resource 'https://www.google-analytics.com/analytics.js' has an integrity attribute, but the…”.

  • 1 low-resolution image

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 230 words

    The homepage has only about 230 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “LEARN MORE”.

  • 3 calls to action

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

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 28 other companies contacted

    Loading the homepage contacts 28 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 juta.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

Framework
Angular
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Azure

Company

Founded
1853

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on juta.co.za, including 24 speed issues, 5 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