Website review, no card needed
five-wellness.com website review
Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 81 checks
This review found 37 issues worth fixing on five-wellness.com, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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.2 s
2.4 s
3.6 s
4.7 s
5.9 s
7.1 s
8.3 s
9.5 s
Speed
Reduce unused JavaScript
1.6 s · 497 KiBAbout 497 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.
Use efficient cache lifetimes
1.0 s · 503 KiB25 files are served with short cache lifetimes, so returning visitors download them again (503 KiB).
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 4.4 s 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 (alia-prod.com, Yotpo and minmaxify.com and others), adding 1.3 MB and 1.8 s of main-thread time.
alia-prod.com adds 759 ms
759 msalia-prod.com costs a phone 759 ms of main-thread work and 343 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.
Render-blocking requests
750 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
400 ms · 183 KiB9 images could be 183 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Reduce unused CSS
300 ms · 86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Yotpo adds 273 ms
273 msYotpo costs a phone 273 ms of main-thread work and 280 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.
minmaxify.com adds 259 ms
259 msminmaxify.com costs a phone 259 ms of main-thread work and 8 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 258 ms. During a long task the page ignores taps.
1,559 HTML elements
The page has 1,559 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 115 ms
115 msShopify costs a phone 115 ms of main-thread work and 367 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.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.1 s
12.1 sYour largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 744 ms
744 msScripts block taps and scrolling for 744 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
2 images without width and height
2 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 324 requests
3.1 MBYour homepage downloads 3.1 MB in 324 requests on a phone: scripts 1.2 MB (76), other files 910 KiB (165) and images 390 KiB (41). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.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 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to fivegummies.com, not five-wellness.com, so Google may credit that host instead.
2 H1 headlines
There are 2 <h1> headlines (“” and “shop before December 11”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Corporation, Organization and WebSite) but with 1 problem, for example “Corporation: sameAs is not an absolute URL ("https:www.leafly.com/brands/five")”.
11 links crawlers can't follow
11 links have no real href, so search engines can't follow them.
68 internal links, 3 external
The homepage links to 68 pages on five-wellness.com and 3 external pages.
5 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “We’ve got delicious edibles that pack a punch (depending on what you prefer), all tied up with a “conveniently delivere…”.
Title: 49 characters
Your title is a healthy 49 characters: “five™ Edibles | Buy Gummies, Oil, and More – Five”.
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://five-wellness.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (839 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://five-wellness.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://five-wellness.com/pages/build-your-bundle and https://five-wellness.com/pages/rewards, which answer with an error. Visitors hit a dead end and search engines drop them.
13 pages without a meta description
https://five-wellness.com/collections/gummies, https://five-wellness.com/collections/sleep, https://five-wellness.com/collections/seltzers, https://five-wellness.com/collections/oil, https://five-wellness.com/collections/capsules and https://five-wellness.com/collections/all and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://five-wellness.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://five-wellness.com/collections/daily-dose, https://five-wellness.com/collections/microdose and https://five-wellness.com/pages/about-us took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 “Cannot read properties of undefined (reading 'isInitialized')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
About 565 words of copy
The homepage carries about 565 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “shop high dose , high dose”.
13 calls to action
The homepage has 13 calls to action, for example “Shop By Product”, “shop all products” and “shop by strength”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 31 testimonial or review blocks, a star rating and 11 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
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.
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 five-wellness.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
Yotpo Loyalty Rewards · Gorgias Live Chat Helpdesk · Triplewhale · Minmaxify Order Limits · nofraud.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
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 five-wellness.com, including 20 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.