Website review, no card needed

boodykids.com.au logo

boodykids.com.au website review

Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 90 checks

This review found 37 issues worth fixing on boodykids.com.au, 14 of them high impact, across 90 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
3.0 s2.3 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.7 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
199 ms166 msMay 16Oct 31183 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026171 ms
May 23, 2026170 ms
May 30, 2026171 ms
Jun 6, 2026173 ms
Jun 13, 2026173 ms
Jun 20, 2026176 ms
Jun 27, 2026175 ms
Jul 4, 2026176 ms
Jul 11, 2026176 ms
Jul 18, 2026177 ms
Jul 25, 2026180 ms
Aug 1, 2026180 ms
Aug 8, 2026188 ms
Aug 15, 2026191 ms
Aug 22, 2026195 ms
Aug 29, 2026195 ms
Sep 5, 2026188 ms
Sep 12, 2026185 ms
Sep 19, 2026180 ms
Sep 26, 2026181 ms
Oct 3, 2026185 ms
Oct 10, 2026186 ms
Oct 17, 2026185 ms
Oct 24, 2026186 ms
Oct 31, 2026183 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 boodykids.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boodykids.com.au at 0.8 s0.8 s
  2. boodykids.com.au at 1.6 s1.6 s
  3. boodykids.com.au at 2.3 s2.3 s
  4. boodykids.com.au at 3.1 s3.1 s
  5. boodykids.com.au at 3.9 s3.9 s
  6. boodykids.com.au at 4.7 s4.7 s
  7. boodykids.com.au at 5.5 s5.5 s
  8. boodykids.com.au at 6.2 s6.2 s

Speed

12 to fix46
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 7.1 s

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

  • 4,028 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and Yotpo and others), adding 2.4 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 897 KiB

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

  • Use efficient cache lifetimes

    200 ms · 727 KiB

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

  • Shopify adds 523 ms

    523 ms

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

  • Improve image delivery

    150 ms · 297 KiB

    16 images could be 297 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.

  • Klaviyo adds 348 ms

    348 ms

    Klaviyo costs a phone 348 ms of main-thread work and 633 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.

  • 17 long tasks on the main thread

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

  • Yotpo adds 259 ms

    259 ms

    Yotpo costs a phone 259 ms of main-thread work and 330 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 · 98 KiB

    About 98 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.

  • Duplicated JavaScript

    53 KiB

    53 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

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

  • Time to Interactive: 27.5 s

    27.5 s

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

  • Speed Index: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 6.1 s

    6.1 s

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

  • Total Blocking Time: 917 ms

    917 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 197 ms

    197 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user TTFB: 612 ms

    612 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

2 to fix64
  • Page weight: 5.1 MB in 405 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 405 requests on a phone: scripts 2.6 MB (183), images 1.0 MB (45) and other files 993 KiB (144). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    MOBILE-HERO-BANNER-_-FULL-WIDTH-BLEED-PERIWINKLE-GWP.gif 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).

  • 1 image in older formats

    1 image (298 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.

  • About 1.4 g of CO₂ per visit

    1.45 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.8 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 9093
  • 16 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 13 images without alt text

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

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

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 51 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: 51 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8583
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (167 characters)

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

  • 2 links with vague text

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

  • 477 internal links, 8 external

    The homepage links to 477 pages on boodykids.com.au and 8 external pages.

6 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “Comfortable & Sustainable Bamboo Clothes | Boody Australia”.

  • Canonical URL set

    The canonical URL is https://www.boody.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://www.boody.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.boody.com.au/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 8 pages without an H1

    https://www.boody.com.au/collections/black-friday-sale, https://www.boody.com.au/pages/delivery-policy, https://www.boody.com.au/collections/signatures, https://www.boody.com.au/collections/womens-bras, https://www.boody.com.au/collections/periwinkle and https://www.boody.com.au/collections/womens-full-bust-bras and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.boody.com.au/collections/black-friday-sale and https://www.boody.com.au/collections/womens-bras 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 108 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

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

Best practices

3 to fixGoogle 5488
  • 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.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    47 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

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

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 454 words of copy

    The homepage carries about 454 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Login / Register”.

  • 55 calls to action

    The homepage has 55 calls to action, for example “Contact Us”, “Shop All Bras” and “Shop All Underwear”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 37 cookies set on arrival

    37

    Opening the homepage sets 37 cookies, 2 of them by other companies (measured from a US location before any click).

  • 71 other companies contacted

    Loading the homepage contacts 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 boodykids.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 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Checkout Components · Helium Customer Fields · Gorgias Live Chat Helpdesk · Tolstoy · Boody X Magic Fit · Yotpo Product Reviews · Triplewhale · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Loop Returns · Bluecart Upsell Progress Bar · Event Promotion Bar · rise-ai.com · oxiapps.com · snapchat.com · rakutenadvertising.io · revenuehunt.com · amazonaws.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on boodykids.com.au, including 19 speed issues, 3 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