waterscience.in website review

Shopify costs a phone 2.2 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 10.5 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Shopify, shopflo.co and Clarity and others), adding 3.8 MB and 2.6 s of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 630 ms faster on a phone.

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

About 75 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.

shopflo.co costs a phone 181 ms of main-thread work and 1.8 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.

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

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

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

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

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

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Real visitors wait 250 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

7 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-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 450 requests on a phone: scripts 3.2 MB (122), images 1.7 MB (84) and other files 1.0 MB (185). Under 2 MB keeps phones on slow connections fast.

Versa_Versa_Skin_Care_Mobile_Banner_1_1_5.jpg 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).

10 images further down the page (476 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example 61nxL6v701L._SL1080.jpg at 1,080 px wide, shown at 135 px. Resized copies would save about 162 KiB.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

7 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your <h1> is empty.

The homepage links to 163 pages on waterscience.in and 17 external pages.

https://www.waterscience.in/collections/water-saving-nozzles, https://www.waterscience.in/pages/water-softeners, https://www.waterscience.in/collections/health-faucet, https://www.waterscience.in/collections/cleaning-care, https://www.waterscience.in/collections/mainline-filters and https://www.waterscience.in/collections/kiddo-hand-shower-filters and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.waterscience.in/pages/water-softeners has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

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