shadybrookfarm.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, elfsightcdn.com and Clarity and others), adding 1.2 MB and 592 ms of main-thread time.

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

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

elfsightcdn.com costs a phone 154 ms of main-thread work and 352 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.

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

About 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

30 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “An open glittery red book lying on a wooden surface, displa…”.

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

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

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

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

Your homepage downloads 3.4 MB in 190 requests on a phone: scripts 1.3 MB (68), other files 1.1 MB (98) and images 815 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

9 elements hidden from screen readers can still receive keyboard focus.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “American Express”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 138 pages on shadybrookfarm.com and 23 external pages.

Your homepage links to https://shadybrookfarm.com/products/st-paddy-unwined-weekend-2026, https://shadybrookfarm.com/products/flower-up-wine-down and https://shadybrookfarm.com/products/garden-to-glass-cocktail-class, which answer with an error. Visitors hit a dead end and search engines drop them.

/, https://shadybrookfarm.com/pages/dashin-thru-the-lights, https://shadybrookfarm.com/pages/events-calendar, https://shadybrookfarm.com/pages/summer-unwined-concerts, https://shadybrookfarm.com/collections/breakfast-with-the-bunny and https://shadybrookfarm.com/pages/easter-eggstravaganza and 6 others all use the title “American Express”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shadybrookfarm.com/pages/dashin-thru-the-lights, https://shadybrookfarm.com/pages/events-calendar, https://shadybrookfarm.com/pages/summer-unwined-concerts, https://shadybrookfarm.com/collections/breakfast-with-the-bunny, https://shadybrookfarm.com/pages/easter-eggstravaganza and https://shadybrookfarm.com/pages/party-on-the-patio and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://shadybrookfarm.com/pages/dashin-thru-the-lights, https://shadybrookfarm.com/pages/summer-unwined-concerts, https://shadybrookfarm.com/collections/breakfast-with-the-bunny, https://shadybrookfarm.com/pages/easter-eggstravaganza, https://shadybrookfarm.com/pages/party-on-the-patio and https://shadybrookfarm.com/pages/cornhole and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'start')”.

Requests the notification permission on page load.

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 742 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 19 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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