mayuwater.com website review

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

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

8 third-party services load with your homepage (ContentSquare, loox.io and reamaze.com and others), adding 2.3 MB and 680 ms of main-thread time.

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

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

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

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

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

Shopify costs a phone 23 ms of main-thread work and 1.5 MB 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.

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

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

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

10 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Products for the best hydration. Period.”. Most of its time is element render delay (2.6 s).

Your homepage downloads 6.3 MB in 290 requests on a phone: images 2.5 MB (101), media 1.3 MB (1) and scripts 1.3 MB (88). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 1_3_1.webp at 2,880 px wide, shown at 390 px. Resized copies would save about 189 KiB.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is 76 characters, so Google will cut it off around 60: “Ultimate Hydration Solution: MAYU Water Structured Water Carafe – Mayu Water”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 206 pages on mayuwater.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://mayuwater.com/a/resources, https://mayuwater.com/a/resources/structured-water and https://mayuwater.com/a/resources/minerals all use the title “Mayu Water”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mayuwater.com/collections/upsell, https://mayuwater.com/collections/swirl-accessories-1, https://mayuwater.com/collections/essential-minerals, https://mayuwater.com/collections/electrolytes, https://mayuwater.com/collections/water-bottles and https://mayuwater.com/pages/science and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://mayuwater.com/pages/science, https://mayuwater.com/pages/structured-water, https://mayuwater.com/pages/3rd-party-tested and https://mayuwater.com/pages/story have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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