kecotabs.com.au website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, addons.business and 9gtb.com and others), adding 681 KiB and 652 ms of main-thread time.

Shopify costs a phone 402 ms of main-thread work and 534 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 129 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.9 s).

The page becomes fully interactive after 12.9 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 638 ms in total while the page loads. Good is under 200 ms.

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

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 16.1 MB in 341 requests on a phone: media 13.3 MB (1), images 1.1 MB (114) and scripts 786 KiB (135). Under 2 MB keeps phones on slow connections fast.

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 14 characters: “KECO Australia”. Between 30 and 65 characters leaves room to say what you do and for whom.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 256 pages on kecotabs.com.au and 20 external pages.

https://kecotabs.com.au/collections/keco-training, https://kecotabs.com.au/collections/glue-guns, https://kecotabs.com.au/collections/k-beams-k-bars, https://kecotabs.com.au/collections/mini-lifters, https://kecotabs.com.au/collections/slide-hammers and https://kecotabs.com.au/collections/pdr-cold-glues and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://kecotabs.com.au/collections/new-products, https://kecotabs.com.au/pages/book-demo and https://kecotabs.com.au/pages/the-glue-pull-repair-advantage took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 602 words of visible text.

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