Website review, no card needed

shaktimats.be logo

shaktimats.be website review

Visit site (opens in a new tab)Reviewed 9 November 202641 issues · 82 checks

This review found 41 issues worth fixing on shaktimats.be, 14 of them high impact, across 82 checks. The most urgent: avoid multiple page redirects. 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 shaktimats.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shaktimats.be at 2.2 s2.2 s
  2. shaktimats.be at 4.3 s4.3 s
  3. shaktimats.be at 6.5 s6.5 s
  4. shaktimats.be at 8.7 s8.7 s
  5. shaktimats.be at 10.9 s10.9 s
  6. shaktimats.be at 13.0 s13.0 s
  7. shaktimats.be at 15.2 s15.2 s
  8. shaktimats.be at 17.4 s17.4 s

Speed

16 to fix31
  • Avoid multiple page redirects

    5.3 s

    The page goes through 2 redirects before it starts loading, costing about 5.3 s. Link and advertise the final URL directly.

  • Document request latency

    5.2 s

    The HTML itself could arrive about 5.2 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Main-thread work: 13.1 s

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. 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 (shaktimat.com, Google Tag Manager and omnisnippet1.com and others), adding 5.4 MB and 2.4 s of main-thread time.

  • shaktimat.com adds 829 ms

    829 ms

    shaktimat.com costs a phone 829 ms of main-thread work and 3.8 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.

  • Reduce unused JavaScript

    300 ms · 770 KiB

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

  • Use efficient cache lifetimes

    150 ms · 695 KiB

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

  • Google Tag Manager adds 425 ms

    425 ms

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

  • Improve image delivery

    150 ms · 254 KiB

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

  • Reduce unused CSS

    300 ms · 89 KiB

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

  • omnisnippet1.com adds 341 ms

    341 ms

    omnisnippet1.com costs a phone 341 ms of main-thread work and 119 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 314 ms. During a long task the page ignores taps.

  • rebuyengine.com adds 215 ms

    215 ms

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

  • 1,723 HTML elements

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

  • Legacy JavaScript

    60 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 27 ms

    27 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 24.8 s

    24.8 s

    Your largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman lying on a Shakti mat and pillow on a carpet”.

  • Speed Index: 24.1 s

    24.1 s

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

  • Time to Interactive: 41.7 s

    41.7 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

    The first text or image appears after 4.4 s on a phone. Good is under 1.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 FCP: 1.8 s

    1.8 s

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 194 ms

    194 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 609 ms

    609 ms

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

  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

1 to fix70
  • Page weight: 8.3 MB in 306 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 306 requests on a phone: fonts 2.5 MB (8), scripts 2.2 MB (121) and images 1.8 MB (42). Under 2 MB keeps phones on slow connections fast.

  • About 2.4 g of CO₂ per visit

    2.35 g

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

4 to fixGoogle 9594
  • 38 text elements with low contrast

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

  • 16 images without alt text

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

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

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

  • Headings should not be empty (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 10075
  • Title is long (79 characters)

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

  • Canonical points to another host

    Your canonical URL points to shaktimat.eu, not shaktimats.be, so Google may credit that host instead.

  • Meta description is long (287 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.shaktimat.eu)”.

  • One H1 headline

    Your <h1> is empty.

  • 50 internal links, 12 external

    The homepage links to 50 pages on shaktimats.be and 12 external pages.

3 checks passed
  • 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://shaktimats.be/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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,501 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://shaktimats.be/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

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

  • 1 page without a meta description

    https://shaktimats.be/pages/which-mat-is-right-for-you has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://shaktimats.be/pages/acupressure-mat, https://shaktimats.be/pages/wonderball, https://shaktimats.be/blogs/journal, https://shaktimats.be/pages/shakti-shala-app, https://shaktimats.be/collections/all and https://shaktimats.be/collections/accessories use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://shaktimats.be/pages/accessibility-statement, https://shaktimats.be/products/wonderball-duo, https://shaktimats.be/pages/acupressure-mat, https://shaktimats.be/pages/wonderball, https://shaktimats.be/pages/why-buy-shakti and https://shaktimats.be/blogs/journal and 9 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 24 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.

  • 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

2 to fixGoogle 9687
  • 10 small tap targets

    10 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 checks passed
  • 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 844 words of copy

    The homepage carries about 844 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 All”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Shop All” and “Shop Duo”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Pinterest Tag and 1 more (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 7 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.

  • 48 other companies contacted

    Loading the homepage contacts 48 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 shaktimats.be, 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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geoip Country Redirect · Weglot Translate Your Store · Mp Instagram Feed · Tolstoy · Easy Variant Images · Rebuy Personalization Engine · Okendo · Omnisend · Eu Cookie Bar · Back In Stock · gorgias.chat · cloudfront.net · amazonaws.com · 9gtb.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

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on shaktimats.be, including 23 speed issues, 5 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