Website review, no card needed

snakeriverfarms.com logo

snakeriverfarms.com website review

Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 89 checks

This review found 37 issues worth fixing on snakeriverfarms.com, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
175 ms151 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026171 ms
May 23, 2026172 ms
May 30, 2026171 ms
Jun 6, 2026169 ms
Jun 13, 2026163 ms
Jun 20, 2026162 ms
Jun 27, 2026162 ms
Jul 4, 2026163 ms
Jul 11, 2026164 ms
Jul 18, 2026164 ms
Jul 25, 2026163 ms
Aug 1, 2026162 ms
Aug 8, 2026160 ms
Aug 15, 2026161 ms
Aug 22, 2026156 ms
Aug 29, 2026155 ms
Sep 5, 2026155 ms
Sep 12, 2026155 ms
Sep 19, 2026155 ms
Sep 26, 2026158 ms
Oct 3, 2026160 ms
Oct 10, 2026156 ms
Oct 17, 2026156 ms
Oct 24, 2026154 ms
Oct 31, 2026154 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of snakeriverfarms.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. snakeriverfarms.com at 1.2 s1.2 s
  2. snakeriverfarms.com at 2.3 s2.3 s
  3. snakeriverfarms.com at 3.5 s3.5 s
  4. snakeriverfarms.com at 4.6 s4.6 s
  5. snakeriverfarms.com at 5.8 s5.8 s
  6. snakeriverfarms.com at 6.9 s6.9 s
  7. snakeriverfarms.com at 8.1 s8.1 s
  8. snakeriverfarms.com at 9.2 s9.2 s

Speed

14 to fix37
  • Reduce unused JavaScript

    3.8 s · 1.3 MB

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

  • Use efficient cache lifetimes

    2.3 s · 604 KiB

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

  • audioeye.com adds 2.3 s

    2.3 s

    audioeye.com costs a phone 2.3 s of main-thread work and 344 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 9.1 s

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

  • 3,069 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Osano CMP and others), adding 2.7 MB and 4.0 s of main-thread time.

  • Improve image delivery

    200 ms · 443 KiB

    8 images could be 443 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.

  • Google Tag Manager adds 550 ms

    550 ms

    Google Tag Manager costs a phone 550 ms of main-thread work and 685 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.

  • Render-blocking requests

    600 ms

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

  • Reduce unused CSS

    340 ms · 88 KiB

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

  • Osano CMP adds 276 ms

    276 ms

    Osano CMP costs a phone 276 ms of main-thread work and 75 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 adds 198 ms

    198 ms

    Klaviyo costs a phone 198 ms of main-thread work and 323 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.

  • Yotpo adds 184 ms

    184 ms

    Yotpo costs a phone 184 ms of main-thread work and 327 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 on the main thread

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

  • Minify JavaScript

    150 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    76 KiB

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

  • Duplicated JavaScript

    12 KiB

    12 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Largest Contentful Paint: 19.6 s

    19.6 s

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

  • Time to Interactive: 35.3 s

    35.3 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Total Blocking Time: 794 ms

    794 ms

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 146 ms

    146 ms

    Real visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 662 ms

    662 ms

    Real visitors wait 662 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 6.4 MB in 344 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 344 requests on a phone: scripts 3.3 MB (125), images 1.5 MB (31) and other files 991 KiB (148). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.81 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8790
  • Elements must only use permitted ARIA attributes (32 elements)

    Elements must only use permitted ARIA attributes: 32 elements on the page fail this check, rated serious by axe-core.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

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

  • 11 links without text

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

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (1 element).

  • ARIA role should be appropriate for the element (4 elements)

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • 3 H1 headlines

    There are 3 <h1> headlines (“Up to $50 off Holiday Hams & Roasts”, “We are ranchers, rooted in tradition, driven by p…” and “We are ranchers, rooted in tradition, driven by p…”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 213 internal links, 8 external

    The homepage links to 213 pages on snakeriverfarms.com and 8 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Explore American Wagyu, USDA Prime beef and Kurobuta pork from Snake River Farms. Find ribeye, filet mignon and other r…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Home | Snake River Farms – The Pioneers of American Wagyu Beef”.

  • Canonical URL set

    The canonical URL is https://snakeriverfarms.com/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://snakeriverfarms.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://snakeriverfarms.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,192 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://snakeriverfarms.com/collections/holiday-centerpieces is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://snakeriverfarms.com/blogs/srf-journal has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 42 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

  • No direct contact details

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

  • About 945 words of copy

    The homepage carries about 945 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All” and “SUBSCRIBE & SAVE”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop All”, “Shop Now American Wagyu Wagyu Steaks” and “Shop Now Kurobuta Pork Kurobuta Roasts”.

  • 36 short forms

    36 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at snakeriverfarms.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Rebuy Personalization Engine · Yotpo Loyalty Rewards · Elevar Conversion Tracking · Microsoft Clarity · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Applovin Shop Integration · Forms · Freegifts · bogos.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Boise

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on snakeriverfarms.com, including 19 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25