stonebase.co.nz website review

About 864 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, POWr and Clarity and others), adding 2.0 MB and 1.3 s of main-thread time.

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

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

Google Tag Manager costs a phone 540 ms of main-thread work and 822 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.

Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

zotabox.com costs a phone 181 ms of main-thread work and 548 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 111 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.

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

15 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

25 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' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.7 MB in 362 requests on a phone: scripts 2.1 MB (80), images 1.4 MB (39) and other files 1.2 MB (233). Under 2 MB keeps phones on slow connections fast.

8 images further down the page (569 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (227 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.34 g of CO₂e: 160.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

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

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

Document should not have more than one banner 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is 76 characters, so Google will cut it off around 60: “Stonebase NZ | Natural Stone Basins, Stone Interior Decor & more – StoneBase”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“”, “Luxury Product range of Natural Stone Basins, Bat…” and “Natural Stone Bathroom Basins & Sinks”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 183 pages on stonebase.co.nz and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://stonebase.co.nz/collections/stone-bowls/%2Fcollections%2Fstone-bowls, which answers with an error. Visitors hit a dead end and search engines drop it.

https://stonebase.co.nz/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://stonebase.co.nz/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://stonebase.co.nz/customer_authentication/redirect, https://stonebase.co.nz/collections/standard-basins, https://stonebase.co.nz/collections/extra-large-basins, https://stonebase.co.nz/collections/extra-large-basins-1, https://stonebase.co.nz/collections/pedestal-basins and https://stonebase.co.nz/collections/luxury-stone-bowls/Bowl-&-Tray and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://stonebase.co.nz/collections/luxury-stone-bowls/Bowl-&-Tray, whose canonical is https://stonebase.co.nz/collections/luxury-stone-bowls. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://stonebase.co.nz/customer_authentication/redirect and https://stonebase.co.nz/collections/stone-basins have no <h1> headline, so visitors and search engines get no clear main topic.

https://stonebase.co.nz/collections/luxury-stone-bowls/Bowl-&-Tray took over 3 s to send its HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://pixel.archipro.co.nz/ping?name=ap-pt-ping&id=stonebase' from origin 'https://stonebase.co.n…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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 545 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 21 cookies, 4 of them by other companies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.