arova.com.au website review

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

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

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

About 1.0 MB of JavaScript is downloaded but never used on this page.

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

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

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

hsappstatic.net costs a phone 655 ms of main-thread work and 720 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 509 ms of main-thread work and 318 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 504 ms. During a long task the page ignores taps.

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

Shopify costs a phone 360 ms of main-thread work and 274 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 CDN costs a phone 248 ms of main-thread work and 386 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 239 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 85 KiB JavaScript that modern phones do not need.

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

13 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.

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

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Your homepage downloads 5.6 MB in 311 requests on a phone: scripts 2.5 MB (99), images 1.7 MB (47) and other files 846 KiB (131). Under 2 MB keeps phones on slow connections fast.

Black_Friday_2026-04.jpg 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).

2 images (73 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.

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

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

The homepage links to 387 pages on arova.com.au and 17 external pages.

https://www.arova.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.arova.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.arova.com.au/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.arova.com.au/pages/find-our-store, https://www.arova.com.au/pages/about-us, https://www.arova.com.au/pages/career-opportunities-1, https://www.arova.com.au/customer_authentication/redirect, https://www.arova.com.au/collections/bathroom-vanity and https://www.arova.com.au/collections/baths and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.arova.com.au/collections/bathroom-vanity, https://www.arova.com.au/collections/baths, https://www.arova.com.au/collections/toilets, https://www.arova.com.au/collections/wall-hung-vanity, https://www.arova.com.au/collections/freestanding-vanity and https://www.arova.com.au/collections/timber-vanity and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.arova.com.au/customer_authentication/redirect and https://www.arova.com.au/collections/toilets took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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: net::ERR_CONNECTION_RESET”.

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

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.

Social proof on the homepage: 1 testimonial or review block. 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 1,082 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies, 10 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.