linenshed.com.au website review

A phone's processor spends 6.4 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 load with your homepage (Heroku, Google Tag Manager and Shopify and others), adding 1.4 MB and 2.4 s of main-thread time.

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

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

Heroku costs a phone 807 ms of main-thread work and 52 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.

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

Google Tag Manager costs a phone 640 ms of main-thread work and 735 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 costs a phone 543 ms of main-thread work and 318 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.

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

Your homepage downloads 3.8 MB in 190 requests on a phone: scripts 1.6 MB (78), images 1.3 MB (17) and other files 774 KiB (81). Under 2 MB keeps phones on slow connections fast.

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Bed Linen for Sale Online Australia | Buy Linen Bed Sheets, Duvet Cove”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Your <h1> is empty.

The homepage links to 202 pages on linenshed.com.au and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

1 image failed to load on a phone, for example https://www.linenshed.com.au/.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token '||'”.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 440 words of visible text.

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

Opening the homepage sets 15 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.