selectseeds.com website review

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Accessibe Accessibility Overlay and others), adding 1.2 MB and 571 ms of main-thread time.

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

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

Klaviyo costs a phone 186 ms of main-thread work and 501 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.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

6 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “15% Off All Seeds”.

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

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

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

Scripts block taps and scrolling for 250 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 7.5 MB in 382 requests on a phone: images 4.4 MB (24), other files 1.3 MB (243) and scripts 1.3 MB (99). Under 2 MB keeps phones on slow connections fast.

asclepias-penstemon-banner-mobile_800x.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 (493 KiB) 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.

4 images are downloaded at several times the size a phone draws them, for example rudbeckia-bouquet-info-card-002_1000x.jpg at 1,000 px wide, shown at 297 px. Resized copies would save about 173 KiB.

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

Required ARIA attributes must be provided: 14 elements on the page fail this check, rated critical by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

24 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 17 characters: “Select Seeds, Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 28 characters: “Homepage - Select Seeds, Co.”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 485 pages on selectseeds.com and 10 external pages.

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

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

10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

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

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

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