Website review, no card needed

growers.ag logo

growers.ag website review

Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 78 checks

This review found 31 issues worth fixing on growers.ag, 9 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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 growers.ag (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. growers.ag at 0.9 s0.9 s
  2. growers.ag at 1.9 s1.9 s
  3. growers.ag at 2.9 s2.9 s
  4. growers.ag at 3.8 s3.8 s
  5. growers.ag at 4.8 s4.8 s
  6. growers.ag at 5.7 s5.7 s
  7. growers.ag at 6.7 s6.7 s
  8. growers.ag at 7.6 s7.6 s

Speed

10 to fix53
  • Render-blocking requests

    1.9 s

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

  • Main-thread work: 4.9 s

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

  • 8 third-party services on the page

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

  • Mobile performance score: 53

    53/100

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

  • Reduce unused JavaScript

    801 KiB

    About 801 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 703 ms

    703 ms

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

  • Use efficient cache lifetimes

    466 KiB

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

  • Reduce unused CSS

    300 ms · 47 KiB

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

  • Facebook adds 279 ms

    279 ms

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

  • Improve image delivery

    292 KiB

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

  • 18 long tasks on the main thread

    18 long tasks block the main thread while loading, the longest for 188 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

    76 KiB

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

  • Minify JavaScript

    32 KiB

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

1 checks passed
  • Server response: 39 ms

    39 ms

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

Core Web Vitals

6 to fix57
  • Time to Interactive: 19.2 s

    19.2 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking "Accept" you agree to the storing of cookies on…”. Most of its time is element render delay (3.3 s).

  • Total Blocking Time: 737 ms

    737 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 12 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix78
  • Page weight: 3.0 MB in 176 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 176 requests on a phone: scripts 2.0 MB (56), images 605 KiB (53) and fonts 224 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

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

  • 8 images in older formats

    8 images (453 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.

  • About 0.9 g of CO₂ per visit

    0.86 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 102.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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8389
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 21 images without alt text

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • 3 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

Google 92100
  • 36 internal links, 14 external

    The homepage links to 36 pages on growers.ag and 14 external pages.

8 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “We're simplifying business and building loyalty across the agriculture ecosystem with effortless transactions and inter…”.

  • One H1 headline

    Your main headline reads: “You Can’t Make More Farmers. But You Can Make Them More Loyal.”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “GROWERS | Uniting Agriculture for Easier and Better Business”.

  • Canonical URL set

    The canonical URL is https://growers.ag/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://growers.ag/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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://growers.ag/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.

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://growers.ag/guide has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://growers.ag/contact, https://growers.ag/guide-solutions and https://growers.ag/sustainability have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://growers.ag/contact 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.

  • 4 pages slow to respond

    https://growers.ag/guide, https://growers.ag/blog, https://growers.ag/sustainability and https://growers.ag/privacy-policy took over 3 s to send their HTML from our server.

  • 9 internal pages checked

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

5 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 743 words of copy

    The homepage carries about 743 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, HubSpot and LinkedIn Insight.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 28 cookies set on arrival

    28

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

  • 39 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 growers.ag, 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 | Google Tag Manager
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on growers.ag, including 16 speed issues and 1 conversion gap. 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