Website review, no card needed

whitingfarms.com logo

whitingfarms.com website review

Visit site (opens in a new tab)Reviewed 8 November 202623 issues · 69 checks

This review found 23 issues worth fixing on whitingfarms.com, 6 of them high impact, across 69 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.1 s794 msMay 16Oct 31851 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026853 ms
May 23, 2026851 ms
May 30, 2026825 ms
Jun 6, 2026862 ms
Jun 13, 2026890 ms
Jun 20, 2026897 ms
Jun 27, 2026899 ms
Jul 4, 2026877 ms
Jul 11, 2026868 ms
Jul 18, 2026897 ms
Jul 25, 2026892 ms
Aug 1, 2026911 ms
Aug 8, 2026964 ms
Aug 15, 2026955 ms
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 2026961 ms
Oct 3, 2026947 ms
Oct 10, 2026902 ms
Oct 17, 2026875 ms
Oct 24, 2026873 ms
Oct 31, 2026851 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms63 msMay 16Oct 3169 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202665 ms
May 23, 202667 ms
May 30, 202665 ms
Jun 6, 202675 ms
Jun 13, 202678 ms
Jun 20, 202677 ms
Jun 27, 202679 ms
Jul 4, 202674 ms
Jul 11, 202671 ms
Jul 18, 202676 ms
Jul 25, 202673 ms
Aug 1, 202676 ms
Aug 8, 202677 ms
Aug 15, 202671 ms
Aug 22, 202674 ms
Aug 29, 202674 ms
Sep 5, 202673 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202675 ms
Oct 17, 202671 ms
Oct 24, 202666 ms
Oct 31, 202669 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 whitingfarms.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. whitingfarms.com at 0.4 s0.4 s
  2. whitingfarms.com at 0.8 s0.8 s
  3. whitingfarms.com at 1.1 s1.1 s
  4. whitingfarms.com at 1.5 s1.5 s
  5. whitingfarms.com at 1.9 s1.9 s
  6. whitingfarms.com at 2.3 s2.3 s
  7. whitingfarms.com at 2.6 s2.6 s
  8. whitingfarms.com at 3.0 s3.0 s

Speed

3 to fix78
  • Improve image delivery

    1.4 s · 453 KiB

    5 images could be 453 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 78

    78/100

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused CSS

    150 ms · 35 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 69 KiB and 24 ms of main-thread time.

  • Use efficient cache lifetimes

    5 KiB

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

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 246 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 65 ms to 69 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-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 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.7 s

    1.7 s

    Real visitors wait 1.7 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.0 s

    1.0 s

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

  • Speed Index: 2.4 s

    2.4 s

    Visually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 219 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 219 requests on a phone: images 922 KiB (16), other files 732 KiB (84) and scripts 362 KiB (112). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.2 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

4 to fixGoogle 9194
  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

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

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “Whiting Farms”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Whiting Farms” and “HACKLE THAT ELEVATES EVERY FLY”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 31 internal links, 1 external

    The homepage links to 31 pages on whitingfarms.com and 1 external page.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.whitingfarms.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://www.whitingfarms.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 (269 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix85
  • 9 pages without a meta description

    https://www.whitingfarms.com/collections/all, https://www.whitingfarms.com/collections/soft-hackle, https://www.whitingfarms.com/collections/dry-fly-hackle, https://www.whitingfarms.com/collections/packs-and-other-feathers, https://www.whitingfarms.com/collections/misc-feathers and https://www.whitingfarms.com/collections and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.whitingfarms.com/collections/soft-hackle/products/hen-saddle, whose canonical is https://www.whitingfarms.com/products/hen-saddle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.whitingfarms.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.whitingfarms.com/collections and https://www.whitingfarms.com/pages/contact have 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    21 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No call to action on the first screen

    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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 194 words

    The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop Catalog”, “Quick shop” and “Shop now”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 1 trust badge.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on whitingfarms.com, including 5 speed issues, 5 SEO issues and 4 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