Website review, no card needed
iathletic.com.au website review
Visit site (opens in a new tab)Reviewed 5 November 202641 issues · 86 checks
This review found 41 issues worth fixing on iathletic.com.au, 12 of them high impact, across 86 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #41,464 of 124,214 reviewed websitesbeats 61%
- #27,465 of 69,818 online storesbeats 54%
- #26,459 of 63,493 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 108 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 116 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 120 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
1.9 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Improve image delivery
1.8 s · 2.0 MB17 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.1 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 2.1 MB and 1.2 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Shopify adds 552 ms
552 msShopify costs a phone 552 ms of main-thread work and 1.2 MB 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.
Use efficient cache lifetimes
250 ms · 308 KiB19 files are served with short cache lifetimes, so returning visitors download them again (308 KiB).
Reduce unused CSS
300 ms · 73 KiBAbout 73 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.
2,318 HTML elements
The page has 2,318 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 159 ms
159 msKlaviyo costs a phone 159 ms of main-thread work and 308 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Minify JavaScript
37 KiB37 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 484 ms
484 msScripts block taps and scrolling for 484 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 282 requests
5.9 MBYour homepage downloads 5.9 MB in 282 requests on a phone: images 2.4 MB (28), scripts 2.3 MB (112) and other files 883 KiB (120). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
web_test-5.jpg 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).
4 images far larger than shown
403 KiB4 images are downloaded at several times the size a phone draws them, for example web_test-5.jpg at 1,600 px wide, shown at 378 px. Resized copies would save about 403 KiB.
10 images below the first screen load straight away
10 images further down the page (281 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (35 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.7 g of CO₂ per visit
1.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.67 g of CO₂e: 200.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
60 links without text
60 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (9 characters)
Your title is only 9 characters: “iAthletic”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
137 internal links, 66 external
The homepage links to 137 pages on iathletic.com.au and 66 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://iathletic.com.au/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://iathletic.com.au/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,154 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://iathletic.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://iathletic.com.au/collections/shop-all, https://iathletic.com.au/collections/ia-performance, https://iathletic.com.au/collections/all-shorts and https://iathletic.com.au/collections/ia-streetwear have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://iathletic.com.au/collections/shop-all, https://iathletic.com.au/collections/ia-performance, https://iathletic.com.au/collections/all-shorts and https://iathletic.com.au/collections/ia-streetwear have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://iathletic.com.au/collections/ia-performance took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
2 checks passed
Tap targets are thumb-sized
61 of 63 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 216 words
The homepage has only about 216 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “SHOP NOW GOOD. BETTER. iATHLETIC.”.
12 calls to action
The homepage has 12 calls to action, for example “IA SHOP”, “CONTACT US” and “SHOP NOW GOOD. BETTER. iATHLETIC.”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before 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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
No consent tool detected
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.
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at iathletic.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ta Labels Badges · Slider Revolution · Puco Sections Blocks · Klaviyo Email Marketing Sms · Meteor Mega Menu · Judge Me Reviews · Fly Bundles Upsells · Textbox By Textify · Zoorix Cross Sell · Hulk Form Builder · Aris Product Options · Fontio · Echo All In One Fixed Bundles · Simple Bundle · Pusher Sections Builder · Bacon Menu · Restockrocket · Free Contact Form · Ecomsend · herokuapp.com · zakeke.com · loloyal.com · nfcube.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Melbourne
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on iathletic.com.au, including 19 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.