Website review, no card needed

farmerspick.com.au logo

farmerspick.com.au website review

Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 90 checks

This review found 43 issues worth fixing on farmerspick.com.au, 8 of them high impact, across 90 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

Real-visitor load time (LCP)75th percentile, phones
4.4 s2.6 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20263.1 s
Aug 22, 20263.6 s
Aug 29, 20263.8 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.2 s
Sep 26, 20264.2 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.1 s
Oct 24, 20264.1 s
Oct 31, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
222 ms136 msMay 16Oct 31211 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026147 ms
May 23, 2026149 ms
May 30, 2026149 ms
Jun 6, 2026150 ms
Jun 13, 2026148 ms
Jun 20, 2026146 ms
Jun 27, 2026146 ms
Jul 4, 2026146 ms
Jul 11, 2026147 ms
Jul 18, 2026146 ms
Jul 25, 2026148 ms
Aug 1, 2026154 ms
Aug 8, 2026162 ms
Aug 15, 2026178 ms
Aug 22, 2026192 ms
Aug 29, 2026198 ms
Sep 5, 2026203 ms
Sep 12, 2026204 ms
Sep 19, 2026202 ms
Sep 26, 2026203 ms
Oct 3, 2026205 ms
Oct 10, 2026208 ms
Oct 17, 2026211 ms
Oct 24, 2026212 ms
Oct 31, 2026211 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 farmerspick.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. farmerspick.com.au at 0.5 s0.5 s
  2. farmerspick.com.au at 1.1 s1.1 s
  3. farmerspick.com.au at 1.6 s1.6 s
  4. farmerspick.com.au at 2.2 s2.2 s
  5. farmerspick.com.au at 2.7 s2.7 s
  6. farmerspick.com.au at 3.2 s3.2 s
  7. farmerspick.com.au at 3.8 s3.8 s
  8. farmerspick.com.au at 4.3 s4.3 s

Speed

13 to fix66
  • Render-blocking requests

    1.8 s

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

  • Main-thread work: 5.9 s

    A phone's processor spends 5.9 s on main-thread work while loading, 3.4 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 (Shopify, Google Tag Manager and ZenDesk and others), adding 6.5 MB and 2.2 s 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.

  • Shopify adds 861 ms

    861 ms

    Shopify costs a phone 861 ms of main-thread work and 1.1 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 JavaScript

    922 KiB

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

  • Improve image delivery

    782 KiB

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

  • Vimeo adds 167 ms

    167 ms

    Vimeo costs a phone 167 ms of main-thread work and 4.1 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.

  • Google Tag Manager adds 334 ms

    334 ms

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

  • ZenDesk adds 305 ms

    305 ms

    ZenDesk costs a phone 305 ms of main-thread work and 431 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

    333 KiB

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

  • Facebook adds 275 ms

    275 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    53 KiB

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

  • Reduce unused CSS

    39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page.

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

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

  • Time to Interactive: 24.9 s

    24.9 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Total Blocking Time: 972 ms

    972 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 220 ms

    220 ms

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

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

    +43%

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

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 899 ms

    899 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Better food, fairly priced. Fruit, veg and meat delivered t…”.

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

2 to fix60
  • Page weight: 7.7 MB in 208 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 208 requests on a phone: other files 3.6 MB (48), scripts 2.2 MB (102) and images 1.1 MB (16). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    312 KiB

    3 images are downloaded at several times the size a phone draws them, for example Box_sticker_produce.webp at 1,667 px wide, shown at 272 px. Resized copies would save about 312 KiB.

  • 1 image below the first screen load straight away

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

  • About 2.2 g of CO₂ per visit

    2.17 g

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

2 to fixGoogle 9498
  • 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.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9296
  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 65 internal links, 11 external

    The homepage links to 65 pages on farmerspick.com.au and 11 external pages.

7 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Save up to 30% on fresh fruit, veg, meat and pantry staples delivered to your door. Flexible subscriptions that help re…”.

  • One H1 headline

    Your main headline reads: “Better food, fairly priced. Fruit, veg and meat delivered to your door.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Fresh Fruit, Veg & Groceries Delivered | Farmers Pick”.

  • Canonical URL set

    The canonical URL is https://farmerspick.com.au/.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • 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://farmerspick.com.au/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://farmerspick.com.au/llms.txt (195 KiB, 238 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://farmerspick.com.au/box-builder and https://farmerspick.com.au/pages/box-builder all use the title “Build Your Own Produce Box | Farmers Pick”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://farmerspick.com.au/box-builder and https://farmerspick.com.au/pages/box-builder 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://farmerspick.com.au/pages/box-builder, whose canonical is https://farmerspick.com.au/box-builder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://farmerspick.com.au/pages/how-it-works, https://farmerspick.com.au/pages/fruit-and-veg, https://farmerspick.com.au/pages/meat-seafood-dairy, https://farmerspick.com.au/pages/pantry-range, https://farmerspick.com.au/pages/about-us and https://farmerspick.com.au/pages/sourcing-commitment and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://farmerspick.com.au/box-builder and https://farmerspick.com.au/pages/box-builder 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 (of 33 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 5488
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Minified React error #421; visit https://reactjs.org/docs/error-decoder.html?invariant=421 for the full message or use …”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

  • No opening hours

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

  • No map or directions link

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

  • About 1,891 words of copy

    The homepage carries about 1,891 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop our Christmas range”, “Contact” and “Subscribe”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 3 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.

  • 36 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on farmerspick.com.au, including 24 speed issues, 2 SEO issues and 5 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