rcherbals.com website review

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

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

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

8 images could be 606 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 2.3 MB and 504 ms of main-thread time.

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

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

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

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

Klaviyo costs a phone 201 ms of main-thread work and 475 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 92 ms of main-thread work and 1.4 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.

LoyaltyLion costs a phone 60 ms of main-thread work and 359 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 73 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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.

3 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 10.4 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.0 s. Good is under 3.8 s.

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 138 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 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 images are downloaded at several times the size a phone draws them, for example Almanac2026_Cover_2Kx2K.png at 2,000 px wide, shown at 374 px. Resized copies would save about 563 KiB.

Your homepage downloads 3.7 MB in 359 requests on a phone: scripts 1.5 MB (229), images 1.3 MB (26) and other files 676 KiB (79). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (885 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images (512 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.

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

9 elements hidden from screen readers can still receive keyboard focus.

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

1 tap target is too small or too close together to hit reliably with a finger.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 18 characters: “RidgeCrest Herbals”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

The homepage links to 146 pages on rcherbals.com and 19 external pages.

https://rcherbals.com/collections/swag has 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://rcherbals.com/collections/swag, whose canonical is https://rcherbals.com/collections/merch. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://rcherbals.com/pages/almanac and https://rcherbals.com/collections/swag have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) SecurityError: Failed to read a named property 'document' from 'Window': Sandbox access violation…”.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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