shaktimats.pl website review

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

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

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

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

About 764 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.

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

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

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

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

About 93 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.

rebuyengine.com costs a phone 146 ms of main-thread work and 711 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,878 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

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.

Your largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A shirtless man sitting on a bed, Shakti Mat and Pillow, wi…”.

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

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

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

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

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

Your homepage downloads 49.5 MB in 341 requests on a phone: media 40.9 MB (7), fonts 2.5 MB (8) and scripts 2.2 MB (123). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Shakti_premium_acupressure_mat_summer_24_black_jpg_f88e49dd- at 2,048 px wide, shown at 48 px. Resized copies would save about 218 KiB.

1 image further down the page (219 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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 Europe”.

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

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

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

Your <h1> is empty.

The homepage links to 51 pages on shaktimats.pl and 12 external pages.

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

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

https://shaktimats.pl/pages/accessibility-statement, https://shaktimats.pl/pages/acupressure-mat, https://shaktimats.pl/pages/wonderball, https://shaktimats.pl/pages/why-buy-shakti, https://shaktimats.pl/blogs/journal and https://shaktimats.pl/pages/our-story and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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 914 words of visible text.

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

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

Opening the homepage sets 32 cookies, 8 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.