justprotools.com.au website review

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

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

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

8 third-party services load with your homepage (amaicdn.com, Clarity and Shopify and others), adding 1.0 MB and 810 ms of main-thread time.

amaicdn.com costs a phone 338 ms of main-thread work and 401 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 348 KiB of JavaScript is downloaded but never used on this page.

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

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

Clarity costs a phone 259 ms of main-thread work and 30 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.

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

Shopify costs a phone 102 ms of main-thread work and 465 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 81 KiB JavaScript that modern phones do not need.

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

54 KiB could be saved by minifying JavaScript.

About 26 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 14.2 s. Good is under 3.8 s.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Spend & Save Nov 2026”.

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

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

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

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

Your homepage downloads 3.5 MB in 430 requests on a phone: other files 1.3 MB (201), scripts 1.1 MB (105) and images 694 KiB (56). Under 2 MB keeps phones on slow connections fast.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 191 pages on justprotools.com.au and 18 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://a.klaviyo.com/media/css/public/klaviyo_subscribe.css' from origin 'https://justpro…”.

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

The homepage carries about 1,841 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 16 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.