moziwash.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, heatmap.com and Clarity and others), adding 1,014 KiB and 1.6 s of main-thread time.

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

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

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

About 489 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

9 long tasks block the main thread while loading, the longest for 98 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 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW LOOK. SAME CLEAN. Meet Our Upgraded Bottle Recyclable a…”.

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

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

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

4 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 151 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.1 MB in 511 requests on a phone: images 1.6 MB (54), other files 1.6 MB (321) and scripts 1.5 MB (95). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example clean-slate_hero.png at 1,800 px wide, shown at 288 px. Resized copies would save about 72 KiB.

1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

7 tap targets are too small or too close together to hit reliably with a finger.

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

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 85 pages on moziwash.com and 14 external pages.

/ and https://www.moziwash.com/blogs/mozi-wash all use the title “Mozi Wash”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.moziwash.com/pages/build-your-bundle, https://www.moziwash.com/pages/why-mozi, https://www.moziwash.com/blogs/mozi-wash, https://www.moziwash.com/pages/refer-a-friend and https://www.moziwash.com/pages/ingredient have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.moziwash.com/collections/shop-detergents, https://www.moziwash.com/collections/shop-dryer-sheets, https://www.moziwash.com/collections/shop-candles-and-linen-spray, https://www.moziwash.com/collections/worlds-best-smelling-laundry-detergent, https://www.moziwash.com/collections/shop-mozi-lab and https://www.moziwash.com/pages/refer-a-friend and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 1,200 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 2 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 58 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 62 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.