Website review, no card needed
haymespaint.com.au website review
Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 86 checks
This review found 40 issues worth fixing on haymespaint.com.au, 10 of them high impact, across 86 checks. The most urgent: main-thread work: 12.4 s. 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
86B- #12,034 of 124,093 reviewed websitesbeats 87%
- #7,289 of 69,769 online storesbeats 85%
- #7,060 of 63,457 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.5 s |
| Nov 14, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 191 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 206 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 213 ms |
| Aug 8, 2026 | 222 ms |
| Aug 15, 2026 | 235 ms |
| Aug 22, 2026 | 242 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 247 ms |
| Sep 12, 2026 | 245 ms |
| Sep 19, 2026 | 237 ms |
| Sep 26, 2026 | 231 ms |
| Oct 3, 2026 | 222 ms |
| Oct 10, 2026 | 209 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 212 ms |
| Oct 31, 2026 | 210 ms |
| Nov 7, 2026 | 214 ms |
| Nov 14, 2026 | 215 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.5 s
3.1 s
4.6 s
6.2 s
7.7 s
9.3 s
10.8 s
12.3 s
Speed
Main-thread work: 12.4 s
A phone's processor spends 12.4 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,026 HTML elements
The page has 3,026 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 (Google Tag Manager, weglot.com and Clarity and others), adding 1.7 MB and 2.1 s of main-thread time.
Improve image delivery
1.4 MB40 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 641 KiBAbout 641 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
554 KiB28 files are served with short cache lifetimes, so returning visitors download them again (554 KiB).
Google Tag Manager adds 440 ms
440 msGoogle Tag Manager costs a phone 440 ms of main-thread work and 348 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.
weglot.com adds 413 ms
413 msweglot.com costs a phone 413 ms of main-thread work and 210 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.
Clarity adds 368 ms
368 msClarity costs a phone 368 ms of main-thread work and 29 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.
Render-blocking requests
350 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Facebook adds 310 ms
310 msFacebook costs a phone 310 ms of main-thread work and 277 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 on the main thread
18 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.
Klaviyo adds 185 ms
185 msKlaviyo costs a phone 185 ms of main-thread work and 336 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
50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need.
Minify JavaScript
15 KiB15 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.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 25.9 s
25.9 sVisually, the page fills in at 25.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 27.7 s
27.7 sThe page becomes fully interactive after 27.7 s. Good is under 3.8 s.
Total Blocking Time: 614 ms
614 msScripts block taps and scrolling for 614 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 177 ms to 215 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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: 161 ms
161 msReal visitors wait 161 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 337 ms
337 msReal visitors wait 337 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.1 s
2.1 sYour largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “FREE Delivery on 4 × 125ml Sample PotsShop Now”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 554 requests
6.3 MBYour homepage downloads 6.3 MB in 554 requests on a phone: images 2.3 MB (85), scripts 2.2 MB (137) and other files 1.4 MB (284). Under 2 MB keeps phones on slow connections fast.
35 images below the first screen load straight away
35 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
11 images in older formats
11 images (673 KiB) are 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.
2 images far larger than shown
164 KiB2 images are downloaded at several times the size a phone draws them, for example BAU_Brand_Assets_2026_Ultra_Premium_Banner.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 164 KiB.
About 1.8 g of CO₂ per visit
1.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.80 g of CO₂e: 216.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
28 text elements with low contrast
28 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (10 elements)
Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
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.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 99 images in the HTML carry an alt attribute.
54 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: 54 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“”, “” and “Global GreenTag Certified”). One clear main headline is easier for people and search engines.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
424 internal links, 22 external
The homepage links to 424 pages on haymespaint.com.au and 22 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Haymes Paint is the only major paint brand made and owned in Australia. Browse our range of interior and exterior paint…”.
Title: 38 characters
Your title is a healthy 38 characters: “Haymes Paint - Australian Made & Owned”.
Canonical URL set
The canonical URL is https://www.haymespaint.com.au/.
Structured data in place
Structured data found: Organization 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://www.haymespaint.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, 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,707 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.haymespaint.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share 4 titles
https://www.haymespaint.com.au/pages/whites-colour-planet and https://www.haymespaint.com.au/pages/whites all use the title “Whites - Haymes Paint”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.haymespaint.com.au/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://www.haymespaint.com.au/pages/whites-colour-planet and https://www.haymespaint.com.au/pages/whites use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.haymespaint.com.au/pages/whites, whose canonical is https://www.haymespaint.com.au/pages/whites-colour-planet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 149 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
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://asia.adform.net/Serving/TrackPoint/?pm=4035126&ADFPageName=pagevisit%7Canypage&ADFdivider=%7C&ADFtpmode=4&itm=%7Bsv1%3A%20%27pagevisit%27%2Csv2%3A%20%27anypage%27%7D.
13 small tap targets
13 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute')”.
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.
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 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 1,162 words of copy
The homepage carries about 1,162 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 “Learn more”.
21 calls to action
The homepage has 21 calls to action, for example “Shop Now”, “Apply for a Trade Account” and “Order Brushouts”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, 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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 1 of them by other companies (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.
54 other companies contacted
Loading the homepage contacts 54 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 haymespaint.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Instafeed · Weglot Translate Your Store · trustpilot.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 1935
- Headquarters
- Melbourne
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on haymespaint.com.au, including 19 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.