Website review, no card needed

matildas.co.za logo

matildas.co.za website review

Visit site (opens in a new tab)Reviewed 10 November 202632 issues · 89 checks

This review found 32 issues worth fixing on matildas.co.za, 7 of them high impact, across 89 checks. The most urgent: 5 buttons without a name. 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
1.5 s1.3 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
110 ms93 msMay 23Nov 7108 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202698 ms
May 30, 2026100 ms
Jun 6, 2026103 ms
Jun 13, 2026105 ms
Jun 20, 2026103 ms
Jun 27, 2026102 ms
Jul 4, 2026100 ms
Jul 11, 202699 ms
Jul 18, 202698 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 202697 ms
Aug 15, 2026101 ms
Aug 22, 2026104 ms
Aug 29, 2026105 ms
Sep 5, 2026107 ms
Sep 12, 2026106 ms
Sep 19, 2026105 ms
Sep 26, 2026105 ms
Oct 3, 2026103 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026105 ms
Nov 7, 2026108 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 matildas.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. matildas.co.za at 0.7 s0.7 s
  2. matildas.co.za at 1.4 s1.4 s
  3. matildas.co.za at 2.2 s2.2 s
  4. matildas.co.za at 2.9 s2.9 s
  5. matildas.co.za at 3.6 s3.6 s
  6. matildas.co.za at 4.3 s4.3 s
  7. matildas.co.za at 5.0 s5.0 s
  8. matildas.co.za at 5.7 s5.7 s

Speed

8 to fix87
  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87. 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 (Shopify, Klaviyo and Google CDN and others), adding 1.2 MB and 475 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Reduce unused JavaScript

    405 KiB

    About 405 KiB of JavaScript is downloaded but never used on this page.

  • 1,940 HTML elements

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

  • Shopify adds 137 ms

    137 ms

    Shopify costs a phone 137 ms of main-thread work and 356 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.

  • Klaviyo adds 129 ms

    129 ms

    Klaviyo costs a phone 129 ms of main-thread work and 329 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 110 ms

    110 ms

    Google CDN costs a phone 110 ms of main-thread work and 296 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 · 53 KiB

    About 53 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

    150 ms · 7 KiB

    1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    63 KiB

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 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 JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 317 ms

    317 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 513 ms

    513 ms

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

  • Total Blocking Time: 102 ms

    102 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix60
  • 1 image over 500 KB

    31977962-d4b8-4a8e-9e02-7211bde37ae8.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.5 MB in 164 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 164 requests on a phone: images 1.4 MB (30), scripts 1.2 MB (79) and other files 658 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (1.1 MB) is 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 1.0 g of CO₂ per visit

    0.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.6 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

7 to fixGoogle 7990
  • 5 buttons without a name

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

  • 22 text elements with low contrast

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

  • 22 tap targets too small

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

  • Scrollable region must have keyboard access (3 elements)

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

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

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

  • 17 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), 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 63 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • 3 H1 headlines

    There are 3 <h1> headlines (“Matildas.co.za”, “Your Online Sex Toy Shop Adult Toys in South Afri…” and “Frequently Asked Questions”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • 301 internal links, 1 external

    The homepage links to 301 pages on matildas.co.za and 1 external page.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Shop sex toys with discreet delivery anywhere in South Africa. Find vibrators, dildos and couples toys with fast courie…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Adult Shop South Africa - Discreet Sex Toys Online - Matilda’s”.

  • Canonical URL set

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

  • 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.matildas.co.za/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.matildas.co.za/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.matildas.co.za/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.matildas.co.za/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.matildas.co.za/pages/swym-wishlist and https://www.matildas.co.za/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.matildas.co.za/pages/swym-wishlist and https://www.matildas.co.za/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.matildas.co.za/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 126 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 9686
  • 16 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

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

    The homepage carries about 888 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: “SHOP GLOW”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Start shopping”, “Shop Glow” and “Start With the Guide”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 51 testimonial or review blocks and a star rating.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 matildas.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seo Manager Venntov · Klaviyo Email Marketing Sms · Specification And Compare · gorgias.chat · 9gtb.com · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2024.

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Durban

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on matildas.co.za, including 11 speed issues, 2 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