yourreformer.com.au website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and hsappstatic.net and others), adding 4.1 MB and 3.1 s of main-thread time.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

hsappstatic.net costs a phone 601 ms of main-thread work and 719 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.

Facebook costs a phone 623 ms of main-thread work and 435 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.

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

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

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

gotolstoy.com costs a phone 255 ms of main-thread work and 429 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.

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

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

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

20 KiB could be saved by minifying JavaScript.

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

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 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Up to $500 Off your Reformer”.

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

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

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

Real visitors wait 212 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 188 ms to 269 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.2 MB in 479 requests on a phone: scripts 3.2 MB (119), images 2.7 MB (182) and other files 867 KiB (134). Under 2 MB keeps phones on slow connections fast.

260804_Your_Reform_Mori_House_Hero_Sh2_Outside_0847_Medium_f 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).

1 image is downloaded at several times the size a phone draws it, for example EU-flag.webp at 3,840 px wide, shown at 51 px. Resized copies would save about 109 KiB.

4 images (312 KiB) are 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.

2 images further down the page (99 KiB) 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 2.05 g of CO₂e: 246.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is 70 characters, so Google will cut it off around 60: “Pilates Reformer Machines for Home & Commercial Use | Your Reformer AU”.

The homepage links to 133 pages on yourreformer.com.au and 21 external pages.

https://yourreformer.com.au/pages/wholesale has no meta description, so Google writes the search snippet from whatever text it finds.

https://yourreformer.com.au/collections/pilates-reformer-machines, https://yourreformer.com.au/pages/commercial-pilates-reformers, https://yourreformer.com.au/pages/wholesale, https://yourreformer.com.au/collections/purchase-reformers, https://yourreformer.com.au/collections/all-accessories-sale and https://yourreformer.com.au/collections/holiday-gift-guide and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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,125 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (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 25 cookies, 8 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 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.