slendertone.com website review

The page goes through 1 redirect before it starts loading, costing about 29.7 s. Link and advertise the final URL directly.

23 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

About 923 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

A phone's processor spends 4.8 s on main-thread work while loading, 2.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, Yotpo and Cloudflare CDN and others), adding 1.5 MB and 1.2 s of main-thread time.

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

111 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Polyfills for old browsers add 70 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).

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 40.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 59.4 s. Good is under 3.8 s.

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

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

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

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

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

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

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

Your homepage downloads 13.4 MB in 472 requests on a phone: images 7.2 MB (122), scripts 4.8 MB (162) and other files 926 KiB (149). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example Bag_Controller_01.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 1.3 MB.

openart-image__E6vPZOD_1763028222580_raw.jpg weighs 567 KiB. On a phone connection a single image that size takes seconds.

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

12 images (973 KiB) 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.

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

1 dropdown has no label.

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

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

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

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

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

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 60 pages on slendertone.com and 5 external pages.

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.

https://eu.slendertone.com/products/ultimate-toning-bundle-women-abs7-bottom-arms declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://eu.slendertone.com/products/ultimate-toning-bundle-women-abs7-bottom-arms all use the title “Slendertone Official Online Store – Slendertone EU”. Search engines can't tell which page to show for a search, so each competes with the others.

https://eu.slendertone.com/pages/why-slendertone, https://eu.slendertone.com/pages/help-centre and https://eu.slendertone.com/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 images failed to load on a phone, for example https://us.slendertone.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies (measured from a US location before any click).

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