Website review, no card needed

evergoodfoods.com logo

evergoodfoods.com website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 79 checks

This review found 28 issues worth fixing on evergoodfoods.com, 10 of them high impact, across 79 checks. The most urgent: page weight: 66.3 MB in 229 requests. 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
1.5 s960 msMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.2 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
130 ms86 msMay 16Oct 31125 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 202694 ms
May 30, 202691 ms
Jun 6, 202694 ms
Jun 13, 202691 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202697 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 2026103 ms
Aug 15, 202697 ms
Aug 22, 202699 ms
Aug 29, 202697 ms
Sep 5, 202699 ms
Sep 12, 2026102 ms
Sep 19, 2026105 ms
Sep 26, 2026110 ms
Oct 3, 2026110 ms
Oct 10, 2026110 ms
Oct 17, 2026111 ms
Oct 24, 2026121 ms
Oct 31, 2026125 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 evergoodfoods.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. evergoodfoods.com at 0.7 s0.7 s
  2. evergoodfoods.com at 1.4 s1.4 s
  3. evergoodfoods.com at 2.1 s2.1 s
  4. evergoodfoods.com at 2.8 s2.8 s
  5. evergoodfoods.com at 3.5 s3.5 s
  6. evergoodfoods.com at 4.2 s4.2 s
  7. evergoodfoods.com at 4.9 s4.9 s
  8. evergoodfoods.com at 5.5 s5.5 s

Speed

6 to fix65
  • Reduce unused JavaScript

    1.6 s · 404 KiB

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

  • Improve image delivery

    100 ms · 1,006 KiB

    15 images could be 1,006 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.

  • Mobile performance score: 65

    65/100

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

  • Use efficient cache lifetimes

    550 ms · 147 KiB

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

  • Minify JavaScript

    450 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Facebook and Google Tag Manager and others), adding 740 KiB and 349 ms of main-thread time.

  • Font display

    200 ms

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

  • Reduce unused CSS

    150 ms · 34 KiB

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

  • Render-blocking requests

    150 ms

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.9 s

    13.9 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

8 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.7 s

    1.7 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 589 ms

    589 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

  • Total Blocking Time: 54 ms

    54 ms

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

Images and page weight

1 to fix70
  • Page weight: 66.3 MB in 229 requests

    66.3 MB

    Your homepage downloads 66.3 MB in 229 requests on a phone: media 63.0 MB (11), images 1.4 MB (36) and scripts 870 KiB (69). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (246 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.

  • About 18.8 g of CO₂ per visit

    18.78 g

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

2 checks passed
  • 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

4 to fixGoogle 8593
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 13 images without alt text

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 8588
  • Title is short (24 characters)

    Your title is only 24 characters: “Evergood Sausage Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 1 link with vague text

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

  • 45 internal links, 9 external

    The homepage links to 45 pages on evergoodfoods.com and 9 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “A family business that has been in San Francisco for over 98 years. Evergood Food Sausage Company has grown from a smal…”.

  • One H1 headline

    Your main headline reads: “Evergood Foods”.

  • Canonical URL set

    The canonical URL is https://evergoodfoods.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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://evergoodfoods.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix60
  • 1 page without a title

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

  • 1 linked page hidden from search

    https://evergoodfoods.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://evergoodfoods.com/pages/build-your-bundle and https://evergoodfoods.com/products/mix-match all use the title “Build Your Bundle”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://evergoodfoods.com/pages/store-locator, https://evergoodfoods.com/pages/build-your-bundle, https://evergoodfoods.com/collections/variety-packs, https://evergoodfoods.com/pages/our-story, https://evergoodfoods.com/pages/contact and https://evergoodfoods.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://evergoodfoods.com/pages/store-locator, https://evergoodfoods.com/pages/build-your-bundle, https://evergoodfoods.com/collections/variety-packs, https://evergoodfoods.com/collections/all, https://evergoodfoods.com/pages/our-story and https://evergoodfoods.com/pages/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://evergoodfoods.com/pages/store-locator, https://evergoodfoods.com/pages/build-your-bundle and https://evergoodfoods.com/collections/variety-packs have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://evergoodfoods.com/customer_authentication/redirect, https://evergoodfoods.com/products/mix-match and https://evergoodfoods.com/products/the-evergood-bundle-1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    35 of 39 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 295 words of copy

    The homepage carries about 295 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 ALL”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop All”, “Contact” and “Shop”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 13 cookies set on arrival

    13

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

  • 25 other companies contacted

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

Apps your storefront loads

Tolstoy · Seal Subscriptions · Judge Me Reviews · Klaviyo Email Marketing Sms · Gift Box Builder

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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on evergoodfoods.com, including 11 speed issues, 3 SEO issues and 1 conversion gap. 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