aquabliss.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 1.7 MB and 1.3 s of main-thread time.

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

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

About 644 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 472 ms of main-thread work and 553 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 207 ms of main-thread work and 322 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.

Shopify costs a phone 190 ms of main-thread work and 322 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,962 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

58 KiB could be saved by minifying JavaScript.

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

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 20.0 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 18.5 MB in 333 requests on a phone: media 14.7 MB (1), scripts 1.8 MB (118) and other files 805 KiB (120). Under 2 MB keeps phones on slow connections fast.

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

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

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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.

Your <h1> is empty.

The homepage links to 129 pages on aquabliss.com and 13 external pages.

https://aquabliss.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://aquabliss.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://aquabliss.com/collections/all, https://aquabliss.com/customer_authentication/redirect, https://aquabliss.com/policies/shipping-policy, https://aquabliss.com/policies/terms-of-service, https://aquabliss.com/collections/shower-filter-cartridge-bundles and https://aquabliss.com/pages/compare-our-range have no meta description, so Google writes the search snippet from whatever text it finds.

https://aquabliss.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/VKDDK9/images/50e32ae4-e33c-4fd1-bce6-3815d21bfcbd.png.

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

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

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

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