ritkeep.au website review

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

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

About 278 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 680 ms faster on a phone.

17 images could be 225 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.

8 third-party services load with your homepage (Clarity, Shopify and 1clicklabs.io and others), adding 1.6 MB and 248 ms of main-thread time.

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

1clicklabs.io costs a phone 16 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.

Shopify costs a phone 103 ms of main-thread work and 300 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 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 220 ms faster on a phone.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.6 MB in 301 requests on a phone: images 4.5 MB (72), other files 956 KiB (151) and scripts 811 KiB (65). Under 2 MB keeps phones on slow connections fast.

29 images (8.1 MB) 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.

1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

32 elements hidden from screen readers can still receive keyboard focus.

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

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

Inline text spacing must be adjustable with custom stylesheets: 6 elements on the page fail this check, rated serious by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

20 images have no alt text, which hurts accessibility and image search.

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

3 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 (h1 → h3, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 85 characters, so Google will cut it off around 60: “Smith Machine | Power Cage | Free Weight | Weight Bench | RitKeep – RITKEEP Australia”.

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

The homepage links to 255 pages on ritkeep.au and 14 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/collections/power-rack-package and /collections/free-weight-package have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /collections/home-gym-smith-machine-package/products/nimitz-n1-counterbalanced-all-in-one-smith-machine-package, whose canonical is /products/nimitz-n1-counterbalanced-all-in-one-smith-machine-package. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/2026-black-friday has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97052050&tm=shpfy_ui&Ver=2&mid=6de9713d-3c92-4986-9d49-ad8659f0ad20&bo=1&sid=b4307860dd0711f1a30ea11058b794eb&vid=b430dda0dd0711f1a264ad56ee123be9&vids=1&msclkid=N&pi=.

2 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'gtag'”.

Requests the notification permission on page load.

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: 17 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 966 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.