Website review, no card needed
babybrezza.co.za website review
Visit site (opens in a new tab)Reviewed 11 November 202641 issues · 82 checks
This review found 41 issues worth fixing on babybrezza.co.za, 16 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75C- #81,236 of 124,093 reviewed websitesbeats 30%
- #51,548 of 69,777 online storesbeats 22%
- #48,644 of 63,466 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 197 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 128 ms |
| Aug 15, 2026 | 121 ms |
| Nov 7, 2026 | 188 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Reduce unused JavaScript
7.0 s · 715 KiBAbout 715 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 418 KiB25 files are served with short cache lifetimes, so returning visitors download them again (418 KiB).
Render-blocking requests
1.9 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
1.1 s · 504 KiB13 images could be 504 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Vimeo, Clarity and Cloudflare CDN and others), adding 15.7 MB and 874 ms of main-thread time.
Vimeo adds 371 ms
371 msVimeo costs a phone 371 ms of main-thread work and 14.9 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.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
300 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 21.5 s
21.5 sYour largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Toggle Video Play & Pause Product 1 Shop Now VIDEO DESCRIPT…”.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 205 ms
205 msReal visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 135 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 365 ms
365 msReal visitors wait 365 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 80 ms
80 msScripts block the page for only 80 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 18.4 MB in 399 requests
18.4 MBYour homepage downloads 18.4 MB in 399 requests on a phone: other files 14.9 MB (247), scripts 1.6 MB (83) and images 1.3 MB (42). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
54 KiB1 image is downloaded at several times the size a phone draws it, for example 0CkyAt_A_480x.png at 389 px wide, shown at 40 px. Resized copies would save about 54 KiB.
1 image in older formats
1 image (314 KiB) 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.
5 images below the first screen load straight away
5 images further down the page (143 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.22 g of CO₂e: 626.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (24 characters)
Your title is only 24 characters: “Baby Brezza South Africa”. 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.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
60 internal links, 2 external
The homepage links to 60 pages on babybrezza.co.za and 2 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://babybrezza.co.za/.
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://babybrezza.co.za/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://babybrezza.co.za/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://babybrezza.co.za/collections/all-products, https://babybrezza.co.za/collections/spare-parts, https://babybrezza.co.za/pages/formula-settings, https://babybrezza.co.za/pages/formula-pro-information-center, https://babybrezza.co.za/pages/about-us and https://babybrezza.co.za/pages/contact and 1 other 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://babybrezza.co.za/products/bottle-washer-pro%C2%AE, whose canonical is https://babybrezza.co.za/products/bottle-washer-pro%c2%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://babybrezza.co.za/collections/all-products, https://babybrezza.co.za/collections/spare-parts and https://babybrezza.co.za/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://babybrezza.co.za/pages/formula-pro-information-center, https://babybrezza.co.za/pages/about-us and https://babybrezza.co.za/pages/retail-partners 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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.
Titles are unique
Every page we checked has its own title.
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
7 small tap targets
7 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 133 words
The homepage has only about 133 words of visible text; thin pages give Google and first-time buyers little to go on.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Product 1 Shop Now” and “Sign Up Here”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 4 of them by other companies (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.
27 other companies contacted
Loading the homepage contacts 27 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 babybrezza.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Klaviyo Email Marketing Sms · Microsoft Clarity · Avada Order Limit · Omnisend · Selleasy · pandect.es
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
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
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 babybrezza.co.za, including 18 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.