waterdrop.ba website review

A phone's processor spends 5.9 s on main-thread work while loading, 2.2 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 LoyaltyLion and others), adding 81.9 MB and 749 ms of main-thread time.

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

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

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

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

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

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

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

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

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

Klaviyo costs a phone 139 ms of main-thread work and 344 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.

LoyaltyLion costs a phone 60 ms of main-thread work and 337 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.

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

2 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 19 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.

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.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tri kutije sa vrećicama okusa na crnoj ovalnoj ploči uz mal…”.

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

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

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

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 85.3 MB in 357 requests on a phone: media 80.0 MB (16), images 2.0 MB (76) and scripts 1.6 MB (167). Under 2 MB keeps phones on slow connections fast.

ML-Homepage-Thumbnail-Mobile_dfe72e52-8f83-4e58-b182-5f38176 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).

1 image is downloaded at several times the size a phone draws it, for example 2-do-not-delete-social-proof-thumbnail.png at 1,000 px wide, shown at 58 px. Resized copies would save about 62 KiB.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

lang attribute must have a valid value: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 8 <h1> headlines (“”, “Pretraga” and “Korpa”). One clear main headline is easier for people and search engines.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 137 pages on waterdrop.ba and 8 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://waterdrop.ba/collections/turbo-boost-2, https://waterdrop.ba/collections/bestseleri, https://waterdrop.ba/collections/microdrink, https://waterdrop.ba/collections/microenergy, https://waterdrop.ba/collections/microlyte and https://waterdrop.ba/collections/svi-okusi and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=17497809&tm=gtm002&Ver=2&mid=4ea3a9ab-189f-4cbc-bc56-89aff49a9e6b&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=waterdrop%C2%AE%20-%20Drink%20More%20Water%20.

23 of 52 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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