soberish.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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 4.9 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Shopify, rebuyengine.com and Klaviyo and others), adding 4.6 MB and 1.2 s of main-thread time.

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

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

1 image could be 40 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

rebuyengine.com costs a phone 253 ms of main-thread work and 719 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.

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

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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

Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Friends toasting with alcohol-free drinks on a sunny patio”.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.1 MB in 397 requests on a phone: images 2.9 MB (25), scripts 2.5 MB (145) and other files 1.0 MB (187). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 240.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.

Links must have discernible text: 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.

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

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

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.

Headings skip levels (h2 → h4), 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 153 pages on soberish.com and 10 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://soberish.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://soberish.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://soberish.com/pages/hemp-policy, https://soberish.com/customer_authentication/redirect, https://soberish.com/collections/calm and https://soberish.com/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://soberish.com/collections/edibles-gummies, whose canonical is https://soberish.com/collections/edibles. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://soberish.com/pages/hemp-policy and https://soberish.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 16 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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