Website review, no card needed
survivalgardenseeds.com website review
Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 90 checks
This review found 39 issues worth fixing on survivalgardenseeds.com, 9 of them high impact, across 90 checks. The most urgent: page weight: 5.7 MB in 335 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Survival Garden Seeds
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #11,983 of 123,513 reviewed websitesbeats 87%
- #7,276 of 69,580 online storesbeats 85%
- #7,048 of 63,320 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 121 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 106 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 104 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 939 KiBAbout 939 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, cloudfront.net and Google CDN and others), adding 2.2 MB and 1.1 s of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Improve image delivery
150 ms · 315 KiB12 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 312 ms
312 msShopify costs a phone 312 ms of main-thread work and 868 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.
Reduce unused CSS
300 ms · 79 KiBAbout 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
cloudfront.net adds 237 ms
237 mscloudfront.net costs a phone 237 ms of main-thread work and 546 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.
2,663 HTML elements
The page has 2,663 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 217 ms
217 msGoogle CDN costs a phone 217 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 172 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
53 KiB10 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.0 s
23.0 sThe page becomes fully interactive after 23.0 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Holiday Early Bird Sale November 1-7”.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 344 ms
344 msScripts block taps and scrolling for 344 ms in total while the page loads. Good is under 200 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 465 ms
465 msReal visitors wait 465 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 121 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.058
0.058The layout barely moves while loading (CLS 0.058, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 335 requests
5.7 MBYour homepage downloads 5.7 MB in 335 requests on a phone: scripts 1.9 MB (120), images 1.6 MB (36) and fonts 923 KiB (21). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 192.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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)
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (12 elements)
ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Cultivate a Healthier Future with Heirloom Seeds – SurvivalGardenSeeds”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
406 internal links, 7 external
The homepage links to 406 pages on survivalgardenseeds.com and 7 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Grow a healthier, self-reliant future! Shop USA family-owned non-GMO heirloom seeds for delicious veggies, herbs & flow…”.
One H1 headline
Your main headline reads: “Seed kits for survival gardens to support your family's food needs for years to come”.
Canonical URL set
The canonical URL is https://survivalgardenseeds.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://survivalgardenseeds.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,484 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://survivalgardenseeds.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://survivalgardenseeds.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://survivalgardenseeds.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://survivalgardenseeds.com/collections/survival-seed-kits and https://survivalgardenseeds.com/collections/survival-seed-vaults all use the title “Heirloom Seed Packet Collections – SurvivalGardenSeeds”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://survivalgardenseeds.com/policies/shipping-policy and https://survivalgardenseeds.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://survivalgardenseeds.com/collections/survival-seed-kits and https://survivalgardenseeds.com/collections/survival-seed-vaults use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://survivalgardenseeds.com/collections/survival-seed-kits, whose canonical is https://survivalgardenseeds.com/collections/survival-seed-vaults. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://survivalgardenseeds.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.
2 checks passed
Tap targets are thumb-sized
60 of 62 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,339 words of copy
The homepage carries about 1,339 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop Survival Seed Vaults”.
17 calls to action
The homepage has 17 calls to action, for example “SHOP NOW”, “SHOP BY ZONE” and “SWAG SHOP”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 126 testimonial or review blocks, a star rating and 3 trust badges.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
No consent tool detected
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.
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at survivalgardenseeds.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Klaviyo Email Marketing Sms · Judge Me Reviews · Yoyo · Region Restrictions · Yoyoloyalty · Zipifypages · Zipify Oneclickupsell · Appstle Loyalty · goaffpro.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Wellsville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on survivalgardenseeds.com, including 16 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.