ommushrooms.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and iovation and others), adding 2.4 MB and 1.3 s of main-thread time.

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

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

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

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

19 KiB could be saved by minifying CSS.

8 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 21.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two friends laughing as they walk a sandy coastal path abov…”.

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

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

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

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

1 image 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 152 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.4 MB in 438 requests on a phone: scripts 1.9 MB (98), other files 1.4 MB (264) and images 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example pack-coffeebooster-60g.webp at 1,200 px wide, shown at 212 px. Resized copies would save about 2.3 MB.

pack-coffeebooster-60g.webp weighs 638 KiB. On a phone connection a single image that size takes seconds.

13 images (3.0 MB) are 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 1.53 g of CO₂e: 184.1 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.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 68 characters, so Google will cut it off around 60: “Best Organic Mushroom Powder & Capsules | Om – Om Mushroom Superfood”.

There are 2 <h1> headlines (“” and “Black Friday: 35% off your first two subscription…”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 165 pages on ommushrooms.com and 1 external page.

https://ommushrooms.com/collections/all, https://ommushrooms.com/pages/quiz, https://ommushrooms.com/collections/focus-memory, https://ommushrooms.com/collections/calm-stress-sleep, https://ommushrooms.com/collections/energy-endurance and https://ommushrooms.com/collections/immunity-defense and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://ommushrooms.com/pages/quiz has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 62 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_EMPTY_RESPONSE”.

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

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