drinksabe.com website review

15 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Optanon and others), adding 878 KiB and 414 ms of main-thread time.

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

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

About 32 KiB of CSS is downloaded but never applied on this page.

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

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

5 KiB could be saved by minifying CSS.

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “JIM ANDREWS | FOUNDER “For those times when only an actual …”.

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

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

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

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

10 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' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 19.8 MB in 75 requests on a phone: media 16.6 MB (1), images 2.1 MB (32) and scripts 820 KiB (14). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example box-moscow-mule-no-shadow.webp at 1,200 px wide, shown at 77 px. Resized copies would save about 1.1 MB.

4 images further down the page (450 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.60 g of CO₂e: 672.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “Home - SABÉ Beverages”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 16 pages on drinksabe.com and 6 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.

The HTML your server sends has 270 of the 500 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.drinksabe.com/products, https://www.drinksabe.com/store-locator, https://www.drinksabe.com/cocktail/margarita, https://www.drinksabe.com/cocktail/moscow-mule, https://www.drinksabe.com/cocktail/mojito and https://www.drinksabe.com/cocktail/espresso-martini and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.drinksabe.com/products has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.drinksabe.com/products, https://www.drinksabe.com/store-locator, https://www.drinksabe.com/cocktail/margarita, https://www.drinksabe.com/cocktail/moscow-mule, https://www.drinksabe.com/cocktail/mojito and https://www.drinksabe.com/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.