uncdairy.com website review

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

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

About 282 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

About 77 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.

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

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

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

6 third-party services load with your homepage (Accessibe Accessibility Overlay, Google Tag Manager and cdn-cookieyes.com and others), adding 633 KiB and 451 ms of main-thread time.

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

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

Polyfills for old browsers add 9 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.

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 21.3 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 21.6 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 6.0 MB in 111 requests on a phone: images 4.7 MB (31), scripts 852 KiB (35) and fonts 223 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

10 images (631 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.70 g of CO₂e: 204.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Page should contain a level-one heading: 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.

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

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

Your title is only 16 characters: “Home | UNC Dairy”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 59 pages on uncdairy.com and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://uncdairy.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://uncdairy.com/bison, https://uncdairy.com/intense-milk/b-intense-milk, https://uncdairy.com/upstate-farms-foodservice/b-upstate-farms-foodservice, https://uncdairy.com/upstate-farms/b-upstate-farms and https://uncdairy.com/bison-foods/b-bison-foods are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://uncdairy.com/bison and https://uncdairy.com/bison-foods/b-bison-foods all use the title “Bison® Foods | UNC Dairy”. Search engines can't tell which page to show for a search, so each competes with the others.

https://uncdairy.com/bison, https://uncdairy.com/intense-milk/b-intense-milk, https://uncdairy.com/upstate-farms-foodservice/b-upstate-farms-foodservice, https://uncdairy.com/upstate-farms/b-upstate-farms and https://uncdairy.com/bison-foods/b-bison-foods have no meta description, so Google writes the search snippet from whatever text it finds.

https://uncdairy.com/about-us and https://uncdairy.com/suppliers use the same meta description. A description written for each page earns more clicks.

https://uncdairy.com/about-us, https://uncdairy.com/blog, https://uncdairy.com/media, https://uncdairy.com/suppliers and https://uncdairy.com/our-brands have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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.

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

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

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

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