Website review, no card needed
feelgreatbotanics.com website review
Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 84 checks
This review found 37 issues worth fixing on feelgreatbotanics.com, 6 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
88B- #6,008 of 126,006 reviewed websitesbeats 93%
- #3,196 of 70,328 online storesbeats 93%
- #3,096 of 63,870 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.2 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 192 ms |
| Sep 19, 2026 | 205 ms |
| Sep 26, 2026 | 203 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
2.1 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 83
83/100Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Lucky Orange and others), adding 976 KiB and 520 ms of main-thread time.
Reduce unused JavaScript
10 ms · 457 KiBAbout 457 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10 ms faster on a phone.
Google Tag Manager adds 321 ms
321 msGoogle Tag Manager costs a phone 321 ms of main-thread work and 522 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 368 ms. During a long task the page ignores taps.
Improve image delivery
310 KiB5 images could be 310 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
150 ms · 143 KiB143 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
226 KiB5 files are served with short cache lifetimes, so returning visitors download them again (226 KiB).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Reduce unused CSS
11 KiBAbout 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 734 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VIVAZEN® restores focus, relief, and calm energy—so you can…”. Most of its time is element render delay (2.3 s).
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 194 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
3 checks passed
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 193 ms
193 msScripts block the page for only 193 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.6 MB in 120 requests
9.6 MBYour homepage downloads 9.6 MB in 120 requests on a phone: images 7.5 MB (16), scripts 1.3 MB (39) and fonts 622 KiB (10). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
241 KiB2 images are downloaded at several times the size a phone draws them, for example ult-3xRed_cfe4271f-4f66-48d0-bd4d-084935fe9ed9.jpg at 2,048 px wide, shown at 211 px. Resized copies would save about 241 KiB.
2 images below the first screen load straight away
2 images further down the page (267 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.71 g of CO₂e: 325.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
4 text elements with low contrast
4 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 (31 elements)
All page content should be contained by landmarks: 31 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 (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (2 elements)
Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 14 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
12 internal links, 47 external
The homepage links to 12 pages on feelgreatbotanics.com and 47 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “The World Runs On Chaos.You Don't Have to. Vivazen is fast, natural relief and focus trusted by millions — when life de…”.
One H1 headline
Your main headline reads: “When Life Hits, Stay Ready”.
Title: 53 characters
Your title is a healthy 53 characters: “Vivazen: Fast and Natural Relief, Trusted By Millions”.
Canonical URL set
The canonical URL is https://feelgreatbotanics.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://feelgreatbotanics.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://feelgreatbotanics.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.
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.
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 (942 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://feelgreatbotanics.com/pages/discovery-kit-landing-page-b and https://feelgreatbotanics.com/pages/discovery-kit-landing-page-a all use the title “Discovery Kit LP A - Feel Great Botanics”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://feelgreatbotanics.com/pages/discovery-kit-landing-page-b, https://feelgreatbotanics.com/shop, https://feelgreatbotanics.com/pages/discovery-kit-landing-page-a, https://feelgreatbotanics.com/pages/store-locator, https://feelgreatbotanics.com/policy-page and https://feelgreatbotanics.com/terms-of-use and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://feelgreatbotanics.com/pages/discovery-kit-landing-page-b, whose canonical is https://feelgreatbotanics.com/pages/discovery-kit-landing-page-a. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://feelgreatbotanics.com/pages/discovery-kit-landing-page-b and https://feelgreatbotanics.com/pages/discovery-kit-landing-page-a have no <h1> headline, so visitors and search engines get no clear main topic.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 7 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 7 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 549 words of copy
The homepage carries about 549 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP VIVAZEN SHOP VIVAZEN”.
10 calls to action
The homepage has 10 calls to action, for example “SHOP”, “SHOP VIVAZEN” and “APPLY”.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
21 other companies contacted
Loading the homepage contacts 21 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 feelgreatbotanics.com, 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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on feelgreatbotanics.com, including 11 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.