stonz.com website review

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

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

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

8 third-party services load with your homepage (shipinsure.io, Shopify and Klaviyo and others), adding 2.9 MB and 1.9 s of main-thread time.

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

22 images could be 1,000 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.

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

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

Shopify costs a phone 464 ms of main-thread work and 1,007 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.

shipinsure.io costs a phone 484 ms of main-thread work and 341 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.

Klaviyo costs a phone 335 ms of main-thread work and 616 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.

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

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

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

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

13 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 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stonz_Winter 2026_Mobile”.

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

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

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

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

14 images 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' tap response (inp) went from 186 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 26.1 MB in 448 requests on a phone: media 14.2 MB (1), images 7.7 MB (79) and scripts 2.6 MB (163). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example Menu_Accessories4_3x_9e8aeca7-817f-4d93-a098-bf9a2a6ff8b8.pn at 1,492 px wide, shown at 133 px. Resized copies would save about 1.1 MB.

2a05db2377354bcc878d9f04541cafdc.thumbnail.0000000000.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Elements must only use permitted ARIA attributes: 62 elements on the page fail this check, rated serious by axe-core.

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/Stonz_header_logo_black2.svg")”.

The homepage links to 209 pages on stonz.com and 8 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://stonz.com/en-us/collections/cruiser%E2%84%A2-everyday, whose canonical is https://stonz.com/en-us/collections/cruiser%e2%84%a2-everyday. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://stonz.com/en-us/pages/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

https://stonz.com/en-us/collections/booties and https://stonz.com/en-us/collections/boots took over 3 s to send their HTML from our server.

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

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

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 671 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 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 25 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.