greenstalkgarden.com website review

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

20 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 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 (Olark, Shopify and Klaviyo and others), adding 1.9 MB and 795 ms of main-thread time.

About 531 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 140 ms faster on a phone.

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

Olark costs a phone 327 ms of main-thread work and 469 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 files are served with short cache lifetimes, so returning visitors download them again (260 KiB).

Shopify costs a phone 246 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.

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

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

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

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

45 KiB could be saved by minifying JavaScript.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “🌻🍂 GROW THROUGH FALL 🍂🌻 Seed Starting Essentials Get Gr…”.

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

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

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

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

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

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

Your homepage downloads 38.8 MB in 311 requests on a phone: media 33.1 MB (7), images 2.7 MB (76) and scripts 1.5 MB (97). Under 2 MB keeps phones on slow connections fast.

Dragonfly_Pop-Up1.jpg 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 are downloaded at several times the size a phone draws them, for example homepage-fennel.png at 716 px wide, shown at 100 px. Resized copies would save about 162 KiB.

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

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

Some list items are not inside a list.

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

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

All page content should be contained by landmarks: 38 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 on the page fails this check, rated moderate by axe-core.

17 visible links have no text or label, so screen readers cannot say where they go.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 27 characters: “GreenStalk Vertical Planter”. Between 30 and 65 characters leaves room to say what you do and for whom.

2 links have no real href, so search engines can't follow them.

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

The homepage links to 116 pages on greenstalkgarden.com and 9 external pages.

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.

Your homepage links to https://greenstalkgarden.com/pages/wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

https://greenstalkgarden.com/pages/online-retailers, https://greenstalkgarden.com/pages/rewards and https://greenstalkgarden.com/collections/fall-seed-starting-collection have no meta description, so Google writes the search snippet from whatever text it finds.

https://greenstalkgarden.com/pages/shop and https://greenstalkgarden.com/collections/vertical-planters use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://greenstalkgarden.com/pages/shop, whose canonical is https://greenstalkgarden.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://greenstalkgarden.com/pages/shop, https://greenstalkgarden.com/pages/how-it-works, https://greenstalkgarden.com/pages/our-story, https://greenstalkgarden.com/pages/faq, https://greenstalkgarden.com/pages/photo-gallery and https://greenstalkgarden.com/blogs/blog and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://greenstalkgarden.com/pages/photo-gallery, https://greenstalkgarden.com/blogs/blog, https://greenstalkgarden.com/pages/store-locator, https://greenstalkgarden.com/pages/online-retailers, https://greenstalkgarden.com/pages/rewards and https://greenstalkgarden.com/collections/fall-seed-starting-collection and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://greenstalkgarden.com/.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 991 words of visible text.

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

Opening the homepage sets 25 cookies (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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.