shaktimat.ca website review

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

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

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

Shopify costs a phone 27 ms of main-thread work and 33.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.

About 626 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

10 images could be 370 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

Your homepage downloads 47.3 MB in 234 requests on a phone: media 40.9 MB (7), images 1.9 MB (31) and scripts 1.7 MB (87). Under 2 MB keeps phones on slow connections fast.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Your title is 79 characters, so Google will cut it off around 60: “The Shakti Acupressure Mat - Total mind and body relaxation – Shakti Mat Canada”.

Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 55 pages on shaktimat.ca and 5 external pages.

https://shaktimat.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://shaktimat.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://shaktimat.ca/pages/wonderball and https://shaktimat.ca/products/wonderball all use the title “Wonderball – Shakti Mat Canada”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shaktimat.ca/pages/which-mat-is-right-for-you and https://shaktimat.ca/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://shaktimat.ca/collections/all, https://shaktimat.ca/pages/acupressure-mat, https://shaktimat.ca/pages/wonderball and https://shaktimat.ca/blogs/journal use the same meta description. A description written for each page earns more clicks.

https://shaktimat.ca/collections/all and https://shaktimat.ca/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://shaktimat.ca/products/wonderball-duo, https://shaktimat.ca/collections/all and https://shaktimat.ca/products/wonderball have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

Opening the homepage sets 13 cookies, 7 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.