Website review, no card needed

littleleaffarms.com logo

littleleaffarms.com website review

Visit site (opens in a new tab)Reviewed 21 October 202645 issues · 97 checks

This review found 45 issues worth fixing on littleleaffarms.com, 20 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. 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.6 s1.5 sMay 23Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.5 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20262.0 s
Aug 29, 20262.2 s
Sep 5, 20262.9 s
Sep 12, 20263.3 s
Sep 19, 20263.1 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
190 ms76 msMay 30Oct 17154 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202689 ms
Jun 6, 202691 ms
Jun 13, 202693 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202699 ms
Jul 18, 2026121 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026130 ms
Aug 15, 2026132 ms
Aug 22, 2026143 ms
Aug 29, 2026150 ms
Sep 5, 2026165 ms
Sep 12, 2026177 ms
Sep 19, 2026162 ms
Sep 26, 2026164 ms
Oct 3, 2026161 ms
Oct 10, 2026162 ms
Oct 17, 2026154 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 littleleaffarms.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. littleleaffarms.com at 2.0 s2.0 s
  2. littleleaffarms.com at 3.9 s3.9 s
  3. littleleaffarms.com at 5.9 s5.9 s
  4. littleleaffarms.com at 7.9 s7.9 s
  5. littleleaffarms.com at 9.8 s9.8 s
  6. littleleaffarms.com at 11.8 s11.8 s
  7. littleleaffarms.com at 13.8 s13.8 s
  8. littleleaffarms.com at 15.8 s15.8 s

Speed

14 to fix20
  • Reduce unused JavaScript

    7.8 s · 2.5 MB

    About 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.

  • Improve image delivery

    4.4 s · 2.4 MB

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

  • Use efficient cache lifetimes

    3.5 s · 713 KiB

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

  • Render-blocking requests

    3.9 s

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

  • Reduce unused CSS

    2.3 s · 494 KiB

    About 494 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • YouTube adds 1.6 s

    1.6 s

    YouTube costs a phone 1.6 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 1.6 s

    1.6 s

    Google Tag Manager costs a phone 1.6 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 15.7 s

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

  • Mobile performance score: 20

    20/100

    Your mobile performance score is 20 (desktop: 25). 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 (YouTube, Google Tag Manager and lets.shop and others), adding 5.3 MB and 5.9 s of main-thread time.

  • lets.shop adds 981 ms

    981 ms

    lets.shop costs a phone 981 ms of main-thread work and 368 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.

  • Google CDN adds 623 ms

    623 ms

    Google CDN costs a phone 623 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 431 ms

    431 ms

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    29 KiB

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

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

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

    27 ms

    Your server sent the HTML in 27 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.

  • First Contentful Paint: 11.7 s

    11.7 s

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

  • Largest Contentful Paint: 41.4 s

    41.4 s

    Your largest element takes 41.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TRY THE LETTUCE THAT SPEAKS FOR ITSELF”.

  • Speed Index: 28.3 s

    28.3 s

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

  • Time to Interactive: 56.0 s

    56.0 s

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

  • Total Blocking Time: 3.9 s

    3.9 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user CLS: 0.15

    0.15

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

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

    +76%

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

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

    +36%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.143

    0.143

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

  • 6 images without width and height

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

2 checks passed
  • Real-user INP: 127 ms

    127 ms

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

  • Real-user TTFB: 755 ms

    755 ms

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

Images and page weight

5 to fix38
  • Page weight: 12.0 MB in 259 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 259 requests on a phone: scripts 5.4 MB (92), images 4.8 MB (31) and stylesheets 654 KiB (37). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

  • 6 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    SBVB3HJL-scaled-2-480x662.webp 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

    63 KiB

    2 images are downloaded at several times the size a phone draws them, for example LLF-Romaine-1x1-Caesar-Salad.png at 1,080 px wide, shown at 349 px. Resized copies would save about 63 KiB.

  • About 3.4 g of CO₂ per visit

    3.39 g

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

6 to fixGoogle 9292
  • 31 text elements with low contrast

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

  • 3 tap targets too small

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

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

    All page content should be contained by landmarks: 25 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), 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).

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 64 internal links, 27 external

    The homepage links to 64 pages on littleleaffarms.com and 27 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “At Little Leaf Farms, we grow the freshest, cleanest, best-tasting baby greens in the US. Greenhouse grown, pesticide-f…”.

  • One H1 headline

    Your main headline reads: “Try the lettuce that speaks for itself”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Little Leaf Farms - Welcome to Greater Greens”.

  • Canonical URL set

    The canonical URL is https://littleleaffarms.com/.

  • Structured data in place

    Structured data found: FoodEstablishment and SiteNavigationElement.

  • 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://littleleaffarms.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

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

Other pages

100
  • 1 page slow to respond

    https://littleleaffarms.com/product/sweet-crispy took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 7 small tap targets

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

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

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

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 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

2 to fix85
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 238 words

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

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “TRY THE LETTUCE THAT SPEAKS FOR ITSELF”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “JOIN OUR TEAM”, “WHERE TO BUY” and “CONTACT US”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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
  • 6 trackers load before any consent

    6

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 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 littleleaffarms.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

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 littleleaffarms.com, including 27 speed issues, 1 SEO issue 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