Website review, no card needed
workwearhub.com.au website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 84 checks
This review found 38 issues worth fixing on workwearhub.com.au, 20 of them high impact, across 84 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
75C- #82,548 of 126,357 reviewed websitesbeats 30%
- #51,972 of 70,445 online storesbeats 22%
- #48,981 of 63,948 Shopify storesbeats 19%
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.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 297 ms |
| May 23, 2026 | 295 ms |
| May 30, 2026 | 292 ms |
| Jun 6, 2026 | 294 ms |
| Jun 13, 2026 | 290 ms |
| Jun 20, 2026 | 289 ms |
| Jun 27, 2026 | 288 ms |
| Jul 4, 2026 | 286 ms |
| Jul 11, 2026 | 286 ms |
| Jul 18, 2026 | 284 ms |
| Jul 25, 2026 | 284 ms |
| Aug 1, 2026 | 283 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 249 ms |
| Aug 22, 2026 | 233 ms |
| Aug 29, 2026 | 218 ms |
| Sep 5, 2026 | 218 ms |
| Sep 12, 2026 | 220 ms |
| Sep 19, 2026 | 225 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 233 ms |
| Oct 10, 2026 | 237 ms |
| Oct 17, 2026 | 238 ms |
| Oct 24, 2026 | 240 ms |
| Oct 31, 2026 | 244 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.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Reduce unused JavaScript
1.7 s · 861 KiBAbout 861 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Shopify adds 1.3 s
1.3 sShopify costs a phone 1.3 s of main-thread work and 529 KiB 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.
Render-blocking requests
1.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,890 HTML elements
The page has 4,890 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
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 2.5 s of main-thread time.
Use efficient cache lifetimes
600 ms · 518 KiB41 files are served with short cache lifetimes, so returning visitors download them again (518 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 650 ms. During a long task the page ignores taps.
Google Tag Manager adds 435 ms
435 msGoogle Tag Manager costs a phone 435 ms of main-thread work and 458 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.
Klaviyo adds 411 ms
411 msKlaviyo costs a phone 411 ms of main-thread work and 623 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.
Legacy JavaScript
200 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Improve image delivery
132 KiB15 images could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 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: 25.9 s
25.9 sYour largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop Now”.
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 34.5 s
34.5 sThe page becomes fully interactive after 34.5 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s 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.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 190 ms
190 msReal visitors wait 190 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: 544 ms
544 msReal visitors wait 544 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 297 ms to 244 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.9 MB in 1,159 requests
7.9 MBYour homepage downloads 7.9 MB in 1,159 requests on a phone: images 3.3 MB (713), scripts 2.5 MB (123) and other files 1.6 MB (294). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
womens.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).
1 image far larger than shown
57 KiB1 image is downloaded at several times the size a phone draws it, for example work-boots-safety-shoes-mens-boa-boots.jpg at 800 px wide, shown at 50 px. Resized copies would save about 57 KiB.
1 image in older formats
1 image (59 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 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 268.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
2 text elements with low contrast
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 (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
884 internal links, 7 external
The homepage links to 884 pages on workwearhub.com.au and 7 external pages.
8 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Shop from the biggest and best brands in workwear at WorkwearHub. Shop Mens and Ladies work clothes, boots, shirts, pan…”.
One H1 headline
Your main headline reads: “WorkwearHub”.
Title: 61 characters
Your title is a healthy 61 characters: “#1 Workwear Clothing Store | Shop Work Clothes Australia Wide”.
Canonical URL set
The canonical URL is https://www.workwearhub.com.au/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://cdn.shopify.com/s/files/1/0277/2742/9771/files/images_sitemap.xml?v=1701745698.
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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,129 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.workwearhub.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.
1 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=295009244&Ver=2&mid=96f21855-4ec7-4741-9994-31be507c25bd&bo=1&sid=79341f40da8911f18077dd3a708c366e&vid=79342140da8911f18346ada91c1fd05a&vids=1&msclkid=N&pi=918639831&l.
25 small tap targets
25 of 58 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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 623 words of copy
The homepage carries about 623 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “Enquire Now”.
22 calls to action
The homepage has 22 calls to action, for example “Download App”, “Shop All” and “Get A Quote”.
6 short forms
6 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
53 other companies contacted
Loading the homepage contacts 53 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 workwearhub.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Seowill Redirects · Triplewhale · Tapcart Mobile App · Yoast Seo · Product Blocker Ageo · Selly Promotion Pricing · Klaviyo Email Marketing Sms · Back In Stock · Slide Cart · webmarked.net · cloudfront.net · gorgias.chat · yotpo.com · 9gtb.com · auspost-collect-app.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Gold Coast
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 workwearhub.com.au, including 18 speed issues and 1 conversion gap. 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.