ruggedvalley.com.au website review

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.4 MB and 836 ms of main-thread time.

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

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

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

Shopify costs a phone 279 ms of main-thread work and 427 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 194 ms of main-thread work and 333 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.

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

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

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

34 KiB could be saved by minifying JavaScript.

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

1 image could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Real visitors wait 336 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “10% OFF ALL SEAT COVERS SITEWIDE. FREE GIFT FOR ORDERS OVER…”.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 167 ms to 204 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 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 33.0 MB in 415 requests on a phone: media 29.4 MB (4), scripts 1.5 MB (106) and other files 1.3 MB (242). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), 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.

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

Your title is 71 characters, so Google will cut it off around 60: “Rugged Valley | Car Seat Covers NZ | Built to Thrash – Rugged Valley NZ”.

Your meta description is 214 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:")”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 73 pages on ruggedvalley.com.au and 2 external pages.

The HTML your server sends has 873 of the 1,477 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://ruggedvalley.co.nz/products/rugged-valley-canvas-utility-picnic-mat, https://ruggedvalley.co.nz/collections/car-floor-mats, https://ruggedvalley.co.nz/collections/dashmats, https://ruggedvalley.co.nz/collections/seat-covers and https://ruggedvalley.co.nz/collections/seat-covers-to-suit-toyota-hilux-utes have no <h1> headline, so visitors and search engines get no clear main topic.

https://ruggedvalley.co.nz/collections/seat-covers and https://ruggedvalley.co.nz/collections/seat-covers-to-suit-toyota-hilux-utes 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.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

5 errors were logged to the browser console while the page loaded, for example “Kaching Cart admin custom script error TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not…”.

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 1,477 words of visible text.

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