stonercarcare.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.5 MB and 1.0 s of main-thread time.

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

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

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

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

Shopify costs a phone 309 ms of main-thread work and 625 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 82 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.

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

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

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

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.

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

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man inside a car wipes the dashboard with a blue microfib…”.

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

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

Your homepage downloads 4.2 MB in 400 requests on a phone: scripts 1.6 MB (180), images 1.1 MB (31) and other files 994 KiB (149). Under 2 MB keeps phones on slow connections fast.

free-moab-offer-drawer.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 1.20 g of CO₂e: 143.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 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: 54 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 260 pages on stonercarcare.com and 17 external pages.

There is no https://stonercarcare.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to https://stonercarcare.com/collections/glass-cleaners, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 157 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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 615 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, Klaviyo and Meta Pixel 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 17 cookies, 1 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.