Website review, no card needed

ruggedvalley.co.nz logo

ruggedvalley.co.nz website review

Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 91 checks

This review found 38 issues worth fixing on ruggedvalley.co.nz, 11 of them high impact, across 91 checks. The most urgent: page weight: 32.6 MB in 393 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.4 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
219 ms152 msMay 16Oct 31201 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026167 ms
May 30, 2026173 ms
Jun 6, 2026169 ms
Jun 13, 2026173 ms
Jun 20, 2026169 ms
Jun 27, 2026166 ms
Jul 4, 2026168 ms
Jul 11, 2026165 ms
Jul 18, 2026162 ms
Jul 25, 2026170 ms
Aug 1, 2026178 ms
Aug 8, 2026188 ms
Aug 15, 2026200 ms
Aug 22, 2026202 ms
Aug 29, 2026189 ms
Sep 5, 2026187 ms
Sep 12, 2026191 ms
Sep 19, 2026195 ms
Sep 26, 2026211 ms
Oct 3, 2026202 ms
Oct 10, 2026200 ms
Oct 17, 2026189 ms
Oct 24, 2026187 ms
Oct 31, 2026201 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ruggedvalley.co.nz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ruggedvalley.co.nz at 2.5 s2.5 s
  2. ruggedvalley.co.nz at 4.9 s4.9 s
  3. ruggedvalley.co.nz at 7.4 s7.4 s
  4. ruggedvalley.co.nz at 9.8 s9.8 s
  5. ruggedvalley.co.nz at 12.3 s12.3 s
  6. ruggedvalley.co.nz at 14.7 s14.7 s
  7. ruggedvalley.co.nz at 17.2 s17.2 s
  8. ruggedvalley.co.nz at 19.6 s19.6 s

Speed

7 to fix68
  • Main-thread work: 5.9 s

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

  • 3,009 HTML elements

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

  • 8 third-party services on the page

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

  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    140 ms · 313 KiB

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

  • Google Tag Manager adds 280 ms

    280 ms

    Google Tag Manager costs a phone 280 ms of main-thread work and 332 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 adds 167 ms

    167 ms

    Klaviyo costs a phone 167 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.

  • 13 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    66 KiB

    About 66 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    31 KiB

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

  • Legacy JavaScript

    25 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 9.5 s

    9.5 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 341 ms

    341 ms

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

  • Total Blocking Time: 400 ms

    400 ms

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROTECT YOUR SEATS FROM DIRT, GRIME AND WATER. BUILT FOR WO…”. Most of its time is element render delay (2.5 s).

  • Tap response (INP) got 19% slower for real visitors

    +19%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 487 ms

    487 ms

    Real visitors wait 487 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.064

    0.064

    The layout barely moves while loading (CLS 0.064, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 32.6 MB in 393 requests

    32.6 MB

    Your homepage downloads 32.6 MB in 393 requests on a phone: media 29.4 MB (5), scripts 1.3 MB (101) and other files 1.2 MB (226). Under 2 MB keeps phones on slow connections fast.

  • About 9.2 g of CO₂ per visit

    9.25 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8290
  • 2 buttons without a name

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

  • Scrollable region must have keyboard access (1 element)

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

  • 8 images without alt text

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

  • All page content should be contained by landmarks (25 elements)

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

  • Zoom is disabled

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

  • 10 form fields without a label

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

  • 3 links without text

    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)

    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

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7771
  • No H1 headline

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

  • 53 links crawlers can't follow

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

  • Title is long (71 characters)

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

  • Meta description is long (214 characters)

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

  • Structured data has 2 problems

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

  • 1 link with vague text

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

  • 71 internal links, 2 external

    The homepage links to 71 pages on ruggedvalley.co.nz and 2 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://ruggedvalley.co.nz/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://ruggedvalley.co.nz/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    55%

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • llms.txt published

    The site publishes https://ruggedvalley.co.nz/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://ruggedvalley.co.nz/pages/update-your-details and https://ruggedvalley.co.nz/pages/returns use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://ruggedvalley.co.nz/pages/update-your-details, 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.

  • 1 page slow to respond

    https://ruggedvalley.co.nz/pages/about-us took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    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…”).

  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    81 of 92 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,459 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up to our email list” and “Shop All Seat Covers”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Sign up to our email list”, “Contact Us” and “Contact”.

  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 35 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ruggedvalley.co.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Okendo · Boost Ai Search Filter · Klaviyo Email Marketing Sms · Preorder Now · cart-bot.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on ruggedvalley.co.nz, including 15 speed issues, 6 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25