cgpurewash.com website review

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

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

About 318 KiB of JavaScript is downloaded but never used on this page.

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

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

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

5 third-party services load with your homepage (Shopify, Google CDN and nfcube.com and others), adding 496 KiB and 170 ms of main-thread time.

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

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

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

About 26 KiB of CSS is downloaded but never applied on this page.

12 KiB could be saved by minifying JavaScript.

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Canadian-made skincare, made with care: small-batch soap, b…”.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.2 MB in 184 requests on a phone: images 700 KiB (16), other files 692 KiB (72) and scripts 592 KiB (51). Under 2 MB keeps phones on slow connections fast.

pure-wash-blue-circular-logo-peach-brushstroke.webp 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).

1 image (184 KiB) is 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 0.62 g of CO₂e: 74.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn'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.

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

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

Your <h1> is empty.

The homepage links to 157 pages on cgpurewash.com and 27 external pages.

https://www.cgpurewash.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.cgpurewash.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

https://www.cgpurewash.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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