russianriverbrewing.com website review

The page goes through 1 redirect before it starts loading, costing about 45.9 s. Link and advertise the final URL directly.

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

11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (YouTube, Usercentrics CMP and Accessibe Accessibility Overlay and others), adding 1.5 MB and 854 ms of main-thread time.

YouTube costs a phone 343 ms of main-thread work and 742 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.

Usercentrics CMP costs a phone 294 ms of main-thread work and 208 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 0 ms of main-thread work and 355 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.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 44.8 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

8 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-17, real Chrome visitors' tap response (inp) went from 80 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.9 MB in 342 requests on a phone: images 6.3 MB (67), scripts 4.4 MB (102) and stylesheets 645 KiB (110). Under 2 MB keeps phones on slow connections fast.

Untitled-8-768x768.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

4 buttons have no accessible name, so screen readers announce just “button”.

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid names: 3 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “Russian River Brewing Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 46 characters: “Award-Winning Beers in the California Bay Area”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 84 pages on russianriverbrewing.com and 34 external pages.

There is no https://www.russianriverbrewing.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.russianriverbrewing.com/santa-rosa-beers and https://www.russianriverbrewing.com/windsor-beers all use the title “Bottles, Cans & Draft - Russian River Brewing Company”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.russianriverbrewing.com/santa-rosa-beers, https://www.russianriverbrewing.com/windsor-beers, https://www.russianriverbrewing.com/blog and https://www.russianriverbrewing.com/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.russianriverbrewing.com/santa-rosa-pub-menu and https://www.russianriverbrewing.com/windsor-pub-menu use the same meta description. A description written for each page earns more clicks.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 583 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.