mysmartlocks.com.au website review

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

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

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

8 third-party services load with your homepage (Shopify, Intercom and Klaviyo and others), adding 2.4 MB and 1.2 s of main-thread time.

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

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

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

Klaviyo costs a phone 176 ms of main-thread work and 421 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.

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smart Security, Smarter Savings Elevate your entry with Fac…”.

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

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

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

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

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

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

Your homepage downloads 2.8 MB in 220 requests on a phone: scripts 1.7 MB (115), images 443 KiB (31) and fonts 389 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

The homepage links to 74 pages on mysmartlocks.com.au and 5 external pages.

Your homepage links to https://mysmartlocks.com.au/collections/palm-recognition and https://mysmartlocks.com.au/products/philips-easykey-ddl303-vp-5hws, which answer with an error. Visitors hit a dead end and search engines drop them.

https://mysmartlocks.com.au/collections/all and https://mysmartlocks.com.au/products/ddl702-1hws-black-video-lock-mortise-924c-60-door-thickness-38-60mm all use the title “Philips Smart Door Locks Australia | Free Shipping”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mysmartlocks.com.au/collections/all, https://mysmartlocks.com.au/collections/premium-range, https://mysmartlocks.com.au/collections/special-offers-promo, https://mysmartlocks.com.au/collections/facial-recognition, https://mysmartlocks.com.au/collections/handle-locks and https://mysmartlocks.com.au/collections/2-in-1-doorbell-smart-locks and 3 others 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 https://mysmartlocks.com.au/products/philips-easykey-ddl709-fvp-7hws, whose canonical is https://mysmartlocks.com.au/products/philips-easykey-ddl709-fvp-7hws-smart-door-lock. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mysmartlocks.com.au/pages/customer-care and https://mysmartlocks.com.au/apps/ldt-compare have no <h1> headline, so visitors and search engines get no clear main topic.

https://mysmartlocks.com.au/products/philips-easykey-ddl709-fvp-7hws took over 3 s to send its HTML from our server.

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

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

Your longest form asks for 20 fields (0 required). Every extra field lowers completion.

The homepage has only about 214 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The page uses urgency cues (a countdown or limited-time wording).

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