Website review, no card needed

farmland.org logo

farmland.org website review

Visit site (opens in a new tab)Reviewed 28 October 202642 issues · 81 checks

This review found 42 issues worth fixing on farmland.org, 10 of them high impact, across 81 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
4.6 s1.8 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.3 s
May 23, 20262.5 s
May 30, 20262.9 s
Jun 6, 20263.8 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20263.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.4 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.5 s
Sep 5, 20262.7 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20262.6 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
244 ms131 msMay 9Oct 24231 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026144 ms
May 16, 2026151 ms
May 23, 2026158 ms
May 30, 2026170 ms
Jun 6, 2026198 ms
Jun 13, 2026204 ms
Jun 20, 2026211 ms
Jun 27, 2026212 ms
Jul 4, 2026194 ms
Jul 11, 2026172 ms
Jul 18, 2026171 ms
Jul 25, 2026167 ms
Aug 1, 2026164 ms
Aug 8, 2026170 ms
Aug 15, 2026166 ms
Aug 22, 2026163 ms
Aug 29, 2026167 ms
Sep 5, 2026162 ms
Sep 12, 2026161 ms
Sep 19, 2026171 ms
Sep 26, 2026189 ms
Oct 3, 2026206 ms
Oct 10, 2026207 ms
Oct 17, 2026222 ms
Oct 24, 2026231 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 farmland.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix32
  • Use efficient cache lifetimes

    4.8 s · 1.2 MB

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

  • Reduce unused JavaScript

    3.9 s · 763 KiB

    About 763 KiB 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.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32 (desktop: 61). 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, Facebook and feathr.co and others), adding 1.7 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 993 ms

    993 ms

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

  • Improve image delivery

    681 KiB

    8 images could be 681 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Facebook adds 407 ms

    407 ms

    Facebook costs a phone 407 ms of main-thread work and 395 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.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Main-thread work: 2.5 s

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

  • Reduce unused CSS

    270 ms · 27 KiB

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

  • Legacy JavaScript

    200 ms · 61 KiB

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

  • 15 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 61 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

13 to fix33
  • 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: 22.0 s

    22.0 s

    Your largest element takes 22.0 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: 22.5 s

    22.5 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Total Blocking Time: 845 ms

    845 ms

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 240 ms

    240 ms

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

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

    +54%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.176

    0.176

    The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

1 checks passed
  • Real-user CLS: 0.01

    0.01

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

Images and page weight

3 to fix74
  • Page weight: 4.0 MB in 103 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 103 requests on a phone: scripts 1.8 MB (28), images 1.7 MB (29) and fonts 340 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    no-farms-no-food-bumper-sticker.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    214 KiB

    2 images are downloaded at several times the size a phone draws them, for example CharityNavigator.png at 1,280 px wide, shown at 72 px. Resized copies would save about 214 KiB.

  • 2 images in older formats

    2 images (224 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.

  • 1 image below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.13 g

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

Accessibility

5 to fixGoogle 9293
  • 21 tap targets too small

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

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

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

  • 3 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 9278
  • Title is short (23 characters)

    Your title is only 23 characters: “American Farmland Trust”. 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.

  • Meta description is short (33 characters)

    Your meta description is only 33 characters: “Saving the land that sustains us!”. 70 to 160 characters is enough to sell the click.

  • No XML sitemap

    No XML sitemap at https://farmland.org/sitemap.xml, so Google discovers your pages only by following links.

  • 4 links with vague text

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

  • 59 internal links, 18 external

    The homepage links to 59 pages on farmland.org and 18 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Become a member and protect the land that we depend on”.

  • Canonical URL set

    The canonical URL is https://farmland.org/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

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.

  • No llms.txt

    There is no https://farmland.org/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 1 crawler

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

2 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 (487 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 14 pages without a meta description

    https://farmland.org/about, https://farmland.org/our-work, https://farmland.org/where-we-work, https://farmland.org/impact, https://farmland.org/get-involved and https://farmland.org/give and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://farmland.org/women, whose canonical is https://farmland.org/women-for-the-land. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://farmland.org/news and https://farmland.org/brighterfuture have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 3 trust badges. 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 477 words of copy

    The homepage carries about 477 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: “JOIN NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “JOIN NOW”, “LEARN MORE” and “Learn More”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 10 cookies set on arrival

    10

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

  • 29 other companies contacted

    Loading the homepage contacts 29 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 farmland.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
228

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on farmland.org, including 22 speed issues, 5 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