Website review, no card needed

gullmeadowfarms.com logo

gullmeadowfarms.com website review

Visit site (opens in a new tab)Reviewed 10 November 202623 issues · 80 checks

This review found 23 issues worth fixing on gullmeadowfarms.com, 5 of them high impact, across 80 checks. The most urgent: 1 button without a name. 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
1.2 s838 msMay 23Nov 7961 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 2026980 ms
Jul 18, 2026968 ms
Jul 25, 2026886 ms
Aug 1, 2026874 ms
Aug 8, 2026884 ms
Aug 15, 2026915 ms
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 2026988 ms
Sep 26, 2026957 ms
Oct 3, 2026959 ms
Oct 10, 2026944 ms
Oct 17, 2026940 ms
Oct 24, 2026943 ms
Oct 31, 2026955 ms
Nov 7, 2026961 ms
Real-visitor tap response (INP)75th percentile, phones
113 ms67 msJun 27Nov 7107 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 202676 ms
Jul 4, 202675 ms
Jul 11, 202672 ms
Jul 18, 202683 ms
Jul 25, 202682 ms
Aug 1, 202682 ms
Aug 8, 202686 ms
Aug 15, 202686 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202690 ms
Sep 12, 202694 ms
Sep 19, 202696 ms
Sep 26, 2026103 ms
Oct 3, 2026104 ms
Oct 10, 2026105 ms
Oct 17, 2026105 ms
Oct 24, 2026105 ms
Oct 31, 2026108 ms
Nov 7, 2026107 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 gullmeadowfarms.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gullmeadowfarms.com at 0.6 s0.6 s
  2. gullmeadowfarms.com at 1.2 s1.2 s
  3. gullmeadowfarms.com at 1.8 s1.8 s
  4. gullmeadowfarms.com at 2.4 s2.4 s
  5. gullmeadowfarms.com at 3.0 s3.0 s
  6. gullmeadowfarms.com at 3.5 s3.5 s
  7. gullmeadowfarms.com at 4.1 s4.1 s
  8. gullmeadowfarms.com at 4.7 s4.7 s

Speed

2 to fix93
  • Improve image delivery

    956 KiB

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

  • Render-blocking requests

    300 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Use efficient cache lifetimes

    163 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Mailchimp, Shopify and elfsight.com and others), adding 289 KiB and 112 ms of main-thread time.

  • Reduce unused JavaScript

    85 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

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

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Speed Index: 6.2 s

    6.2 s

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

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

    +42%

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

  • Time to Interactive: 6.8 s

    6.8 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 99 ms

    99 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 772 ms

    772 ms

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

  • Largest Contentful Paint: 1.9 s

    1.9 s

    Your largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Nestled in Richland, MI, just outside Kalamazoo, our farm i…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 2 ms

    2 ms

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    christmas-at-the-farm-gull-meadow-farm_800x800.webp weighs 974 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.2 MB in 149 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 149 requests on a phone: images 1.0 MB (13), other files 673 KiB (65) and scripts 397 KiB (55). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (1.2 MB) 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.

  • 5 images far larger than shown

    422 KiB

    5 images are downloaded at several times the size a phone draws them, for example walk_through_the_lights-at-night_800x800.png at 800 px wide, shown at 151 px. Resized copies would save about 422 KiB.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

Accessibility

7 to fixGoogle 8291
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 8 text elements with low contrast

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

  • 2 images without alt text

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

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

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

  • 29 links without text

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

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
  • 66 internal links, 7 external

    The homepage links to 66 pages on gullmeadowfarms.com and 7 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Experience fun for the whole family at Gull Meadow Farms in Kalamazoo, MI, with over 30 activities, u-pick apples & pum…”.

  • One H1 headline

    Your main headline reads: “The place to be for holiday traditions family memories date night”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Gull Meadow Farms | Richland, MI”.

  • Canonical URL set

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

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

  • XML sitemap found

    Your XML sitemap is reachable at https://gullmeadowfarms.com/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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://gullmeadowfarms.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 4 pages without a meta description

    https://gullmeadowfarms.com/collections/fall-admission, https://gullmeadowfarms.com/pages/employment, https://gullmeadowfarms.com/pages/faqs and https://gullmeadowfarms.com/pages/lost-and-found have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 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.

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 447 words of copy

    The homepage carries about 447 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 5 calls to action

    The homepage has 5 calls to action, for example “Pricing”, “Buy Tickets” and “Subscribe”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 14 cookies set on arrival

    14

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

  • 21 other companies contacted

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

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Warnify Pro Warnings · Product Warnings · Mailchimp · itoris.com · elfsight.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on gullmeadowfarms.com, including 6 speed 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