livewell.co.nz website review

The page goes through 2 redirects before it starts loading, costing about 9.6 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, frontapp.com and POWr and others), adding 6.9 MB and 2.3 s of main-thread time.

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

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

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

frontapp.com costs a phone 562 ms of main-thread work and 1.3 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.

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

POWr costs a phone 423 ms of main-thread work and 13 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.

alliedmedical.co.nz costs a phone 115 ms of main-thread work and 2.6 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.

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

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

cleva.bot costs a phone 124 ms of main-thread work and 966 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.

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Polyfills for old browsers add 11 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.

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Your homepage downloads 8.3 MB in 543 requests on a phone: scripts 4.3 MB (178), images 1.9 MB (23) and other files 1.4 MB (283). Under 2 MB keeps phones on slow connections fast.

Eldernet_Images.jpg 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).

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

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

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

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: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 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. (1 element).

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Your title is 92 characters, so Google will cut it off around 60: “Livewell and Allied Medical | Mobility & Independence Products – Allied Medical and Livew…”.

Your canonical URL points to alliedmedical.co.nz, not livewell.co.nz, so Google may credit that host instead.

There are 2 <h1> headlines (“” and “Supporting Independence and Everyday Safety”). One clear main headline is easier for people and search engines.

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

Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://alliedmedical.co.nz)”.

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

The homepage links to 305 pages on livewell.co.nz and 32 external pages.

https://livewell.co.nz/pages/join-mailing-list, https://livewell.co.nz/pages/contact, https://livewell.co.nz/pages/livewell, https://livewell.co.nz/collections/new-products, https://livewell.co.nz/collections/adi and https://livewell.co.nz/collections/allard-international and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://livewell.co.nz/pages/join-mailing-list has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 1,587 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 30 cookies, 15 of them by other companies (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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.