priceattack.com.au website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and shortcutssoftware.com and others), adding 3.7 MB and 2.6 s of main-thread time.

About 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

58 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

shortcutssoftware.com costs a phone 340 ms of main-thread work and 724 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.

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

TikTok costs a phone 312 ms of main-thread work and 283 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,684 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 157 ms of main-thread work and 312 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 74 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

The page becomes fully interactive after 35.5 s. Good is under 3.8 s.

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

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

Real visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

1 image 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' tap response (inp) went from 192 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 530 requests on a phone: scripts 3.7 MB (149), other files 1.8 MB (305) and images 346 KiB (26). Under 2 MB keeps phones on slow connections fast.

PA_4955_Christmas_Phase_01_Digital_17_Website_Banner_W2800xH is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example PA_4955_Christmas_Phase_01_Digital_17_Website_Banner_W2800xH at 2,800 px wide, shown at 390 px. Resized copies would save about 74 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your <h1> is empty.

The homepage links to 362 pages on priceattack.com.au and 13 external pages.

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

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

Chrome logged issues while loading the page (“Cookie”).

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

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