Website review, no card needed
industrie.com.au website review
Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 86 checks
This review found 38 issues worth fixing on industrie.com.au, 15 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
77C- #68,974 of 124,300 reviewed websitesbeats 39%
- #44,614 of 69,848 online storesbeats 31%
- #42,421 of 63,521 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 135 ms |
| May 16, 2026 | 130 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 131 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 149 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 150 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 2026 | 149 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
1.0 s
2.1 s
3.1 s
4.1 s
5.1 s
6.2 s
7.2 s
8.2 s
Speed
Reduce unused JavaScript
4.2 s · 1.0 MBAbout 1.0 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.
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,724 HTML elements
The page has 6,724 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
350 ms · 1.4 MB61 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Wunderkind and athoscommerce.io and others), adding 2.2 MB and 1.1 s of main-thread time.
Use efficient cache lifetimes
800 ms · 249 KiB28 files are served with short cache lifetimes, so returning visitors download them again (249 KiB).
Google Tag Manager adds 370 ms
370 msGoogle Tag Manager costs a phone 370 ms of main-thread work and 373 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 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 382 ms. During a long task the page ignores taps.
Wunderkind adds 216 ms
216 msWunderkind costs a phone 216 ms of main-thread work and 1.1 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.
Legacy JavaScript
150 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 32 ms
32 msYour server sent the HTML in 32 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.
Largest Contentful Paint: 27.4 s
27.4 sYour largest element takes 27.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.7 s
30.7 sThe page becomes fully interactive after 30.7 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 662 ms
662 msScripts block taps and scrolling for 662 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 135 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 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 FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 474 ms
474 msReal visitors wait 474 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-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 10.3 MB in 550 requests
10.3 MBYour homepage downloads 10.3 MB in 550 requests on a phone: images 6.1 MB (199), scripts 2.4 MB (103) and other files 1.3 MB (234). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mobile_960x12100_1c3bc5b5-04c8-4c81-9795-fe10500212e9.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).
About 2.9 g of CO₂ per visit
2.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.91 g of CO₂e: 349.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
53 tap targets too small
53 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (222 characters)
Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected end of JSON input)”.
349 internal links, 0 external
The homepage links to 349 pages on industrie.com.au and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Industrie Clothing I Menswear Brand”.
Title: 50 characters
Your title is a healthy 50 characters: “Industrie Clothing I Menswear Brand – Industrie AU”.
Canonical URL set
The canonical URL is https://www.industrie.com.au/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://www.industrie.com.au/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,710 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.industrie.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.industrie.com.au/collections/del-sur-tees-3-for-90 and https://www.industrie.com.au/pages/help-centre have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.industrie.com.au/collections/sale, https://www.industrie.com.au/collections/del-sur-tees-3-for-90, https://www.industrie.com.au/collections/new-arrivals, https://www.industrie.com.au/pages/help-centre, https://www.industrie.com.au/collections/tees and https://www.industrie.com.au/collections/shirts and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=23006798&tm=gtm002&Ver=2&mid=b14abb1f-417f-42c1-a871-71af3c589e62&bo=1&sid=c3196c40d52411f19656d9066093466b&vid=c31950f0d52411f1a2d141321c3fee56&vids=1&msclkid=N&pi=91.
56 small tap targets
56 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot find mount node with ID "reactify-mount-instant-search"”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 966 words of copy
The homepage carries about 966 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP YOUR SITE”.
57 calls to action
The homepage has 57 calls to action, for example “Shop All New”, “Shop Tees” and “Shop Shirts”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
55 other companies contacted
Loading the homepage contacts 55 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 industrie.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on industrie.com.au, including 17 speed issues, 2 SEO issues and 2 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.