2rowbrewing.com website review

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

2 third-party services load with your homepage (Framer CDN and framer.com), adding 1.0 MB and 507 ms of main-thread time.

Framer CDN costs a phone 507 ms of main-thread work and 1.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.

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

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

3 images could be 99 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

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

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 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Chasing Haze Beer Can”.

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

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

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

2 images are downloaded at several times the size a phone draws them, for example Tc7N5mc79CDWhFp0hUTt3bHTFOs.png at 2,160 px wide, shown at 696 px. Resized copies would save about 25 KiB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“2 row brewing taproom”, “Favorites” and “From home-brew to taproom”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 43 pages on 2rowbrewing.com and 25 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.2rowbrewing.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.2rowbrewing.com/beers, https://www.2rowbrewing.com/find-us, https://www.2rowbrewing.com/our-story, https://www.2rowbrewing.com/contact and https://www.2rowbrewing.com/feelin-hazy and 2 others all use the title “2 Row Brewing | Utah Craft Brewery”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.2rowbrewing.com/beers, https://www.2rowbrewing.com/find-us, https://www.2rowbrewing.com/our-story, https://www.2rowbrewing.com/contact, https://www.2rowbrewing.com/feelin-hazy and https://www.2rowbrewing.com/tastes-like-citrus and 1 other use the same meta description. A description written for each page earns more clicks.

https://www.2rowbrewing.com/find-us, https://www.2rowbrewing.com/feelin-hazy and https://www.2rowbrewing.com/tastes-like-citrus have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.2rowbrewing.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 7 pages linked from your homepage 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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.