Website review, no card needed

boori.com.au logo

boori.com.au website review

Visit site (opens in a new tab)Reviewed 9 November 202623 issues · 78 checks

This review found 23 issues worth fixing on boori.com.au, 4 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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.4 s707 msMay 23Nov 7816 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 2026944 ms
Sep 26, 2026888 ms
Oct 3, 2026827 ms
Oct 10, 2026786 ms
Oct 17, 2026783 ms
Oct 24, 2026788 ms
Oct 31, 2026807 ms
Nov 7, 2026816 ms
Real-visitor tap response (INP)75th percentile, phones
161 ms126 msMay 23Nov 7152 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026130 ms
May 30, 2026132 ms
Jun 6, 2026137 ms
Jun 13, 2026138 ms
Jun 20, 2026142 ms
Jun 27, 2026145 ms
Jul 4, 2026145 ms
Jul 11, 2026145 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026147 ms
Aug 15, 2026151 ms
Aug 22, 2026153 ms
Aug 29, 2026153 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026155 ms
Oct 3, 2026155 ms
Oct 10, 2026155 ms
Oct 17, 2026157 ms
Oct 24, 2026156 ms
Oct 31, 2026155 ms
Nov 7, 2026152 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 boori.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix99
  • 6,647 HTML elements

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    343 KiB

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

  • Use efficient cache lifetimes

    275 KiB

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

  • Shopify adds 0 ms

    0 ms

    Shopify costs a phone 0 ms of main-thread work and 469 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 (Shopify, Klaviyo and ahrefs.com and others), adding 865 KiB and 0 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    16 KiB

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

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

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

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

3 to fix33
  • 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.

  • Real-user INP: 242 ms

    242 ms

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

  • Real-user CLS: 0.13

    0.13

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

  • Tap response (INP) got 17% slower for real visitors

    +17%

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

10 checks passed
  • Real-user LCP: 0.7 s

    0.7 s

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 285 ms

    285 ms

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

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

    -35%

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

  • First Contentful Paint: 1.6 s

    1.6 s

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

  • Largest Contentful Paint: 1.6 s

    1.6 s

    Your largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Speed Index: 2.3 s

    2.3 s

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

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 22 ms

    22 ms

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

Images and page weight

3 to fix69
  • Page weight: 2.3 MB in 160 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 160 requests on a phone: images 1.3 MB (87), scripts 715 KiB (46) and HTML 145 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    WEB_Homepage_Mobile-Slider_2000x1171_044f1e6a-c835-4b98-82fb 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 far larger than shown

    116 KiB

    1 image is downloaded at several times the size a phone draws it, for example Mobile_category_banner_2000_x_600px_-Whatsapp_cf2db595-00cf- at 2,001 px wide, shown at 300 px. Resized copies would save about 116 KiB.

  • 1 image in older formats

    1 image (193 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 0.6 g of CO₂ per visit

    0.64 g

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

Accessibility

4 to fixGoogle 9696
  • 25 text elements with low contrast

    25 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 (7 elements)

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

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

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

  • 3 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), 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. (13 elements).

2 checks passed
  • Every image has alt text

    All 220 images in the HTML carry an alt attribute.

  • 53 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: 53 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

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 521 internal links, 17 external

    The homepage links to 521 pages on boori.com.au and 17 external pages.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Boori Australia: Beautifully crafted nursery, kids and bedroom furniture in sustainable timber. Trusted by 1M+ parents …”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Boori Australia | Timeless Baby, Kids & Home Furniture”.

  • Canonical URL set

    The canonical URL is https://boori.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://boori.com.au/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • 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 (3,167 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://boori.com.au/pages/careers has 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 131 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    5 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 5 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 5 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 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    46 of 48 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • 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 1,232 words of copy

    The homepage carries about 1,232 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact Us”, “Sign in/ Register” and “Baby Bedding Shop Now”.

  • 40 short forms

    40 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 boori.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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Instafeed · Ecomposer Builder · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Microsoft Clarity · Fbp Fast Bundle · Yotpo Loyalty Rewards · Cartbot · Countdown Timer · Cypher Cart Upsell · Selleasy · Forms · Dealeasy · Frontend · Essential Icon Badge Banners · Order Value Booster · cloudfront.net

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

Hiring

Hiring
3 open roles
Job board
careers page

Company

Founded
1993
Headquarters
Sydney

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on boori.com.au, including 8 speed issues, 1 SEO issue 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