Website review, no card needed

99counties.com logo

99counties.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 78 checks

This review found 32 issues worth fixing on 99counties.com, 12 of them high impact, across 78 checks. The most urgent: improve image delivery. 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.2 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 18, 20261.8 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.2 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
203 ms126 msMay 2Sep 26162 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026154 ms
May 9, 2026147 ms
May 16, 2026138 ms
May 23, 2026135 ms
May 30, 2026145 ms
Jun 6, 2026156 ms
Jun 13, 2026185 ms
Jun 20, 2026189 ms
Jun 27, 2026179 ms
Jul 4, 2026163 ms
Aug 29, 2026179 ms
Sep 5, 2026194 ms
Sep 12, 2026161 ms
Sep 19, 2026162 ms
Sep 26, 2026162 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 99counties.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 99counties.com at 3.1 s3.1 s
  2. 99counties.com at 6.2 s6.2 s
  3. 99counties.com at 9.3 s9.3 s
  4. 99counties.com at 12.4 s12.4 s
  5. 99counties.com at 15.5 s15.5 s
  6. 99counties.com at 18.6 s18.6 s
  7. 99counties.com at 21.7 s21.7 s
  8. 99counties.com at 24.8 s24.8 s

Speed

12 to fix49
  • Improve image delivery

    1.9 s · 1.8 MB

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

  • Reduce unused JavaScript

    2.9 s · 622 KiB

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

  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    1.6 s · 480 KiB

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

  • Mobile performance score: 49

    49/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 2.2 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    300 ms · 158 KiB

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

  • Main-thread work: 3.4 s

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

  • Google Tag Manager adds 271 ms

    271 ms

    Google Tag Manager costs a phone 271 ms of main-thread work and 503 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 147 ms

    147 ms

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

  • rise-ai.com adds 111 ms

    111 ms

    rise-ai.com costs a phone 111 ms of main-thread work and 376 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.

  • cloudfront.net adds 46 ms

    46 ms

    cloudfront.net costs a phone 46 ms of main-thread work and 511 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.

  • 9 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    63 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 20 ms

    20 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 26.5 s

    26.5 s

    Your largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “99 COUNTIES 100% GRASS FED & GRASS-FINISHED | ETHICALLY RAI…”.

  • Speed Index: 24.8 s

    24.8 s

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

  • Time to Interactive: 27.6 s

    27.6 s

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

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Total Blocking Time: 289 ms

    289 ms

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

6 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.5 s

    1.5 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 574 ms

    574 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 11.6 MB in 362 requests

    11.6 MB

    Your homepage downloads 11.6 MB in 362 requests on a phone: other files 6.0 MB (183), images 2.4 MB (22) and scripts 2.3 MB (125). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (109 KiB) is 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.

  • About 3.3 g of CO₂ per visit

    3.30 g

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

2 checks passed
  • 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

5 to fixGoogle 8592
  • 2 buttons without a name

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

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

  • All page content should be contained by landmarks (10 elements)

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

  • 16 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

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

  • Meta description is long (184 characters)

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 94 internal links, 4 external

    The homepage links to 94 pages on 99counties.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “99 Counties”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Regenerative Beef, Pork, & Poultry”.

  • Canonical URL set

    The canonical URL is https://99counties.com/.

  • 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://99counties.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://99counties.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 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.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 380 words of copy

    The homepage carries about 380 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET STARTED”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Get Started”, “Contact Us” and “Member Shop”.

  • 8 short forms

    8 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar, Segment and TikTok Pixel.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 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.

  • 22 cookies set on arrival

    22

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

  • No consent tool detected

    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.

  • 51 other companies contacted

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

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 99counties.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar | Segment

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on 99counties.com, including 18 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