nebraskabison.com website review

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

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

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

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

8 third-party services load with your homepage (route.com, amaicdn.com and Shopify and others), adding 2.1 MB and 988 ms of main-thread time.

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

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

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

Polyfills for old browsers add 87 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

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

route.com costs a phone 236 ms of main-thread work and 543 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.

amaicdn.com costs a phone 202 ms of main-thread work and 420 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 143 ms of main-thread work and 550 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.

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

6 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 315 requests on a phone: scripts 2.4 MB (135), images 1.0 MB (19) and other files 1,022 KiB (137). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Some list items are not inside a list.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

12 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 skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 81 characters, so Google will cut it off around 60: “Shop Bison Meat | Bison Burgers, Steaks & More – Buy Online Now. – Nebraska Bison”.

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

There are 4 <h1> headlines (“Left NEW PRODUCTS Right”, “Left Best Sellers Right” and “Left Shop Elk Meat Right”). One clear main headline is easier for people and search engines.

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

The homepage links to 167 pages on nebraskabison.com and 8 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.

https://www.nebraskabison.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.nebraskabison.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.nebraskabison.com/collections/full-menu, https://www.nebraskabison.com/pages/our-story, https://www.nebraskabison.com/customer_authentication/redirect, https://www.nebraskabison.com/collections/bison-meat-cuts, https://www.nebraskabison.com/collections/buffalo-bison-roasts-ribs and https://www.nebraskabison.com/collections/bison-buffalo-jerky and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nebraskabison.com/pages/buffalo-bison-meat-cooking-tips and https://www.nebraskabison.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'setting')”.

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

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

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 1,020 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, 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 17 cookies, 1 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.