urbanhydration.com website review

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

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

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

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

Shopify costs a phone 757 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.

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

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

43 KiB JavaScript is shipped twice across bundles.

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

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

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.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Take Our 5-Question Skincare Quiz”.

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

Real visitors wait 236 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-31, real Chrome visitors' tap response (inp) went from 150 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 859 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 20.4 MB in 593 requests on a phone: media 14.6 MB (2), images 2.2 MB (137) and scripts 1.8 MB (280). Under 2 MB keeps phones on slow connections fast.

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

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 245 pages on urbanhydration.com and 22 external pages.

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

1 error was 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 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.

The homepage has only about 15 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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