lovattsmagazines.com.au website review

18 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

8 third-party services load with your homepage (Facebook, Google Tag Manager and Klaviyo and others), adding 1.7 MB and 940 ms of main-thread time.

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

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

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

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

Facebook costs a phone 341 ms of main-thread work and 398 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 289 ms of main-thread work and 474 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.

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

Klaviyo costs a phone 97 ms of main-thread work and 319 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 long tasks block the main thread while loading, the longest for 167 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 41 KiB JavaScript that modern phones do not need.

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

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.

5 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 14.0 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 24.9 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 224 requests on a phone: images 2.5 MB (29), scripts 1.9 MB (88) and other files 696 KiB (84). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example b1eac188eb18--lovatts-mags-web-slider-special-editons-2026-0 at 2,520 px wide, shown at 391 px. Resized copies would save about 1,018 KiB.

19 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

21 images have 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.

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

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

Your title is 100 characters, so Google will cut it off around 60: “Shop Lovatts Magazines | Mindful Magazines | Subscriptions & Single Issues - lovattsmagaz…”.

There are 3 <h1> headlines (“Our Subscriptions”, “Magazines For Kids” and “Special Editions”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("https")”.

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

The homepage links to 99 pages on lovattsmagazines.com.au and 18 external pages.

https://lovattsmagazines.com.au/collections/single-issues and https://lovattsmagazines.com.au/collections/single-issues/bundle use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://lovattsmagazines.com.au/pages/subscribe-to-win, whose canonical is https://lovattsmagazines.com.au/pages/competition-winners. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lovattsmagazines.com.au/collections/subscriptions and https://lovattsmagazines.com.au/collections/single-issues have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

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