Website review, no card needed
superfoods.io website review
Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 73 checks
This review found 29 issues worth fixing on superfoods.io, 9 of them high impact, across 73 checks. The most urgent: aRIA attributes must conform to valid values (3 elements). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
1.4 s
2.8 s
4.3 s
5.7 s
7.1 s
8.5 s
10.0 s
11.4 s
Speed
Mobile performance score: 83
83/100Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
800 ms · 113 KiB4 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used 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.
1 third-party service on the page
1 third-party service load with your homepage (Shopify), adding 12 KiB and 2 ms of main-thread time.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 278 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (10.8 s).
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
4 checks passed
Time to Interactive: 3.2 s
3.2 sThe page is fully interactive after 3.2 s.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
3 images below the first screen load straight away
3 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.18 g of CO₂e: 21.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 633 KiB in 42 requests
633 KiBYour homepage downloads 633 KiB in 42 requests on a phone: images 376 KiB (23), scripts 168 KiB (12) and other files 61 KiB (5). That is a lean page.
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.
Accessibility
ARIA attributes must conform to valid values (3 elements)
ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<dt> and <dd> elements must be contained by a <dl> (6 elements)
<dt> and <dd> elements must be contained by a <dl>: 6 elements on the page fail this check, rated serious by axe-core.
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (3 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Invalid ARIA attributes
6 elements use ARIA attributes their role does not allow, which confuses screen readers.
Unlabelled dropdowns
1 dropdown has no label.
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.
37 tap targets too small
37 tap targets are too small or too close together to hit reliably with a finger.
2 form fields without a label
2 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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (11 characters)
Your title is only 11 characters: “eSuperFoods”. 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.
No XML sitemap
No XML sitemap at https://superfoods.io/sitemap.xml, so Google discovers your pages only by following links.
45 internal links, 6 external
The homepage links to 45 pages on superfoods.io and 6 external pages.
4 checks passed
One H1 headline
Your main headline reads: “<img src="//superfoods.io/cdn/shop/files/logo_ab2479c1-e956-49f6-9283-cec702cf2662_250x.png?v=1613734286" srcset="//sup…”.
Canonical URL set
The canonical URL is https://superfoods.io/.
Structured data in place
Structured data found: Organization, Product and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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 (607 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://superfoods.io/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://superfoods.io/products/lorem-ipsum-product and https://superfoods.io/collections/frontpage/products/lorem-ipsum-product all use the title “Lorem Ipsum Product – eSuperFoods”. 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://superfoods.io/collections/all and https://superfoods.io/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages share a meta description
https://superfoods.io/pages/oysters, https://superfoods.io/pages/caviar, https://superfoods.io/pages/clams-shrimp, https://superfoods.io/pages/tools-gear and https://superfoods.io/pages/farm-tours use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://superfoods.io/collections/frontpage/products/lorem-ipsum-product, whose canonical is https://superfoods.io/products/lorem-ipsum-product. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages slow to respond
https://superfoods.io/pages/oysters, https://superfoods.io/pages/caviar, https://superfoods.io/pages/clams-shrimp, https://superfoods.io/pages/tools-gear and https://superfoods.io/products/lorem-ipsum-product took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage 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 an H1
Each page we checked has a main headline.
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
5 small tap targets
5 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 507 words of copy
The homepage carries about 507 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY NOW”.
11 calls to action
The homepage has 11 calls to action, for example “buy now”, “shop now” and “BUY NOW”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 superfoods.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on superfoods.io, including 6 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.