mojudrinks.com website review

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

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

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

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

8 third-party services load with your homepage (Kaltura Video Platform, Yotpo and Google Tag Manager and others), adding 3.1 MB and 1.8 s of main-thread time.

35 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

About 221 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.

Kaltura Video Platform costs a phone 443 ms of main-thread work and 1.1 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.

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

6 images could be 271 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.

Yotpo costs a phone 365 ms of main-thread work and 532 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.

Google Tag Manager costs a phone 352 ms of main-thread work and 509 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 89 ms of main-thread work and 526 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 59 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

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

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

Your homepage downloads 5.8 MB in 342 requests on a phone: scripts 2.6 MB (107), images 1.6 MB (49) and other files 1.2 MB (154). Under 2 MB keeps phones on slow connections fast.

14 images (551 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example header_logo.webp at 1,600 px wide, shown at 150 px. Resized copies would save about 78 KiB.

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

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

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

All page content should be contained by landmarks: 19 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.

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

1 link inside paragraphs relies on colour alone to stand out.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 81 pages on mojudrinks.com and 5 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://mojudrinks.com/collections/all, https://mojudrinks.com/pages/shots and https://mojudrinks.com/pages/rewards have no meta description, so Google writes the search snippet from whatever text it finds.

https://mojudrinks.com/collections/all and https://mojudrinks.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://mojudrinks.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Framing 'https://mojudrinks.com/' violates the following Content Security Policy directive: "frame-ancestors 'none'". T…”.

Chrome logged issues while loading the page (“Content security policy”).

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.

The homepage carries about 1,157 words of visible text.

Before a visitor clicks anything, the page loads Hotjar, Klaviyo and Meta Pixel (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, 2 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.