marshallsgarden.com website review

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

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

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

27 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Trust Pilot, Google Tag Manager and Clarity and others), adding 960 KiB and 613 ms of main-thread time.

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

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

Trust Pilot costs a phone 128 ms of main-thread work and 391 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.

4 long tasks block the main thread while loading, the longest for 101 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.

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 392 requests on a phone: images 2.4 MB (49), other files 1.0 MB (187) and scripts 1,021 KiB (90). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

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

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “Marshalls Garden: Buy Plants, Seeds, Vegetables & Garden Equipment”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 1,649 pages on marshallsgarden.com and 14 external pages.

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

https://marshallsgarden.com/collections/houseplant-seeds, https://marshallsgarden.com/collections/seeds, https://marshallsgarden.com/collections/asparagus-seeds, https://marshallsgarden.com/collections/aubergine-seeds and https://marshallsgarden.com/collections/artichoke-seeds have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 557 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 mores (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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.