Website review, no card needed

zinto.co.za logo

zinto.co.za website review

Visit site (opens in a new tab)Reviewed 25 October 202641 issues · 76 checks

This review found 41 issues worth fixing on zinto.co.za, 17 of them high impact, across 76 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

Full-page screenshot of zinto.co.za (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zinto.co.za at 0.7 s0.7 s
  2. zinto.co.za at 1.4 s1.4 s
  3. zinto.co.za at 2.1 s2.1 s
  4. zinto.co.za at 2.8 s2.8 s
  5. zinto.co.za at 3.5 s3.5 s
  6. zinto.co.za at 4.3 s4.3 s
  7. zinto.co.za at 5.0 s5.0 s
  8. zinto.co.za at 5.7 s5.7 s

Speed

4 to fix43
  • Use efficient cache lifetimes

    2.4 s · 3.5 MB

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

  • Render-blocking requests

    5.6 s

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

  • Improve image delivery

    1.8 s · 1.9 MB

    32 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 1.8 s faster on a phone.

  • Mobile performance score: 43

    43/100

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

  • Reduce unused JavaScript

    160 ms · 45 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Analytics), adding 19 KiB and 20 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix42
  • Largest Contentful Paint: 24.9 s

    24.9 s

    Your largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 26.2 s

    26.2 s

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

  • Cumulative Layout Shift: 0.396

    0.396

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 47 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix33
  • Page weight: 9.2 MB in 197 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 197 requests on a phone: images 8.6 MB (150), scripts 328 KiB (21) and HTML 264 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    1,004 KiB

    7 images are downloaded at several times the size a phone draws them, for example 3.png at 732 px wide, shown at 160 px. Resized copies would save about 1,004 KiB.

  • 40 images in older formats

    40 images (4.2 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.

  • 34 images below the first screen load straight away

    34 images further down the page (3.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.6 g of CO₂ per visit

    2.61 g

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

Accessibility

8 to fixGoogle 5778
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 111 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

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

  • Headings skip levels

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

1 checks passed
  • 17 automated accessibility rules passed

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

SEO

9 to fixGoogle 8257
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (5 characters)

    Your title is only 5 characters: “Zinto”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 9 H1 headlines

    There are 9 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • 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://zinto.co.za/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • No favicon declared

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 21 internal links, 4 external

    The homepage links to 21 pages on zinto.co.za and 4 external pages.

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://zinto.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix71
  • 3 pages without a title

    https://zinto.co.za/Scythia_files/videos/Kiri_Cheese_Taste_Experience.m4v, https://zinto.co.za/Scythia_files/videos/10.m4v and https://zinto.co.za/Scythia_files/videos/13.m4v have no <title>, so Google invents the link text in results.

  • 3 pages without a meta description

    https://zinto.co.za/Scythia_files/videos/Kiri_Cheese_Taste_Experience.m4v, https://zinto.co.za/Scythia_files/videos/10.m4v and https://zinto.co.za/Scythia_files/videos/13.m4v have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://zinto.co.za/Scythia_files/videos/Kiri_Cheese_Taste_Experience.m4v, https://zinto.co.za/Scythia_files/videos/10.m4v and https://zinto.co.za/Scythia_files/videos/13.m4v have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 internal pages checked

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

3 checks passed
  • Linked pages load

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

3 to fixGoogle 4687
  • 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 “Mixed Content: The page at 'https://zinto.co.za/' was loaded over HTTPS, but requested an insecure stylesheet 'http://f…”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 17 low-resolution images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 726 words of copy

    The homepage carries about 726 words of visible text.

5 checks passed
  • 1 call to action

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

  • Social proof on the page

    Social proof on the homepage: 22 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

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

    1

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

  • 4 cookies set on arrival

    4

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 zinto.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on zinto.co.za, including 10 speed issues, 9 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