Website review, no card needed

super1foods.com logo

super1foods.com website review

Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 74 checks

This review found 26 issues worth fixing on super1foods.com, 8 of them high impact, across 74 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
3.3 s2.6 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
290 ms214 msMay 9Oct 24281 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026230 ms
May 16, 2026227 ms
May 23, 2026227 ms
May 30, 2026223 ms
Jun 6, 2026225 ms
Jun 13, 2026229 ms
Jun 20, 2026229 ms
Jun 27, 2026236 ms
Jul 4, 2026229 ms
Jul 11, 2026228 ms
Jul 18, 2026229 ms
Jul 25, 2026230 ms
Aug 1, 2026233 ms
Aug 8, 2026239 ms
Aug 15, 2026243 ms
Aug 22, 2026245 ms
Aug 29, 2026249 ms
Sep 5, 2026251 ms
Sep 12, 2026250 ms
Sep 19, 2026254 ms
Sep 26, 2026258 ms
Oct 3, 2026261 ms
Oct 10, 2026272 ms
Oct 17, 2026275 ms
Oct 24, 2026281 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 super1foods.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

100
  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Use efficient cache lifetimes

    9 KiB

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100 (desktop: 28). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix0
  • 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.

  • Real-user CLS: 0.37

    0.37

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 438 ms

    438 ms

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

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

    +22%

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

  • Real-user TTFB: 838 ms

    838 ms

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

8 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

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

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

    -11%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

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

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website is using a security service to protect itself …”.

  • Speed Index: 0.8 s

    0.8 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

1 to fix98
  • An image on the first screen is lazy-loaded

    S1FW-2607063-S1F---Web-102126-Buy-Big-Save-Big_760x400.webp 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).

  • 1 image below the first screen load straight away

    1 image further down the page (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.00 g of CO₂ per visit

    0.00 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.00 g of CO₂e: 0.4 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

  • Page weight: 11 KiB in 4 requests

    11 KiB

    Your homepage downloads 11 KiB in 4 requests on a phone: stylesheets 5 KiB (1), images 4 KiB (2) and HTML 2 KiB (1). That is a lean page.

Accessibility

5 to fixGoogle 9694
  • 3 text elements with low contrast

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

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

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

  • 5 form fields without a label

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

  • 1 link without text

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

  • No main landmark

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 4066
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • Meta description is long (172 characters)

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 784 internal links, 11 external

    The homepage links to 784 pages on super1foods.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Fall Recipes”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Super 1 Foods | Order Groceries Online for Pickup or Delivery”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: OnlineStore and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.super1foods.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    25%

    A phone browser shows 5,758 words, but the HTML your server sends has only 1,430. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, 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.

  • No llms.txt

    There is no https://www.super1foods.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://www.super1foods.com/sm/pickup/rsid/600 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.super1foods.com/sm/pickup/rsid/600 all use the title “Super 1 Foods | Order Groceries Online for Pickup or Delivery”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://www.super1foods.com/sm/pickup/rsid/600/help, https://www.super1foods.com/categories/produce-id-C201, https://www.super1foods.com/categories/produce/dried-fruits-nuts-grains-id-C201004, https://www.super1foods.com/categories/dried-fruits-nuts-grains/fruits-id-C20100401, https://www.super1foods.com/categories/dried-fruits-nuts-grains/nuts-id-C20100402 and https://www.super1foods.com/categories/produce/fruits-id-C201001 and 6 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.super1foods.com/sm/pickup/rsid/600/contact-us 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 200 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “[object Object] getRecommendationsPaginated”.

2 checks passed
  • Tap targets are thumb-sized

    91 of 103 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

  • 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 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 5,758 words of copy

    The homepage carries about 5,758 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Join Our Team”, “Contact Us” and “Hi GuestSign In or Register”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (measured from a US location before any click).

  • 45 other companies contacted

    Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 super1foods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on super1foods.com, including 6 speed issues, 4 SEO issues and 3 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