Website review, no card needed

farmersnational.com logo

farmersnational.com website review

Visit site (opens in a new tab)Reviewed 2 November 202645 issues · 89 checks

This review found 45 issues worth fixing on farmersnational.com, 17 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
3.5 s3.0 sMay 16Oct 313.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.3 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Oct 31, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
154 ms89 msMay 16Oct 31145 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202697 ms
May 30, 202696 ms
Jun 6, 2026102 ms
Jun 13, 2026105 ms
Jun 20, 2026107 ms
Jun 27, 2026111 ms
Jul 4, 2026106 ms
Jul 11, 2026103 ms
Jul 18, 202699 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202697 ms
Aug 22, 202698 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026114 ms
Sep 26, 2026123 ms
Oct 3, 2026135 ms
Oct 10, 2026146 ms
Oct 17, 2026146 ms
Oct 24, 2026146 ms
Oct 31, 2026145 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 farmersnational.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix30
  • Use efficient cache lifetimes

    10.8 s · 36.1 MB

    59 files are served with short cache lifetimes, so returning visitors download them again (36.1 MB).

  • Improve image delivery

    9.3 s · 25.0 MB

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

  • Reduce unused JavaScript

    2.1 s · 572 KiB

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 6.8 s

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

  • 4,204 HTML elements

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

  • Render-blocking requests

    700 ms

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

  • 8 third-party services on the page

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

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 223 ms

    223 ms

    Google Tag Manager costs a phone 223 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.

  • Unpkg adds 116 ms

    116 ms

    Unpkg costs a phone 116 ms of main-thread work and 333 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.

  • Reduce unused CSS

    140 ms · 47 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • 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: 34 ms

    34 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 44.5 s

    44.5 s

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

  • Time to Interactive: 45.0 s

    45.0 s

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

  • Speed Index: 10.8 s

    10.8 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Real-user INP: 216 ms

    216 ms

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

  • Tap response (INP) got 50% slower for real visitors

    +50%

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 600 ms

    600 ms

    Real visitors wait 600 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

5 to fix18
  • Page weight: 43.8 MB in 147 requests

    43.8 MB

    Your homepage downloads 43.8 MB in 147 requests on a phone: images 29.4 MB (49), other files 6.5 MB (64) and media 6.4 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 28 images over 500 KB

    28 images weigh 23.0 MB together. On a phone connection a single image that size takes seconds.

  • 34 images far larger than shown

    22.5 MB

    34 images are downloaded at several times the size a phone draws them, for example Untitled-1778-x-2317-px-3.png at 1,778 px wide, shown at 358 px. Resized copies would save about 22.5 MB.

  • 39 images in older formats

    39 images (25.3 MB) 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.

  • 38 images below the first screen load straight away

    38 images further down the page (25.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 12.4 g of CO₂ per visit

    12.42 g

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

Accessibility

5 to fix85
  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • 403 tap targets too small

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

  • 11 links without text

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

  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 8591
  • Structured data has 2 problems

    Structured data found (BreadcrumbList, LocalBusiness, Organization and WebPage) but with 2 problems, for example “LocalBusiness: missing name”.

  • No social preview image

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 67 internal links, 15 external

    The homepage links to 67 pages on farmersnational.com and 15 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Maximize your asset's value with Farmers National Company. Leaders in farm management, land real estate, and comprehens…”.

  • One H1 headline

    Your main headline reads: “LEADERS IN LAND”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Farmers National Company | Leaders In Land”.

  • Canonical URL set

    The canonical URL is https://www.farmersnational.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.farmersnational.com/sitemaps-1-sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, 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.

  • No llms.txt

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

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

4 to fix83
  • 4 pages without a meta description

    https://www.farmersnational.com/news, https://www.farmersnational.com/events, https://www.farmersnational.com/executives and https://www.farmersnational.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.farmersnational.com/real-estate, https://www.farmersnational.com/appraisal, https://www.farmersnational.com/forestry and https://www.farmersnational.com/insurance use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.farmersnational.com/real-estate/properties/Farmland, whose canonical is https://www.farmersnational.com/real-estate/properties/farmland. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.farmersnational.com/real-estate has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.farmersnational.com/find-a-rep has 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 (of 36 found) 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

2 to fixGoogle 10087
  • 1,458 small tap targets

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

  • 1 JavaScript error while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 18 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 592 words of copy

    The homepage carries about 592 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: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 8 cookies set on arrival

    8

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 farmersnational.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
SEOmatic
Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Azure

Hiring

Hiring
3 open roles
Job board
adp

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on farmersnational.com, including 20 speed issues, 3 SEO issues and 3 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