Website review, no card needed
naturalstacks.com website review
Visit site (opens in a new tab)Reviewed 6 November 202644 issues · 86 checks
This review found 44 issues worth fixing on naturalstacks.com, 16 of them high impact, across 86 checks. The most urgent: youTube adds 1.0 s. 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
Site score
74C- #76,973 of 109,350 reviewed websitesbeats 26%
- #48,456 of 61,859 online storesbeats 18%
- #45,606 of 56,401 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 195 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 185 ms |
| Jul 18, 2026 | 184 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 190 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 183 ms |
| Oct 17, 2026 | 191 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 198 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
1.6 s
3.3 s
4.9 s
6.5 s
8.2 s
9.8 s
11.4 s
13.1 s
Speed
YouTube adds 1.0 s
1.0 sYouTube costs a phone 1.0 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 11.2 s
A phone's processor spends 11.2 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,422 HTML elements
The page has 4,422 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Klaviyo and others), adding 4.2 MB and 2.7 s of main-thread time.
Improve image delivery
350 ms · 1.6 MB26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused JavaScript
1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 783 ms
783 msGoogle Tag Manager costs a phone 783 ms of main-thread work and 842 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.
Use efficient cache lifetimes
200 ms · 316 KiB33 files are served with short cache lifetimes, so returning visitors download them again (316 KiB).
Klaviyo adds 249 ms
249 msKlaviyo costs a phone 249 ms of main-thread work and 483 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 284 ms. During a long task the page ignores taps.
Shopify adds 184 ms
184 msShopify costs a phone 184 ms of main-thread work and 442 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.
Google CDN adds 112 ms
112 msGoogle CDN costs a phone 112 ms of main-thread work and 349 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
83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 17.9 s
17.9 sYour largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “better brain. better life.”.
Speed Index: 25.7 s
25.7 sVisually, the page fills in at 25.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 56.4 s
56.4 sThe page becomes fully interactive after 56.4 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 74% slower for real visitors
+74%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 826 ms
826 msReal visitors wait 826 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 195 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.079
0.079The layout barely moves while loading (CLS 0.079, good is under 0.1).
Images and page weight
Page weight: 11.7 MB in 489 requests
11.7 MBYour homepage downloads 11.7 MB in 489 requests on a phone: images 5.5 MB (112), scripts 4.5 MB (182) and other files 881 KiB (148). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
1.2 MB15 images are downloaded at several times the size a phone draws them, for example test3.webp at 1,600 px wide, shown at 312 px. Resized copies would save about 1.2 MB.
18 images below the first screen load straight away
18 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
12 images in older formats
12 images (1.7 MB) 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 3.3 g of CO₂ per visit
3.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.32 g of CO₂e: 398.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (2 elements)
Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 86 images in the HTML carry an alt attribute.
45 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: 45 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
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.naturalstacks.com")”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
160 internal links, 10 external
The homepage links to 160 pages on naturalstacks.com and 10 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Start building a better, faster, sharper brain today with Natural Stacks. Premium ingredients, transparent formulas and…”.
Title: 53 characters
Your title is a healthy 53 characters: “Natural Stacks - Premium Supplements for Brain Health”.
Canonical URL set
The canonical URL is https://www.naturalstacks.com/.
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://www.naturalstacks.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,111 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.naturalstacks.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.naturalstacks.com/collections/sleep, which answers with an error. Visitors hit a dead end and search engines drop it.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
Best practices
8 third-party cookies
8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “$(...).slick is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
13 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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.
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 563 words of copy
The homepage carries about 563 words of visible text.
5 checks passed
50 calls to action
The homepage has 50 calls to action, for example “SHOP BY BENEFITS”, “Shop All” and “Shop By Type”.
21 short forms
21 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 41 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
55 other companies contacted
Loading the homepage contacts 55 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 naturalstacks.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 21 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Tapcart Mobile App · Pagefly Ai Page Builder · Minmaxify Order Limits · Squaredance · Okendo · Frequently Bought · Seo Manager Venntov · Reelup Shoppable Videos Reels · Klaviyo Email Marketing Sms · Klickly Connector · Gdpr Backpack · Applovin Shop Integration · Aftersell · rechargecdn.com · electricsms.com · googleapis.com · amazonaws.com · govx.com · retention.com · revoffers.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Lewes
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on naturalstacks.com, including 23 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.