rawrev.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and rechargecdn.com and others), adding 2.2 MB and 592 ms of main-thread time.

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

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.

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

Klaviyo costs a phone 177 ms of main-thread work and 619 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 1,621 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rechargecdn.com costs a phone 57 ms of main-thread work and 298 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.

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

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

13 KiB could be saved by minifying CSS.

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

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

Your largest element takes 18.7 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 18.9 s. Good is under 3.8 s.

Visually, the page fills in at 11.6 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.

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

Your homepage downloads 5.0 MB in 554 requests on a phone: scripts 1.9 MB (254), other files 1.2 MB (216) and images 1.2 MB (35). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example site-hero_pb-darkchoc-sea-salt_pb-sea-salt_2026-07-22.png at 1,209 px wide, shown at 390 px. Resized copies would save about 6 KiB.

1 image (207 KiB) is 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 43 pages on rawrev.com and 19 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://rawrev.com/pages/meet-alice and https://rawrev.com/pages/our-story all use the title “Meet Alice Benedetto, RN — Founder of Raw Rev | Vegan Protein Bars”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://rawrev.com/collections/new-raw-rev-stevia-free-protein-bars/products/chocolate-chip-cookie-dough-glo-2-0-vegan-protein-bars, whose canonical is https://rawrev.com/products/chocolate-chip-cookie-dough-glo-2-0-vegan-protein-bars. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://rawrev.com/pages/our-story has no <h1> headline, so visitors and search engines get no clear main topic.

https://rawrev.com/pages/meet-alice, https://rawrev.com/blogs/news, https://rawrev.com/collections/all and https://rawrev.com/pages/our-story took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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

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

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