mountainviewsoap.com website review

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

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

POWr costs a phone 415 ms of main-thread work and 13 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 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

21 KiB could be saved by minifying JavaScript.

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

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

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

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 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

The layout shifts by 0.588 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 4.1 MB in 791 requests on a phone: other files 2.0 MB (558), scripts 1.4 MB (161) and fonts 252 KiB (15). Under 2 MB keeps phones on slow connections fast.

Holiday_Collection_Banner_2026.png 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.15 g of CO₂e: 138.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

Your <h1> is empty.

The homepage links to 38 pages on mountainviewsoap.com and 13 external pages.

/collections/all, /collections/currently-available, /collections/halloween-collection, /collections/fall-collection, /pages/about and /blogs/mvs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /products/%F0%9F%9A%97-fall-car-diffusers, whose canonical is /products/%f0%9f%9a%97-fall-car-diffusers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/currently-available, /pages/contact-us and /blogs/mvs have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “window.fd is not a function”.

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

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

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

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

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