Website review, no card needed
thestabledoor.com.au website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 91 checks
This review found 38 issues worth fixing on thestabledoor.com.au, 17 of them high impact, across 91 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
79C- #56,307 of 126,442 reviewed websitesbeats 50%
- #36,709 of 70,471 online storesbeats 42%
- #35,141 of 63,972 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 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 | 129 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 153 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.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.9 s
8.0 s
9.2 s
Speed
Reduce unused JavaScript
1.7 s · 346 KiBAbout 346 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.
Use efficient cache lifetimes
1.1 s · 334 KiB23 files are served with short cache lifetimes, so returning visitors download them again (334 KiB).
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.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,856 HTML elements
The page has 5,856 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 CDN, Shopify and Klaviyo and others), adding 1.1 MB and 1.2 s of main-thread time.
Improve image delivery
450 ms · 678 KiB17 images could be 678 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
490 ms · 73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 490 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 356 ms. During a long task the page ignores taps.
Minify JavaScript
340 ms · 11 KiB11 KiB could be saved by minifying JavaScript.
Google CDN adds 291 ms
291 msGoogle CDN costs a phone 291 ms of main-thread work and 298 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
150 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. 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 CSS
3 KiB3 KiB could be saved by minifying CSS.
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
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blue suede cowboy boot with tan leather accents and intrica…”.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Total Blocking Time: 898 ms
898 msScripts block taps and scrolling for 898 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 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.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 518 ms
518 msReal visitors wait 518 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.068
0.068The layout barely moves while loading (CLS 0.068, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 7.7 MB in 331 requests
7.7 MBYour homepage downloads 7.7 MB in 331 requests on a phone: images 5.0 MB (95), scripts 1.2 MB (86) and other files 1.2 MB (131). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.19 g of CO₂e: 262.7 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
18 elements hidden from screen readers can still receive keyboard focus.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (20 elements).
2 checks passed
Every image has alt text
All 122 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 4 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 long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Ariat, Thomas Cook, Stetson, Wrangler and much more – The Stable Door”.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
588 internal links, 14 external
The homepage links to 588 pages on thestabledoor.com.au and 14 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://thestabledoor.com.au/.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
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://thestabledoor.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 (2,439 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://thestabledoor.com.au/llms.txt (34 KiB, 87 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://thestabledoor.com.au/pages/all-brands has no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://thestabledoor.com.au/collections/adventureline-mens/Adventureline-Mens, whose canonical is https://thestabledoor.com.au/collections/adventureline-mens/adventureline-mens. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://thestabledoor.com.au/pages/all-brands has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://thestabledoor.com.au/collections/adventureline-kids/Adventureline-Kids took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 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.
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
3 broken images
3 images failed to load on a phone, for example https://d.adroll.com/uev/GOI5QXT4ZBH2BKJDDULU4S/VI6GJEH7IVBMBD46KTSAJ3/?af0=0fe6f973&adroll_fpc=a403f0d34817b315fc9c6bd1531716b2-1794050049444&pv=10304881561.997902&arrfrr=https%3A%2F%2Fthestabledoor..
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d19ayerf5ehaab.cloudfront.net/css/product-widget/style.css' from origin 'https://t…”.
2 checks passed
Tap targets are thumb-sized
51 of 58 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,317 words of copy
The homepage carries about 1,317 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Bulk Order”.
72 calls to action
The homepage has 72 calls to action, for example “Contact Us”, “Bulk Order” and “Shop now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
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, 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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 4 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.
38 other companies contacted
Loading the homepage contacts 38 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 thestabledoor.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Avada Seo Suite · Smart Filter Search · Klaviyo Email Marketing Sms · Google Youtube · Smart Product Filters · Frontend · Reviews Co Uk Product And Merchant Review Collection · adroll.com · cloudfront.net
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
- 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 thestabledoor.com.au, including 17 speed issues, 3 SEO issues and 3 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.