seedworldusa.com website review

25 images could be 481 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Shopify and Other Google APIs/SDKs and others), adding 1.4 MB and 684 ms of main-thread time.

14 KiB could be saved by minifying JavaScript.

Google CDN costs a phone 223 ms of main-thread work and 296 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 144 ms of main-thread work and 622 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.

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

About 29 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 50 ms).

Polyfills for old browsers add 7 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 17.4 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 21.6 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

23 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' tap response (inp) went from 104 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.3 MB in 270 requests on a phone: images 2.6 MB (57), scripts 1.2 MB (100) and other files 653 KiB (87). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (325 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 1.49 g of CO₂e: 179.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 dropdowns have no label.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Seed World - Grass Seed, Food Plot Seed, Gardening, Lawn, Pest Control”.

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 281 pages on seedworldusa.com and 7 external pages.

https://www.seedworldusa.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.seedworldusa.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.seedworldusa.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.seedworldusa.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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