Website review, no card needed

sleepcountry.ca logo

sleepcountry.ca website review

Visit site (opens in a new tab)Reviewed 29 October 202649 issues · 88 checks

This review found 49 issues worth fixing on sleepcountry.ca, 23 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s1.9 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.3 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
205 ms166 msMay 9Oct 24192 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026175 ms
May 16, 2026171 ms
May 23, 2026170 ms
May 30, 2026170 ms
Jun 6, 2026170 ms
Jun 13, 2026171 ms
Jun 20, 2026171 ms
Jun 27, 2026171 ms
Jul 4, 2026175 ms
Jul 11, 2026178 ms
Jul 18, 2026178 ms
Jul 25, 2026178 ms
Aug 1, 2026179 ms
Aug 8, 2026187 ms
Aug 15, 2026195 ms
Aug 22, 2026197 ms
Aug 29, 2026200 ms
Sep 5, 2026191 ms
Sep 12, 2026188 ms
Sep 19, 2026189 ms
Sep 26, 2026191 ms
Oct 3, 2026193 ms
Oct 10, 2026194 ms
Oct 17, 2026193 ms
Oct 24, 2026192 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

Full-page screenshot of sleepcountry.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sleepcountry.ca at 1.2 s1.2 s
  2. sleepcountry.ca at 2.5 s2.5 s
  3. sleepcountry.ca at 3.7 s3.7 s
  4. sleepcountry.ca at 4.9 s4.9 s
  5. sleepcountry.ca at 6.2 s6.2 s
  6. sleepcountry.ca at 7.4 s7.4 s
  7. sleepcountry.ca at 8.7 s8.7 s
  8. sleepcountry.ca at 9.9 s9.9 s

Speed

14 to fix30
  • Use efficient cache lifetimes

    1.6 s · 6.1 MB

    105 files are served with short cache lifetimes, so returning visitors download them again (6.1 MB).

  • Render-blocking requests

    5.0 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.

  • Reduce unused JavaScript

    2.3 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.7 s

    A phone's processor spends 7.7 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,332 HTML elements

    The page has 3,332 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    650 ms · 3.8 MB

    46 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Bigcommerce and Noibu and others), adding 3.5 MB and 2.6 s of main-thread time.

  • Reduce unused CSS

    910 ms · 163 KiB

    About 163 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.

  • Google Tag Manager adds 776 ms

    776 ms

    Google Tag Manager costs a phone 776 ms of main-thread work and 695 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.

  • Bigcommerce adds 572 ms

    572 ms

    Bigcommerce costs a phone 572 ms of main-thread work and 1.7 MB 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.

  • Noibu adds 315 ms

    315 ms

    Noibu costs a phone 315 ms of main-thread work and 161 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.

  • Klaviyo adds 185 ms

    185 ms

    Klaviyo costs a phone 185 ms of main-thread work and 332 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 KiB

    Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need.

  • 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 JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • 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 LCP: 4.3 s

    4.3 s

    Real visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.3 s

    3.3 s

    Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 8.5 s

    8.5 s

    The first text or image appears after 8.5 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 31.9 s

    31.9 s

    Your largest element takes 31.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “06 DAYS : 02 HOURS : 34 MINS Get up to 35% off mattresses, …”.

  • Speed Index: 19.0 s

    19.0 s

    Visually, the page fills in at 19.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 42.0 s

    42.0 s

    The page becomes fully interactive after 42.0 s. Good is under 3.8 s.

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 219 ms

    219 ms

    Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 175 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 14.1 MB in 296 requests

    14.1 MB

    Your homepage downloads 14.1 MB in 296 requests on a phone: images 9.5 MB (107), scripts 2.8 MB (92) and media 751 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 16 images far larger than shown

    1.7 MB

    16 images are downloaded at several times the size a phone draws them, for example BF26-home-feature-3-en:4-3 at 800 px wide, shown at 171 px. Resized copies would save about 1.7 MB.

  • 38 images in older formats

    38 images (6.8 MB) 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.

  • 19 images below the first screen load straight away

    19 images further down the page (3.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.0 g of CO₂ per visit

    3.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.99 g of CO₂e: 479.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

10 to fixGoogle 8186
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Interactive controls must not be nested (12 elements)

    Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 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.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (27 elements)

    All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 6985
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Trusted Brands Behind Better Sleep.” and “Holiday Gift Shop”). One clear main headline is easier for people and search engines.

  • 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.

  • 12 links crawlers can't follow

    12 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 322 internal links, 2 external

    The homepage links to 322 pages on sleepcountry.ca and 2 external pages.

5 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Sleep Country Canada is Canada's top mattress and bedding company, browse the best mattresses, bedding, and accessories…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Canada's Top Mattresses and Bedding | Sleep Country Canada”.

  • Canonical URL set

    The canonical URL is https://en.sleepcountry.ca/.

  • 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://en.sleepcountry.ca/xmlsitemap.php.

AI search readiness

1 to fix88
  • 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,936 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://en.sleepcountry.ca/llms.txt (3 KiB, 22 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 116 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211034998&Ver=2&mid=6a02ae34-d198-4569-936c-8eeeeefad67a&bo=1&sid=22c55480d35911f19e954908a7a300ec&vid=22c556a0d35911f1ae65af27280ff3ad&vids=1&msclkid=N&pi=918639831&l.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    100 of 107 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,037 words of copy

    The homepage carries about 1,037 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Mattresses” and “Shop All”.

  • 48 calls to action

    The homepage has 48 calls to action, for example “Shop All”, “Shop All Mattresses” and “Shop All Pillows”.

  • 9 short forms

    9 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 8 phone links and 0 email links.

  • 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

1 to fix
  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 6 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.

  • 41 cookies set on arrival

    41

    Opening the homepage sets 41 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.

  • 55 other companies contacted

    Loading the homepage contacts 55 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 sleepcountry.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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 sleepcountry.ca, including 25 speed issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25