Website review, no card needed
buildmat.com.au website review
Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 92 checks
This review found 37 issues worth fixing on buildmat.com.au, 12 of them high impact, across 92 checks. The most urgent: render-blocking requests. 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- #40,636 of 121,091 reviewed websitesbeats 61%
- #27,067 of 68,525 online storesbeats 54%
- #26,098 of 62,445 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 311 ms |
| May 23, 2026 | 308 ms |
| May 30, 2026 | 305 ms |
| Jun 6, 2026 | 310 ms |
| Jun 13, 2026 | 313 ms |
| Jun 20, 2026 | 313 ms |
| Jun 27, 2026 | 320 ms |
| Jul 4, 2026 | 325 ms |
| Jul 11, 2026 | 329 ms |
| Jul 18, 2026 | 332 ms |
| Jul 25, 2026 | 330 ms |
| Aug 1, 2026 | 331 ms |
| Aug 8, 2026 | 339 ms |
| Aug 15, 2026 | 346 ms |
| Aug 22, 2026 | 359 ms |
| Aug 29, 2026 | 366 ms |
| Sep 5, 2026 | 366 ms |
| Sep 12, 2026 | 367 ms |
| Sep 19, 2026 | 369 ms |
| Sep 26, 2026 | 368 ms |
| Oct 3, 2026 | 383 ms |
| Oct 10, 2026 | 404 ms |
| Oct 17, 2026 | 436 ms |
| Oct 24, 2026 | 463 ms |
| Oct 31, 2026 | 470 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
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Render-blocking requests
1.3 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 6.2 s
A phone's processor spends 6.2 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,833 HTML elements
The page has 5,833 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, Shopify and CallRail and others), adding 1.8 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
300 ms · 948 KiBAbout 948 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 612 ms
612 msGoogle Tag Manager costs a phone 612 ms of main-thread work and 704 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.
Use efficient cache lifetimes
150 ms · 386 KiB22 files are served with short cache lifetimes, so returning visitors download them again (386 KiB).
Shopify adds 230 ms
230 msShopify costs a phone 230 ms of main-thread work and 570 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.
Legacy JavaScript
64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need.
Reduce unused CSS
43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
38 KiB4 images could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 CSS
2 KiB2 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 817 ms
817 msScripts block taps and scrolling for 817 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 320 ms
320 msReal visitors wait 320 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 311 ms to 470 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 661 ms
661 msReal visitors wait 661 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 335 requests
3.9 MBYour homepage downloads 3.9 MB in 335 requests on a phone: scripts 2.2 MB (121), other files 969 KiB (152) and images 225 KiB (34). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 131.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
25 links without text
25 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 (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 520 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Buildmat | Kitchen & Bathroom Sinks, Tapware, Vanities – Melbourne”.
2 H1 headlines
There are 2 <h1> headlines (“Buildmat” and “Luxury kitchen sinks made for modern Australian h…”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
1,125 internal links, 22 external
The homepage links to 1,125 pages on buildmat.com.au and 22 external pages.
6 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “We carry a vast range of bathroom, kitchen, laundry and garden supplies in Melbourne. Visit our Melbourne showroom!”.
Canonical URL set
The canonical URL is https://www.buildmat.com.au/.
Structured data in place
Structured data found: HomeAndConstructionBusiness and Organization.
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.buildmat.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,596 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.buildmat.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.buildmat.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.buildmat.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://www.buildmat.com.au/customer_authentication/redirect, https://www.buildmat.com.au/collections/samples-and-swatches, https://www.buildmat.com.au/collections/kitchen-sinks, https://www.buildmat.com.au/collections/laundry-sinks, https://www.buildmat.com.au/collections/kitchen-sink-trough and https://www.buildmat.com.au/collections/alfresco-sinks and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.buildmat.com.au/customer_authentication/redirect, https://www.buildmat.com.au/collections/samples-and-swatches, https://www.buildmat.com.au/collections/kitchen-sinks, https://www.buildmat.com.au/collections/laundry-sinks, https://www.buildmat.com.au/collections/kitchen-sink-trough and https://www.buildmat.com.au/collections/alfresco-sinks and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.buildmat.com.au/collections/alfresco-sinks, https://www.buildmat.com.au/collections/fireclay-sinks and https://www.buildmat.com.au/collections/gunmetal-kitchen-sinks have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 185 found) and read each the way a search engine does.
3 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.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to construct 'URL': Invalid URL”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
29 of 31 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 953 words of copy
The homepage carries about 953 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL”.
7 calls to action
The homepage has 7 calls to action, for example “Shop All”, “Subscribe” and “Book Appointment”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 126 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 5 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
50 other companies contacted
Loading the homepage contacts 50 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 buildmat.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;Shopify Local Pickup;Shopify Plus;Shopify POS
- Hosting
- Cloudflare
Company
- Headquarters
- Hallam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on buildmat.com.au, including 18 speed issues and 3 SEO issues. 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.