rawjuicery.com website review

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

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

4 images could be 311 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

8 third-party services load with your homepage (superfiliate-cdn.com, Unpkg and Attentive and others), adding 19.6 MB and 328 ms of main-thread time.

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

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

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

46 KiB could be saved by minifying JavaScript.

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

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

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

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.

4 KiB could be saved by minifying CSS.

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 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Organic Juice Cleanse”.

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

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

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

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

12 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 87 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.9 MB in 212 requests on a phone: media 18.0 MB (2), images 1.2 MB (31) and other files 869 KiB (108). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example Free_Order_Protection_Mobile_v01.webp at 1,227 px wide, shown at 358 px. Resized copies would save about 713 KiB.

18 images (5.0 MB) 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.

9 images further down the page (2.7 MB) 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.93 g of CO₂e: 711.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”.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

4 visible links have no text or label, so screen readers cannot say where they go.

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

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

Your title is 83 characters, so Google will cut it off around 60: “Organic Cold-Pressed Juice, Immunity Shots & Cleanses—Ships Overnight – Raw Juicery”.

The homepage links to 50 pages on rawjuicery.com and 14 external pages.

https://rawjuicery.com/pages/ingredients and https://rawjuicery.com/pages/refund-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://rawjuicery.com/pages/cleanses and https://rawjuicery.com/pages/cleanses/%22 all use the title “Organic Juice Cleanses | Raw & Cold-Pressed. Never Cooked or Frozen. …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rawjuicery.com/collections/kits and https://rawjuicery.com/pages/ingredients have no meta description, so Google writes the search snippet from whatever text it finds.

https://rawjuicery.com/pages/cleanses and https://rawjuicery.com/pages/cleanses/%22 use the same meta description. A description written for each page earns more clicks.

https://rawjuicery.com/pages/subscriber-benefits and https://rawjuicery.com/pages/affiliate have no <h1> headline, so visitors and search engines get no clear main topic.

https://rawjuicery.com/pages/affiliate, https://rawjuicery.com/pages/support and https://rawjuicery.com/pages/cleanses/%22 took over 3 s to send their HTML from our server.

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

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

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

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.

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel, Microsoft Ads and Pinterest Tag and 2 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 33 cookies, 5 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.