Website review, no card needed

zebrababies.com.au logo

zebrababies.com.au website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 74 checks

This review found 31 issues worth fixing on zebrababies.com.au, 7 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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.3 s977 msMay 23Jul 251.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
122 ms106 msMay 23Jul 18120 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026113 ms
Jun 13, 2026111 ms
Jun 20, 2026108 ms
Jun 27, 2026110 ms
Jul 4, 2026112 ms
Jul 11, 2026112 ms
Jul 18, 2026120 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 zebrababies.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zebrababies.com.au at 0.4 s0.4 s
  2. zebrababies.com.au at 0.8 s0.8 s
  3. zebrababies.com.au at 1.1 s1.1 s
  4. zebrababies.com.au at 1.5 s1.5 s
  5. zebrababies.com.au at 1.9 s1.9 s
  6. zebrababies.com.au at 2.3 s2.3 s
  7. zebrababies.com.au at 2.6 s2.6 s
  8. zebrababies.com.au at 3.0 s3.0 s

Speed

9 to fix74
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    380 ms · 618 KiB

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

  • Improve image delivery

    514 KiB

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

  • Use efficient cache lifetimes

    50 ms · 357 KiB

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

  • 2,129 HTML elements

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

  • Main-thread work: 2.0 s

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

  • bestfreecdn.com adds 145 ms

    145 ms

    bestfreecdn.com costs a phone 145 ms of main-thread work and 302 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.

  • Shopify adds 84 ms

    84 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (bestfreecdn.com, Shopify and searchatlas.com and others), adding 766 KiB and 265 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    80 ms · 14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    87 KiB

    About 87 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ribbon Dummy Clip baby girl dummy clips with daisy flowers …”.

  • Time to Interactive: 10.4 s

    10.4 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

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

4 checks passed
  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 39 ms

    39 ms

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

Images and page weight

3 to fix69
  • Page weight: 3.4 MB in 255 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 255 requests on a phone: images 1.4 MB (43), other files 1.0 MB (105) and scripts 673 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    silicone-sippy-cup-clearance-687.jpg 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).

  • 17 images in older formats

    17 images (923 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 1.0 g of CO₂ per visit

    0.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 115.9 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 8793
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Meta description is long (239 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 168 internal links, 14 external

    The homepage links to 168 pages on zebrababies.com.au and 14 external pages.

6 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Zebra Babies - Dummy Clips and Teething Toys”.

  • Canonical URL set

    The canonical URL is https://zebrababies.com.au/.

  • Structured data in place

    Structured data found: Organization 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://zebrababies.com.au/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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://zebrababies.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://zebrababies.com.au/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://zebrababies.com.au/products/dummy-clips-silicone-custom-personalised and https://zebrababies.com.au/products/dummy-clip-flexi-ribbon have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'CartDrawer' has already been declared”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

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

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 781 words of visible text.

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Contact” and “Contact information”.

  • 8 short forms

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

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.

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 zebrababies.com.au, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

King Product Options · Seo King · Judge Me Reviews · Sc Easy Redirects · Stockist Maps · Snap B2b Wholesale Pricing · Syncx Preorder · bestfreecdn.com

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on zebrababies.com.au, including 12 speed issues, 2 SEO issues and 4 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