Website review, no card needed
ambertiles.com.au website review
Visit site (opens in a new tab)Reviewed 19 October 202649 issues · 92 checks
This review found 49 issues worth fixing on ambertiles.com.au, 20 of them high impact, across 92 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
66D- #110,094 of 120,492 reviewed websitesbeats 7%
- #65,218 of 68,208 online storesbeats 4%
- #59,888 of 62,153 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 203 ms |
| May 9, 2026 | 209 ms |
| May 16, 2026 | 210 ms |
| May 23, 2026 | 212 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 220 ms |
| Jun 27, 2026 | 212 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 217 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 216 ms |
| Aug 1, 2026 | 214 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 304 ms |
| Aug 22, 2026 | 362 ms |
| Aug 29, 2026 | 426 ms |
| Sep 5, 2026 | 433 ms |
| Sep 12, 2026 | 424 ms |
| Sep 19, 2026 | 431 ms |
| Sep 26, 2026 | 428 ms |
| Oct 3, 2026 | 421 ms |
| Oct 10, 2026 | 421 ms |
| Oct 17, 2026 | 418 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.4 s · 709 KiBAbout 709 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
trkcall.com adds 1.7 s
1.7 strkcall.com costs a phone 1.7 s of main-thread work and 17 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.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,216 HTML elements
The page has 6,216 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (trkcall.com, Google Tag Manager and Facebook and others), adding 1.5 MB and 2.8 s of main-thread time.
Use efficient cache lifetimes
750 ms · 698 KiB27 files are served with short cache lifetimes, so returning visitors download them again (698 KiB).
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Google Tag Manager adds 505 ms
505 msGoogle Tag Manager costs a phone 505 ms of main-thread work and 819 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 516 ms. During a long task the page ignores taps.
Improve image delivery
382 KiB16 images could be 382 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 270 ms
270 msFacebook costs a phone 270 ms of main-thread work and 340 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.
Minify JavaScript
52 KiB52 KiB could be saved by minifying JavaScript.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Reduce unused CSS
12 KiBAbout 12 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: 17 ms
17 msYour server sent the HTML in 17 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.
Real-user INP: 517 ms
517 msReal visitors wait 517 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 18.0 s
18.0 sYour largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image”.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 104% slower for real visitors
+104%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 203 ms to 418 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 364 requests
5.3 MBYour homepage downloads 5.3 MB in 364 requests on a phone: images 2.1 MB (65), scripts 2.1 MB (157) and other files 843 KiB (127). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
OCT_SALE_HOT_OFFERS_2026_3-1_-_Home_page_banner_MOBILE.png 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).
3 images in older formats
3 images (98 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.
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 180.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (22 elements)
Elements must only use permitted ARIA attributes: 22 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
91 form fields without a label
91 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 130 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Amber Tiles”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
355 internal links, 50 external
The homepage links to 355 pages on ambertiles.com.au and 50 external pages.
4 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Australia's tile and paver specialists for 50+ years. Browse tiles, pavers, natural stone and bathroomware, or book a d…”.
Canonical URL set
The canonical URL is https://www.ambertiles.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://www.ambertiles.com.au/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (2,956 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ambertiles.com.au/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.ambertiles.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.ambertiles.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.ambertiles.com.au/blogs/inspiration, https://www.ambertiles.com.au/customer_authentication/redirect, https://www.ambertiles.com.au/pages/wishlist and https://www.ambertiles.com.au/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.ambertiles.com.au/blogs/inspiration, https://www.ambertiles.com.au/customer_authentication/redirect, https://www.ambertiles.com.au/pages/wishlist, https://www.ambertiles.com.au/pages/store-locator, https://www.ambertiles.com.au/pages/albion and https://www.ambertiles.com.au/pages/armidale 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 122 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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56266533&Ver=2&mid=a3fa744a-f48b-41b7-98f0-2c9f8ec511e6&bo=1&sid=02050ef0cc0211f1baa2c51e605a2e4b&vid=020534e0cc0211f1a496055adca3f2bf&vids=1&msclkid=N&pi=918639831&lg.
23 small tap targets
23 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
9 third-party cookies
9 third-party cookies are 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 “Expected property name or '}' in JSON at position 2 (line 1 column 3) JSON.parse (<anonymous>)”.
Missing source maps
Large scripts ship without source maps.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 562 words of copy
The homepage carries about 562 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SEND QUOTE REQUEST”.
11 calls to action
The homepage has 11 calls to action, for example “Shop By Category”, “Shop By Room” and “Shop By Material”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 50 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.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
36 cookies set on arrival
36Opening the homepage sets 36 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.
42 other companies contacted
Loading the homepage contacts 42 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 ambertiles.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on ambertiles.com.au, including 23 speed issues, 5 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.