Website review, no card needed

neutralfarming.earth logo

neutralfarming.earth website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 75 checks

This review found 34 issues worth fixing on neutralfarming.earth, 9 of them high impact, across 75 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

Full-page screenshot of neutralfarming.earth (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. neutralfarming.earth at 0.6 s0.6 s
  2. neutralfarming.earth at 1.1 s1.1 s
  3. neutralfarming.earth at 1.7 s1.7 s
  4. neutralfarming.earth at 2.3 s2.3 s
  5. neutralfarming.earth at 2.9 s2.9 s
  6. neutralfarming.earth at 3.4 s3.4 s
  7. neutralfarming.earth at 4.0 s4.0 s
  8. neutralfarming.earth at 4.6 s4.6 s

Speed

8 to fix66
  • Improve image delivery

    4.7 s · 854 KiB

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

  • Reduce unused JavaScript

    1.2 s · 207 KiB

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

  • Render-blocking requests

    1.2 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and WordPress and others), adding 8.7 MB and 350 ms of main-thread time.

  • Mobile performance score: 66

    66/100

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

  • WordPress adds 98 ms

    98 ms

    WordPress costs a phone 98 ms of main-thread work and 8.3 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.

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • Use efficient cache lifetimes

    300 ms · 31 KiB

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

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 29 ms

    29 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 29.0 s

    29.0 s

    Your largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gemelos digitales para decidir a tiempo medir impacto produ…”.

  • Time to Interactive: 29.0 s

    29.0 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 5.4 s

    5.4 s

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 20 ms

    20 ms

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

Images and page weight

4 to fix38
  • Page weight: 12.7 MB in 97 requests

    12.7 MB

    Your homepage downloads 12.7 MB in 97 requests on a phone: media 6.5 MB (2), images 5.3 MB (20) and scripts 602 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 4.8 MB together. On a phone connection a single image that size takes seconds.

  • 4 images below the first screen load straight away

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

  • 2 images far larger than shown

    401 KiB

    2 images are downloaded at several times the size a phone draws them, for example cc97d4_3a69bc5a2d244a27a6cf8e8ccd18d2cf~mv2.png at 902 px wide, shown at 213 px. Resized copies would save about 401 KiB.

  • About 3.6 g of CO₂ per visit

    3.60 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 8994
  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 2 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is long (195 characters)

    Your title is 195 characters, so Google will cut it off around 60: “Neutral Farming: IA al servicio del agro – En Neutral Farming convertimos procesos manual…”.

  • Meta description is long (382 characters)

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

  • 6 internal links, 3 external

    The homepage links to 6 pages on neutralfarming.earth and 3 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Neutral Farming”.

  • Canonical URL set

    The canonical URL is https://neutralfarming.earth/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://neutralfarming.earth/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://neutralfarming.earth/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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://neutralfarming.earth/en all use the title “Neutral Farming: IA al servicio del agro – En Neutral Farming convert…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://neutralfarming.earth/privacy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://neutralfarming.earth/quienes-somos and https://neutralfarming.earth/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 internal pages checked

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

4 checks passed
  • Linked pages load

    All 3 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 13 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • Only about 185 words

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

  • No form on the homepage

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

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Agendar Demo”.

  • 1 call to action

    The homepage has 1 call to action, for example “Agendar Demo”.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 2 of them by other companies (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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 neutralfarming.earth, 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
Analytics
Google Analytics
Hosting
WordPress.com

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on neutralfarming.earth, including 13 speed issues, 2 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