Website review, no card needed

legacyfoodstorage.com logo

legacyfoodstorage.com website review

Visit site (opens in a new tab)Reviewed 7 November 202631 issues · 88 checks

This review found 31 issues worth fixing on legacyfoodstorage.com, 12 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.8 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
149 ms113 msMay 16Oct 31119 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026119 ms
May 23, 2026121 ms
May 30, 2026117 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026120 ms
Jun 27, 2026136 ms
Jul 4, 2026137 ms
Jul 11, 2026137 ms
Jul 18, 2026145 ms
Jul 25, 2026132 ms
Aug 1, 2026131 ms
Aug 8, 2026136 ms
Aug 15, 2026130 ms
Aug 22, 2026130 ms
Aug 29, 2026128 ms
Sep 5, 2026125 ms
Sep 12, 2026122 ms
Sep 19, 2026124 ms
Sep 26, 2026122 ms
Oct 3, 2026123 ms
Oct 10, 2026129 ms
Oct 17, 2026125 ms
Oct 24, 2026129 ms
Oct 31, 2026119 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

Full-page screenshot of legacyfoodstorage.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. legacyfoodstorage.com at 0.4 s0.4 s
  2. legacyfoodstorage.com at 0.8 s0.8 s
  3. legacyfoodstorage.com at 1.1 s1.1 s
  4. legacyfoodstorage.com at 1.5 s1.5 s
  5. legacyfoodstorage.com at 1.9 s1.9 s
  6. legacyfoodstorage.com at 2.3 s2.3 s
  7. legacyfoodstorage.com at 2.6 s2.6 s
  8. legacyfoodstorage.com at 3.0 s3.0 s

Speed

2 to fix80
  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    500 ms

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

  • Improve image delivery

    100 ms · 53 KiB

    8 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Use efficient cache lifetimes

    100 ms · 20 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (klck.dev, staq-cdn.com and Shopify and others), adding 223 KiB and 52 ms of main-thread time.

  • Font display

    50 ms

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 245 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotional advertisement for a sitewide sale of Legacy Foo…”.

  • Real-user CLS: 0.23

    0.23

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

9 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 644 ms

    644 ms

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.0 s

    2.0 s

    Visually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.024

    0.024

    The layout barely moves while loading (CLS 0.024, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.29 g

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

4 checks passed
  • Page weight: 1.0 MB in 102 requests

    1.0 MB

    Your homepage downloads 1.0 MB in 102 requests on a phone: scripts 383 KiB (42), images 290 KiB (30) and fonts 257 KiB (5). That is a lean page.

  • 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

12 to fixGoogle 7984
  • 67 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Frames without titles

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

  • Interactive controls must not be nested (1 element)

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

  • 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.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (6 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (3 elements)

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 207 internal links, 1 external

    The homepage links to 207 pages on legacyfoodstorage.com and 1 external page.

6 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Lowest Cost / LB of Emergency Food - Free S+H - Legacy Food Storage - 25 Year Shelf Life - Best Value - Great Tasting -…”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Legacy Food Storage Company | The Best Value in Freeze Dried Food”.

  • Canonical URL set

    The canonical URL is https://www.legacyfoodstorage.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, OnlineStore, Organization, WebPage and WebSite.

  • 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://www.legacyfoodstorage.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (825 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.legacyfoodstorage.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://www.legacyfoodstorage.com/products/110-watt-solar-panel declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.legacyfoodstorage.com/products/110-watt-solar-panel all use the title “Legacy Food Storage Company | The Best Value in Freeze Dried Food”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.legacyfoodstorage.com/collections/bulk-meal-packages-1 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.legacyfoodstorage.com/collections/bulk-single-items, https://www.legacyfoodstorage.com/collections/bulk-single-items/ProteinBulkSingleIngredients, https://www.legacyfoodstorage.com/collections/bulk-single-items/FruitsBulkSingleIngredients, https://www.legacyfoodstorage.com/collections/bulk-single-items/VegetablesBulkSingleIngredients and https://www.legacyfoodstorage.com/collections/bulk-single-items/DairyBulkSingleIngredients use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://www.legacyfoodstorage.com/collections/bulk-meal-packages-1, https://www.legacyfoodstorage.com/collections/grab-go, https://www.legacyfoodstorage.com/collections/gluten-free, https://www.legacyfoodstorage.com/collections/entree-buckets, https://www.legacyfoodstorage.com/collections/breakfast-buckets and https://www.legacyfoodstorage.com/collections/survival-seeds and 6 others have 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 80 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9651
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5661618&Ver=2&mid=ab009b9d-c847-498c-b7b8-39abd12634b5&bo=1&sid=998ac6d0daad11f19095855211ec07d7&vid=998aeab0daad11f194bb9137f721767c&vids=1&msclkid=N&pi=918639831&lg=.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • Tap targets are thumb-sized

    23 of 25 tappable elements near the top are at least 24 px.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • 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 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 385 words of copy

    The homepage carries about 385 words of visible text.

7 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign Up”, “Contact Us” and “Why Shop With Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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 to fix
  • 8 trackers load before any consent

    8

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

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 legacyfoodstorage.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Product Reviews · Klickly Connector · Klaviyo Email Marketing Sms · Cartbite · Mbcbundlesapp · tidio.co · rechargecdn.com · revenuehunt.com · hextom.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

  • The footer still says © 2014.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Salt Lake City

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on legacyfoodstorage.com, including 6 speed issues, 2 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25