Website review, no card needed
ashleyhomestore.ca website review
Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 86 checks
This review found 42 issues worth fixing on ashleyhomestore.ca, 20 of them high impact, across 86 checks. The most urgent: avoid multiple page redirects. 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
65D- #117,196 of 126,508 reviewed websitesbeats 6%
- #67,980 of 70,497 online storesbeats 3%
- #62,113 of 63,990 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 208 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 226 ms |
| Jul 4, 2026 | 228 ms |
| Jul 11, 2026 | 226 ms |
| Jul 18, 2026 | 224 ms |
| Jul 25, 2026 | 222 ms |
| Aug 1, 2026 | 221 ms |
| Aug 8, 2026 | 227 ms |
| Aug 15, 2026 | 228 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 226 ms |
| Sep 12, 2026 | 225 ms |
| Sep 19, 2026 | 225 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 228 ms |
| Oct 17, 2026 | 227 ms |
| Oct 24, 2026 | 223 ms |
| Oct 31, 2026 | 220 ms |
| Nov 7, 2026 | 216 ms |
| Nov 14, 2026 | 211 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.8 s
1.7 s
2.5 s
3.3 s
4.2 s
5.0 s
5.8 s
6.7 s
Speed
Avoid multiple page redirects
39.6 sThe page goes through 1 redirect before it starts loading, costing about 39.6 s. Link and advertise the final URL directly.
Reduce unused JavaScript
12.7 s · 2.5 MBAbout 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.7 s faster on a phone.
Optimizely adds 2.2 s
2.2 sOptimizely costs a phone 2.2 s of main-thread work and 4 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.
Use efficient cache lifetimes
1.5 s · 274 KiB15 files are served with short cache lifetimes, so returning visitors download them again (274 KiB).
Main-thread work: 10.5 s
A phone's processor spends 10.5 s on main-thread work while loading, 7.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 7
7/100Your mobile performance score is 7. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Optimizely, affirm.ca and Bazaarvoice and others), adding 625 KiB and 2.8 s of main-thread time.
Render-blocking requests
900 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Improve image delivery
885 KiB2 images could be 885 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
750 ms · 98 KiB98 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
2,733 HTML elements
The page has 2,733 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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 CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 53.1 s
53.1 sYour largest element takes 53.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 55.0 s
55.0 sThe page becomes fully interactive after 55.0 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.734
0.734The layout shifts by 0.734 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 208 ms to 211 ms 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 INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 220 ms
220 msReal visitors wait 220 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 13.7 MB in 334 requests
13.7 MBYour homepage downloads 13.7 MB in 334 requests on a phone: images 8.6 MB (63), scripts 3.3 MB (105) and other files 942 KiB (139). Under 2 MB keeps phones on slow connections fast.
About 3.9 g of CO₂ per visit
3.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.89 g of CO₂e: 466.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (3 elements).
[role]s do not have all required [aria-*] attributes
[role]s do not have all required [aria-*] attributes (2 elements).
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
14 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 14 passed and 3 failed. 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.
Structured data has 2 problems
Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//ashleyhomestore.ca/cdn/shop/files/AshleyHomeStore_Web…”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
453 internal links, 7 external
The homepage links to 453 pages on ashleyhomestore.ca and 7 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Ashley Canada is your trusted name for quality furniture and mattresses. Enjoy trending styles and massive savings! 100…”.
Title: 39 characters
Your title is a healthy 39 characters: “Ashley Furniture Canada | Ashley Canada”.
Canonical URL set
The canonical URL is https://ashleyhomestore.ca/.
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://ashleyhomestore.ca/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
No llms.txt
There is no https://ashleyhomestore.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Other pages
5 pages without an H1
https://ashleyhomestore.ca/pages/about, https://ashleyhomestore.ca/collections/deals, https://ashleyhomestore.ca/pages/financing, https://ashleyhomestore.ca/collections/living-room and https://ashleyhomestore.ca/collections/sofas 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 141 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
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 5 pages that loaded have a <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.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.
Missing source maps
Large scripts ship without source maps.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
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 call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 11 words
The homepage has only about 11 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
25 calls to action
The homepage has 25 calls to action, for example “shop hot buys”, “Shop Now, click to know more! Shop Now” and “Shop All Mattresses”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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 Clarity 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.
46 cookies set on arrival
46Opening the homepage sets 46 cookies, 46 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.
65 other companies contacted
Loading the homepage contacts 65 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 ashleyhomestore.ca, 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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Eg Auto Add To Cart · Attentive · Extole · Region Restrictions · fairstone.ca · wheelio-app.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
- Framework
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Hamilton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on ashleyhomestore.ca, including 21 speed issues, 4 SEO issues and 4 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.