Website review, no card needed

snookums.co.za logo

snookums.co.za website review

Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 78 checks

This review found 34 issues worth fixing on snookums.co.za, 13 of them high impact, across 78 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 snookums.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. snookums.co.za at 1.5 s1.5 s
  2. snookums.co.za at 3.1 s3.1 s
  3. snookums.co.za at 4.6 s4.6 s
  4. snookums.co.za at 6.2 s6.2 s
  5. snookums.co.za at 7.7 s7.7 s
  6. snookums.co.za at 9.3 s9.3 s
  7. snookums.co.za at 10.8 s10.8 s
  8. snookums.co.za at 12.4 s12.4 s

Speed

11 to fix44
  • Use efficient cache lifetimes

    2.8 s · 1.6 MB

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

  • Render-blocking requests

    4.3 s

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

  • Reduce unused JavaScript

    1.9 s · 744 KiB

    About 744 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce initial server response time

    1.1 s

    Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

  • Document request latency

    1.1 s

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

  • Mobile performance score: 44

    44/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Google Fonts and others), adding 792 KiB and 674 ms of main-thread time.

  • Google Tag Manager adds 458 ms

    458 ms

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

  • Main-thread work: 2.6 s

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

  • 2,233 HTML elements

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

  • Server response: 1.2 s

    1.2 s

    Your server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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

    156 KiB

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

6 to fix53
  • 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 “GROWING UP. TOGETHER. SINCE 1975 Trusted Baby Products for …”.

  • Speed Index: 12.2 s

    12.2 s

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

  • Time to Interactive: 14.7 s

    14.7 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 499 ms

    499 ms

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

  • 2 images without width and height

    2 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
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 110 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 110 requests on a phone: scripts 1.7 MB (36), HTML 425 KiB (1) and images 412 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    logo_snookums.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (97 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.

  • About 0.7 g of CO₂ per visit

    0.75 g

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

1 checks passed
  • 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 8493
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 36 text elements with low contrast

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

  • 5 tap targets too small

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

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

  • 7 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 62 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (15 characters)

    Your title is only 15 characters: “Home - Snookums”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (399 characters)

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

  • 12 links with vague text

    12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 220 internal links, 14 external

    The homepage links to 220 pages on snookums.co.za and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Growing up. Together.Since 1975”.

  • Canonical URL set

    The canonical URL is https://snookums.co.za/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, 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://snookums.co.za/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://snookums.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.

3 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, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 pages share a title

    https://snookums.co.za/product-category/feeding/bottle-warmers and https://snookums.co.za/product-category/bottle-warmers all use the title “Bottle Warmers - Snookums”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://snookums.co.za/shop, https://snookums.co.za/product-category/feeding/breast-pumps-milk-storage, https://snookums.co.za/product-category/feeding/bottle-feeding, https://snookums.co.za/product-category/feeding/sippy-cups-weaning, https://snookums.co.za/product-category/feeding/sterilising and https://snookums.co.za/product-category/feeding/bottle-warmers and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://snookums.co.za/product-category/bottle-warmers, whose canonical is https://snookums.co.za/product-category/feeding/bottle-warmers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages slow to respond

    https://snookums.co.za/product-category/feeding/breast-pumps-milk-storage, https://snookums.co.za/product-category/feeding/bottle-feeding, https://snookums.co.za/product-category/feeding/sippy-cups-weaning, https://snookums.co.za/product-category/feeding/sterilising, https://snookums.co.za/product-category/feeding and https://snookums.co.za/product-category/feeding/sterilising/sterilisers and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 9691
  • 1 JavaScript error while loading

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

  • 6 distorted images

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

2 checks passed
  • Tap targets are thumb-sized

    36 of 39 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 33 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 763 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: “Contact us” and “Shop Baby Products”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Contact us”, “Shop all Feeding” and “Shop all Sterilising”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 snookums.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
E-commerce
WooCommerce
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 34 issues on snookums.co.za, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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