Website review, no card needed

carenut.co.za logo

carenut.co.za website review

Visit site (opens in a new tab)Reviewed 13 November 202643 issues · 82 checks

This review found 43 issues worth fixing on carenut.co.za, 16 of them high impact, across 82 checks. The most urgent: document request latency. 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

Full-page screenshot of carenut.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. carenut.co.za at 1.7 s1.7 s
  2. carenut.co.za at 3.4 s3.4 s
  3. carenut.co.za at 5.0 s5.0 s
  4. carenut.co.za at 6.7 s6.7 s
  5. carenut.co.za at 8.4 s8.4 s
  6. carenut.co.za at 10.1 s10.1 s
  7. carenut.co.za at 11.7 s11.7 s
  8. carenut.co.za at 13.4 s13.4 s

Speed

8 to fix55
  • Document request latency

    4.2 s

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

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 55

    55/100

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

  • Reduce unused JavaScript

    750 ms · 130 KiB

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

  • Avoid multiple page redirects

    751 ms

    The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

  • Google Tag Manager adds 333 ms

    333 ms

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

  • Use efficient cache lifetimes

    300 KiB

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

  • 2,356 HTML elements

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs and others), adding 359 KiB and 335 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 11 KiB

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

  • Improve image delivery

    132 KiB

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

  • Legacy JavaScript

    8 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 466 ms

    466 ms

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

Core Web Vitals

9 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 CLS: 1.27

    1.27

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

  • Speed Index: 19.6 s

    19.6 s

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

  • Largest Contentful Paint: 9.1 s

    9.1 s

    Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SPECIALS FREE SHIPPING - for orders over R800 Ts&Cs DAILY D…”. Most of its time is resource load delay (9.5 s).

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 870 ms

    870 ms

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

  • 19 images without width and height

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

4 checks passed
  • Real-user INP: 161 ms

    161 ms

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

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

  • Cumulative Layout Shift: 0.053

    0.053

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

  • Total Blocking Time: 66 ms

    66 ms

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

Images and page weight

3 to fix65
  • Page weight: 2.9 MB in 159 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 159 requests on a phone: images 2.3 MB (120), scripts 455 KiB (19) and HTML 84 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (502 KiB) 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.

  • 6 images far larger than shown

    272 KiB

    6 images are downloaded at several times the size a phone draws them, for example Main3.png at 852 px wide, shown at 163 px. Resized copies would save about 272 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (97 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.83 g

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

Accessibility

11 to fixGoogle 4277
  • Image buttons must have alternative text (14 elements)

    Image buttons must have alternative text: 14 elements on the page fail this check, rated critical by axe-core.

  • Input buttons must have discernible text (2 elements)

    Input buttons must have discernible text: 2 elements on the page fail this check, rated critical by axe-core.

  • 7 text elements with low contrast

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

  • Positive tabindex

    7 elements have a tabindex above 0, which scrambles the keyboard order.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

  • 88 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 23 form fields without a label

    23 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

4 to fixGoogle 9286
  • No canonical URL

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

  • Meta description is long (178 characters)

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

  • Structured data has 8 problems

    Structured data found (BookStore) but with 8 problems, for example “ld+json block 2 is not valid JSON (Unexpected token 'C', ..." "name": CONCAT(', "... is not va)”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 522 internal links, 0 external

    The homepage links to 522 pages on carenut.co.za and 0 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Pro Visions Online - New and Second hand Books, Bags, Laptops, Tablets and Graduation attire. An official UNISA Booksel…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Pro Visions | Books, Laptops, Stationery - Student Supplies”.

  • 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.provisions.co.za/DynamicSiteMap.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://provisions.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 (3,645 words), so crawlers that don't run JavaScript still read it.

Best practices

3 to fixGoogle 8166
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 8 small tap targets

    8 of 23 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 checks passed
  • No console errors

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

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 18-field form

    Your longest form asks for 18 fields (0 required). Every extra field lowers completion.

  • No map or directions link

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

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register”.

  • 1 call to action

    The homepage has 1 call to action, for example “Book”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 carenut.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

Analytics
Google Analytics | Google Tag Manager
Hosting
Afrihost Sp (Pty) Ltd Afrihost Sp (Pty) Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on carenut.co.za, including 17 speed issues, 4 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