evatac.com.au website review

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

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

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

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

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

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

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

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

Klaviyo costs a phone 173 ms of main-thread work and 397 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 112 ms of main-thread work and 357 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 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

1 long task block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.

11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

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

Your largest element takes 12.2 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 9.9 s (Speed Index). Good is under 3.4 s.

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

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

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

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

Your homepage downloads 3.3 MB in 400 requests on a phone: other files 1.4 MB (269), scripts 1.0 MB (95) and images 655 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example airflex-v2-look-3.jpg at 390 px wide, shown at 78 px. Resized copies would save about 47 KiB.

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

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: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 12 characters: “EVA ATHLETIC”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“EVA ATHLETIC” and “26.11.26”). One clear main headline is easier for people and search engines.

The homepage links to 147 pages on evatac.com.au and 11 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://evaathletic.com.au/products/eva-elite-membership-yearly, https://evaathletic.com.au/collections/mens-tees-tanks, https://evaathletic.com.au/collections/evolution-oversize-tee, https://evaathletic.com.au/collections/eva-8591-longline-tee, https://evaathletic.com.au/collections/mens-shorts and https://evaathletic.com.au/collections/mens-hoodies have no meta description, so Google writes the search snippet from whatever text it finds.

https://evaathletic.com.au/collections/shop-all, https://evaathletic.com.au/collections/mens-tees-tanks, https://evaathletic.com.au/collections/evolution-oversize-tee, https://evaathletic.com.au/collections/eva-8591-longline-tee, https://evaathletic.com.au/collections/mens-shorts and https://evaathletic.com.au/collections/mens-hoodies have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 11 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 “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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

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