rayslocker.com.au website review

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

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

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

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

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

Shopify costs a phone 167 ms of main-thread work and 323 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 1,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, Klaviyo and Azure Web Services and others), adding 637 KiB and 244 ms of main-thread time.

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

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

About 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.

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

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

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.

The layout shifts by 0.945 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 2.4 MB in 207 requests on a phone: other files 990 KiB (118), scripts 670 KiB (62) and images 508 KiB (15). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Asics.Gel.Kayano.14.Carrier.Grey.Rayslocker.1_943b39a2-b459- at 1,080 px wide, shown at 171 px. Resized copies would save about 210 KiB.

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

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

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

Structured data found (Corporation) but with 2 problems, for example “Corporation: logo is not an absolute URL ("https:")”.

The homepage links to 99 pages on rayslocker.com.au and 5 external pages.

https://rayslocker.com.au/collections/new-arrivals, https://rayslocker.com.au/collections/accessories, https://rayslocker.com.au/collections/our-biggest-mid-year-sale-ever, https://rayslocker.com.au/collections/unreleased-kayano-20-pack, https://rayslocker.com.au/collections/asics-gel-cumulus-16-exclusive-pink-salt and https://rayslocker.com.au/collections/trending-saucony-omni-9 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://rayslocker.com.au/products/gift-card, whose canonical is https://rayslocker.com.au/products/egift-voucher. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://rayslocker.com.au/products/gift-card, https://rayslocker.com.au/collections/new-arrivals, https://rayslocker.com.au/collections/mens, https://rayslocker.com.au/collections/womens, https://rayslocker.com.au/collections/all and https://rayslocker.com.au/collections/accessories 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 51 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Wishlist app is not enabled”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

The homepage shows no opening hours. If customers visit or call, show when.

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