strike.com.au website review

About 592 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

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

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

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

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

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

Google Tag Manager costs a phone 328 ms of main-thread work and 313 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.

rebuyengine.com costs a phone 286 ms of main-thread work and 676 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 243 ms of main-thread work and 408 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.

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

Klaviyo costs a phone 209 ms of main-thread work and 322 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 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.

9 images could be 82 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.

4 KiB JavaScript is shipped twice across bundles.

Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Strike Volt Lockable Tablet Charging Cabinet”.

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

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

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

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

19 images 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 113 ms to 120 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 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 306 requests on a phone: scripts 1.8 MB (109), images 1.8 MB (40) and other files 800 KiB (106). Under 2 MB keeps phones on slow connections fast.

Strike-Homepage-S12-Accessories-1920x350.png 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).

2 images further down the page (61 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.46 g of CO₂e: 175.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 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: 3 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

Your title is 70 characters, so Google will cut it off around 60: “Car Phone Holders, Cradles & Mounts, Phone Antennas, Car Kits | Strike”.

Your <h1> is empty.

The homepage links to 520 pages on strike.com.au and 11 external pages.

/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

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

2 images failed to load on a phone, for example https://www.strike.com.au/apps/updateanticopyrecords/crawlerbeacon?shop=strike-group-australia.myshopify.com&path=%2F.

3 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot assign to read only property 'klaviyo' of object '#<Window>'”.

1 image is served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.strike.com.au/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,134 words of visible text.

DMARC is set to p=none, so mail pretending to be strike.com.au is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and LinkedIn Insight and 4 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 18 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.