Website review, no card needed

waldochfarm.com logo

waldochfarm.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 83 checks

This review found 33 issues worth fixing on waldochfarm.com, 8 of them high impact, across 83 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
4.6 s842 msMay 23Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.1 s
May 30, 20263.7 s
Jun 6, 20264.2 s
Jun 13, 20262.9 s
Jun 20, 20262.0 s
Jun 27, 20261.6 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
124 ms69 msMay 23Nov 780 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202695 ms
May 30, 2026105 ms
Jun 6, 2026118 ms
Jun 13, 202696 ms
Jun 20, 202686 ms
Jun 27, 202680 ms
Jul 4, 202678 ms
Jul 11, 202678 ms
Jul 18, 202677 ms
Jul 25, 202675 ms
Aug 1, 202678 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202680 ms
Oct 17, 202680 ms
Oct 24, 202680 ms
Oct 31, 202680 ms
Nov 7, 202680 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 waldochfarm.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. waldochfarm.com at 0.4 s0.4 s
  2. waldochfarm.com at 0.8 s0.8 s
  3. waldochfarm.com at 1.1 s1.1 s
  4. waldochfarm.com at 1.5 s1.5 s
  5. waldochfarm.com at 1.9 s1.9 s
  6. waldochfarm.com at 2.3 s2.3 s
  7. waldochfarm.com at 2.6 s2.6 s
  8. waldochfarm.com at 3.0 s3.0 s

Speed

9 to fix58
  • Reduce unused JavaScript

    2.1 s · 473 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 58

    58/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and omnisnippet1.com and others), adding 3.3 MB and 420 ms of main-thread time.

  • Improve image delivery

    100 ms · 412 KiB

    9 images could be 412 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 54 KiB

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

  • Shopify adds 41 ms

    41 ms

    Shopify costs a phone 41 ms of main-thread work and 2.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.

  • Google Tag Manager adds 224 ms

    224 ms

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

  • 1,756 HTML elements

    The page has 1,756 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 3 long tasks on the main thread

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    101 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A GROWING Experience Since 1916”.

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Cumulative Layout Shift: 0.204

    0.204

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

  • 14 images without width and height

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

10 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: 2.1 s

    2.1 s

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

  • Real-user INP: 71 ms

    71 ms

    Real visitors wait 71 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.1 s

    1.1 s

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

  • Real-user TTFB: 713 ms

    713 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

  • Largest content (LCP) got 62% faster for real visitors

    -62%

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

  • Total Blocking Time: 158 ms

    158 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix53
  • Page weight: 4.5 MB in 163 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 163 requests on a phone: images 2.4 MB (22), scripts 1.0 MB (44) and other files 659 KiB (80). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    287 KiB

    3 images are downloaded at several times the size a phone draws them, for example joyeradventurefarm2025logofinalol_hZfo.jpg at 1,920 px wide, shown at 150 px. Resized copies would save about 287 KiB.

  • 7 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.3 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 8694
  • 9 text elements with low contrast

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

  • 11 images without alt text

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

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

3 to fixGoogle 9284
  • Title is short (19 characters)

    Your title is only 19 characters: “Home | Waldoch Farm”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (204 characters)

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

  • 76 internal links, 6 external

    The homepage links to 76 pages on waldochfarm.com and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Waldoch Farm”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix88
  • 2 pages without a meta description

    https://waldochfarm.com/collections/all-tickets and https://waldochfarm.com/pages/garden-center-annuals have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://waldochfarm.com/pages/garden-center-hours-and-calendar-2 and https://waldochfarm.com/pages/adventure-farm-barnyard-and-attractions use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://waldochfarm.com/pages/garden-center-main has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: HUB.embedScript is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

    The homepage carries about 363 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Joyer Adventure Farm ticket here!”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Buy Joyer Adventure Farm ticket here!”, “Pricing & Tickets” and “Contact”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 12 cookies set on arrival

    12

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 waldochfarm.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Form Builder · Layouthub Pagebuilder · omnisnippet1.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 33 issues on waldochfarm.com, including 14 speed issues, 3 SEO 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