Website review, no card needed

tumbleliving.ca logo

tumbleliving.ca website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 82 checks

This review found 31 issues worth fixing on tumbleliving.ca, 9 of them high impact, across 82 checks. The most urgent: page weight: 24.0 MB in 639 requests. 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

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

How it loaded on a phone

  1. tumbleliving.ca at 1.3 s1.3 s
  2. tumbleliving.ca at 2.6 s2.6 s
  3. tumbleliving.ca at 3.9 s3.9 s
  4. tumbleliving.ca at 5.2 s5.2 s
  5. tumbleliving.ca at 6.5 s6.5 s
  6. tumbleliving.ca at 7.8 s7.8 s
  7. tumbleliving.ca at 9.1 s9.1 s
  8. tumbleliving.ca at 10.4 s10.4 s

Speed

12 to fix56
  • Main-thread work: 6.4 s

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

  • 3,544 HTML elements

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

  • Improve image delivery

    950 ms · 1.6 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (recart.com, Google Tag Manager and Facebook and others), adding 2.3 MB and 1.1 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    150 ms · 785 KiB

    51 files are served with short cache lifetimes, so returning visitors download them again (785 KiB).

  • Render-blocking requests

    900 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Google Tag Manager adds 244 ms

    244 ms

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

  • recart.com adds 265 ms

    265 ms

    recart.com costs a phone 265 ms of main-thread work and 223 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.

  • yuma.ai adds 150 ms

    150 ms

    yuma.ai costs a phone 150 ms of main-thread work and 509 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.

  • Shopify adds 70 ms

    70 ms

    Shopify costs a phone 70 ms of main-thread work and 391 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 · 118 KiB

    Polyfills for old browsers add 118 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    42 KiB

    About 42 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: 20 ms

    20 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alt text not provided for this image”.

  • Time to Interactive: 36.8 s

    36.8 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 304 ms

    304 ms

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

  • 1 image without width and height

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

7 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: 1.6 s

    1.6 s

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

  • Real-user INP: 139 ms

    139 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 603 ms

    603 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 24.0 MB in 639 requests

    24.0 MB

    Your homepage downloads 24.0 MB in 639 requests on a phone: media 11.9 MB (16), images 5.4 MB (111) and scripts 3.1 MB (180). Under 2 MB keeps phones on slow connections fast.

  • About 6.8 g of CO₂ per visit

    6.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.81 g of CO₂e: 817.1 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

3 to fixGoogle 9797
  • 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.

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

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

  • Table header text should not be empty (1 element)

    Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 153 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

2 to fixGoogle 6167
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 137 internal links, 17 external

    The homepage links to 137 pages on tumbleliving.ca and 17 external pages.

8 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “Spillproof & Washable Rugs. Perfect for homes with kids and pets. Free Shipping and Returns on all orders.”.

  • One H1 headline

    Your main headline reads: “Rugs Made for Together.”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Tumble - Spillproof & Washable Rugs”.

  • Canonical URL set

    The canonical URL is https://www.tumbleliving.ca/.

  • Structured data in place

    Structured data found: Organization, VideoObject and WebSite.

  • 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.tumbleliving.com/sitemap.xml.

AI search readiness

100
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 (1,998 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.tumbleliving.ca/llms.txt (3 KiB, 14 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 15 linked pages hidden from search

    https://www.tumbleliving.ca/pages/how-were-different, https://www.tumbleliving.ca/pages/reviews, https://www.tumbleliving.ca/pages/faqs, https://www.tumbleliving.ca/pages/favorites, https://www.tumbleliving.ca/collections/all and https://www.tumbleliving.ca/collections/bestsellers and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.tumbleliving.ca/pages/reviews, https://www.tumbleliving.ca/pages/faqs, https://www.tumbleliving.ca/pages/favorites and https://www.tumbleliving.ca/collections/frida-kahlo have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.tumbleliving.ca/pages/faqs, https://www.tumbleliving.ca/collections/all, https://www.tumbleliving.ca/collections/bestsellers, https://www.tumbleliving.ca/collections/9x12-rugs, https://www.tumbleliving.ca/collections/8x10-rugs and https://www.tumbleliving.ca/collections/6x9-rugs and 4 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 50 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 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 “Cannot read properties of null (reading 'find')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    77 of 82 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 1,755 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Washable Rugs” and “Shop Now”.

  • 33 calls to action

    The homepage has 33 calls to action, for example “Shop All”, “Shop All Rugs” and “Get your free design consult”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 17 testimonial or review blocks, 6 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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
  • 5 trackers load before any consent

    5

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

  • 56 other companies contacted

    Loading the homepage contacts 56 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 tumbleliving.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Geo Pro Geolocation · Klaviyo Email Marketing Sms · Okendo · Recart Sms List Growth · Elevar Conversion Tracking · Easylocation · Event Promotion Bar · hextom.com · amazonaws.com · retention.com

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
React
E-commerce
Shopify
Analytics
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 31 issues on tumbleliving.ca, including 18 speed issues, 2 SEO issues and 1 conversion gap. 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