sleepys.com.au website review

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

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

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

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

8 third-party services load with your homepage (Shopify, birdeye.com and Google Tag Manager and others), adding 8.4 MB and 1.8 s of main-thread time.

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

19 images could be 530 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.

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

About 665 KiB of JavaScript is downloaded but never used on this page.

birdeye.com costs a phone 282 ms of main-thread work and 366 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.

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

podium.com costs a phone 134 ms of main-thread work and 304 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 21.7 MB in 243 requests on a phone: media 9.9 MB (2), images 8.9 MB (46) and scripts 1.6 MB (67). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example hero_banner.png at 1,445 px wide, shown at 116 px. Resized copies would save about 391 KiB.

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

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

111 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

33 tap targets are too small or too close together to hit reliably with a finger.

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

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (33 elements).

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 256 pages on sleepys.com.au and 7 external pages.

https://sleepys.com.au/pages/delivery, https://sleepys.com.au/collections/all, https://sleepys.com.au/collections/all-mattresses and https://sleepys.com.au/collections/hot-sleeper have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

14 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

Opening the homepage sets 14 cookies (measured from a US location before any click).

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.

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