drinku.com website review

About 870 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Shopify and others), adding 2.2 MB and 1.9 s of main-thread time.

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

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

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

alia-prod.com costs a phone 423 ms of main-thread work and 659 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 259 ms of main-thread work and 102 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.

Polyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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

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

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

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.8 MB in 310 requests on a phone: scripts 2.4 MB (116), images 1.1 MB (22) and other files 677 KiB (120). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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 57 pages on drinku.com and 2 external pages.

https://www.calmingco.com/pages/lab-testing is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.calmingco.com/pages/recipes, https://www.calmingco.com/blogs/news and https://www.calmingco.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.calmingco.com/collections/shop-all, https://www.calmingco.com/pages/reviews, https://www.calmingco.com/pages/the-science, https://www.calmingco.com/pages/faq, https://www.calmingco.com/pages/our-story and https://www.calmingco.com/pages/recipes and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97142048&Ver=2&mid=31e98ccd-2c71-4a26-8162-eab631e98ebf&bo=1&sid=569eb080dc9a11f1857e3fc0d8cfebbc&vid=569ecf50dc9a11f1973d4bf1d9cfd403&vids=1&msclkid=N&pi=918639831&lg.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 602 words of visible text.

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