Website review, no card needed

koalaliving.com.au logo

koalaliving.com.au website review

Visit site (opens in a new tab)Reviewed 23 October 202647 issues · 86 checks

This review found 47 issues worth fixing on koalaliving.com.au, 20 of them high impact, across 86 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.2 sMay 2Oct 173.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.7 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20263.9 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
202 ms176 msMay 2Oct 17199 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026185 ms
May 9, 2026183 ms
May 16, 2026179 ms
May 23, 2026180 ms
May 30, 2026180 ms
Jun 6, 2026187 ms
Jun 13, 2026185 ms
Jun 20, 2026185 ms
Jun 27, 2026185 ms
Jul 4, 2026182 ms
Jul 11, 2026187 ms
Jul 18, 2026187 ms
Jul 25, 2026188 ms
Aug 1, 2026188 ms
Aug 8, 2026187 ms
Aug 15, 2026187 ms
Aug 22, 2026187 ms
Aug 29, 2026188 ms
Sep 5, 2026195 ms
Sep 12, 2026196 ms
Sep 19, 2026196 ms
Sep 26, 2026197 ms
Oct 3, 2026196 ms
Oct 10, 2026196 ms
Oct 17, 2026199 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 koalaliving.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix10
  • Use efficient cache lifetimes

    2.4 s · 11.7 MB

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

  • Reduce unused JavaScript

    7.3 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Mobile performance score: 10

    10/100

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

  • Main-thread work: 5.5 s

    A phone's processor spends 5.5 s on main-thread work while loading, 3.3 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 (Google Tag Manager, Facebook and Klaviyo and others), adding 1.5 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    900 ms · 113 KiB

    About 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Improve image delivery

    300 ms · 315 KiB

    11 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 442 ms

    442 ms

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

  • Legacy JavaScript

    300 ms · 42 KiB

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

  • 20 long tasks on the main thread

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

  • 2,169 HTML elements

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

  • Klaviyo adds 141 ms

    141 ms

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

  • commbank.com.au adds 100 ms

    100 ms

    commbank.com.au costs a phone 100 ms of main-thread work and 307 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.

  • Phones get a much slower page than desktops

    Desktop scores 45 but mobile only 10. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 4 ms

    4 ms

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

Core Web Vitals

13 to fix0
  • 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 CLS: 1.01

    1.01

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

  • Largest Contentful Paint: 26.9 s

    26.9 s

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

  • Time to Interactive: 31.9 s

    31.9 s

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

  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.394

    0.394

    The layout shifts by 0.394 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 263 ms

    263 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

Images and page weight

2 to fix63
  • Page weight: 16.5 MB in 260 requests

    16.5 MB

    Your homepage downloads 16.5 MB in 260 requests on a phone: media 10.9 MB (5), scripts 3.1 MB (101) and images 1.6 MB (54). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

    8 images further down the page (527 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

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

    4.68 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.68 g of CO₂e: 562.1 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

6 to fix75
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 6 links without text

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

  • Orphan list items

    Some list items are not inside a list.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

SEO

4 to fixGoogle 8580
  • No H1 headline

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

  • 22 links crawlers can't follow

    22 links have no real href, so search engines can't follow them.

  • Meta description is long (162 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 225 internal links, 4 external

    The homepage links to 225 pages on koalaliving.com.au and 4 external pages.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Koala Living: Designer Furniture Store In Australia”.

  • Canonical URL set

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

  • 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.koalaliving.com.au/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://koalaliving.com.au/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 (688 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix68
  • 5 pages without a title

    https://koalaliving.com.au/living/leather-sofas/2-seater-leather-sofa, https://koalaliving.com.au/living/leather-sofas/leather-recliner-sofa, https://koalaliving.com.au/living/leather-sofas/leather-armchair, https://koalaliving.com.au/living/fabric-sofas/2-seater-sofa and https://koalaliving.com.au/living/fabric-sofas/3-seater-sofa have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://koalaliving.com.au/living/leather-sofas and https://koalaliving.com.au/living/fabric-sofas all use the title “| Koala Living”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://koalaliving.com.au/membership, https://koalaliving.com.au/customer, https://koalaliving.com.au/sourcebooks, https://koalaliving.com.au/living/leather-sofas, https://koalaliving.com.au/living/leather-sofas/2-seater-leather-sofa and https://koalaliving.com.au/living/leather-sofas/leather-recliner-sofa and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://koalaliving.com.au/sourcebooks, https://koalaliving.com.au/living/leather-sofas, https://koalaliving.com.au/living/leather-sofas/2-seater-leather-sofa, https://koalaliving.com.au/living/leather-sofas/leather-recliner-sofa, https://koalaliving.com.au/living/leather-sofas/leather-armchair and https://koalaliving.com.au/living/fabric-sofas and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://koalaliving.com.au/customer, https://koalaliving.com.au/store-locator, https://koalaliving.com.au/sourcebooks, https://koalaliving.com.au/new-arrivals, https://koalaliving.com.au/living and https://koalaliving.com.au/living/leather-sofas and 3 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 189 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97167562&Ver=2&mid=682d5d09-cf2a-4a6d-b60b-a8777d55c640&bo=1&sid=e561efa0cedc11f1b918a94d3871b313&vid=e5620cf0cedc11f18bc07d289bb77d32&vids=1&msclkid=N&pi=918639831&lg.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

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

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

    The homepage carries about 305 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP NOW”, “Contact Us” and “Trade Sign Up”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.

  • 40 other companies contacted

    Loading the homepage contacts 40 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 koalaliving.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

Company

Founded
2007
Headquarters
Victoria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on koalaliving.com.au, including 27 speed issues, 4 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