bugasalt.co.nz website review

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

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

About 306 KiB of JavaScript is downloaded but never used on this page.

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

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

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

8 third-party services load with your homepage (Google Optimize, Google Tag Manager and Shopify and others), adding 884 KiB and 236 ms of main-thread time.

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

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

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

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

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 8.0 s. Good is under 3.8 s.

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

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PRE-BLACK FRIDAY SALE: UP TO $30 OFF BUG-BEAM COMBOS!”. Most of its time is element render delay (2.4 s).

6 images have no width and height attributes, so the layout jumps as each one loads.

1 image (85 KiB) is 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 0.41 g of CO₂e: 48.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

2 elements hidden from screen readers can still receive keyboard focus.

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is only 22 characters: “Bug-A-Salt New Zealand”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 65 pages on bugasalt.co.nz and 13 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.

https://www.bugasalt.co.nz/products/bug-a-salt-lawn-garden-3-0 and https://www.bugasalt.co.nz/collections/3-0-singles/products/bug-a-salt-lawn-garden-3-0 all use the title “NEW LAWN & GARDEN 3.0 – Bug-A-Salt New Zealand”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.bugasalt.co.nz/pages/bundles and https://www.bugasalt.co.nz/collections/pre-black-friday-sale have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bugasalt.co.nz/products/bug-a-salt-lawn-garden-3-0 and https://www.bugasalt.co.nz/collections/3-0-singles/products/bug-a-salt-lawn-garden-3-0 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.bugasalt.co.nz/collections/3-0-singles/products/bug-a-salt-camofly-3-0, whose canonical is https://www.bugasalt.co.nz/products/bug-a-salt-camofly-3-0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.bugasalt.co.nz/collections/3-0, https://www.bugasalt.co.nz/pages/how-it-works, https://www.bugasalt.co.nz/collections/accessories-1 and https://www.bugasalt.co.nz/collections/pre-black-friday-sale have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.bugasalt.co.nz/pages/bundles has 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 51 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus-css-bundles/0-107-0/reviews-widget.dee7b6…”.

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 713 words of visible text.

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