gutzbusta.com.au website review

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

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

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

8 third-party services load with your homepage (Clarity, rebuyengine.com and Klaviyo and others), adding 1.3 MB and 475 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 105 ms of main-thread work and 330 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.

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

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

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

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

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

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

40 KiB could be saved by minifying JavaScript.

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday Sale 2026”.

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

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

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

Your homepage downloads 4.0 MB in 411 requests on a phone: images 1.2 MB (46), scripts 1.2 MB (121) and other files 1.1 MB (168). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example gutzbusta-logo.webp at 519 px wide, shown at 95 px. Resized copies would save about 129 KiB.

4 images (246 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.

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

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

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

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

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

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

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

Your meta description is 249 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 150 pages on gutzbusta.com.au and 28 external pages.

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

https://gutzbusta.com.au/products/small-slow-feed-hay-net took over 3 s to send its HTML from our server.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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