shopcloudsole.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Shopify and Google Tag Manager and others), adding 2.2 MB and 1.1 s of main-thread time.

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

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

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

alia-prod.com costs a phone 440 ms of main-thread work and 579 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.

11 images could be 486 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

Your largest element takes 20.3 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 21.3 s. Good is under 3.8 s.

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

The first text or image appears after 4.3 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 179 ms to 260 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 5.4 MB in 543 requests on a phone: scripts 2.1 MB (84), other files 1.5 MB (370) and images 1.1 MB (25). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 9 characters: “CloudSole”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Look taller. Walk taller.Feel the difference inst…”). One clear main headline is easier for people and search engines.

The homepage links to 80 pages on shopcloudsole.com and 1 external page.

https://shopcloudsole.com/collections/all, https://shopcloudsole.com/policies/shipping-policy and https://shopcloudsole.com/pages/kit-collections have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://shopcloudsole.com/products/cloudsole%C2%AE-wide-insoles-1, whose canonical is https://shopcloudsole.com/products/cloudsole%c2%ae-wide-insoles-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shopcloudsole.com/collections/all, https://shopcloudsole.com/policies/shipping-policy, https://shopcloudsole.com/pages/kit-collections, https://shopcloudsole.com/products/cloudsole-insoles, https://shopcloudsole.com/products/cloudsole%C2%AE-wide-insoles-1 and https://shopcloudsole.com/products/height-boosting-insoles and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://shopcloudsole.com/policies/shipping-policy has 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.

https://shopcloudsole.com/products/height-boosting-insoles, https://shopcloudsole.com/products/cloudsole-comfort-lift-insoles, https://shopcloudsole.com/products/stealthlifts, https://shopcloudsole.com/products/recovery-slides, https://shopcloudsole.com/products/cushion-padded-cloud-sock and https://shopcloudsole.com/products/wool-socks%C2%AE and 2 others took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'includes') https://shopcloudsole.com/:79:605 NodeList.forEach (<anonymous>)”.

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

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

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