Website review, no card needed
sereneherbs.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 82 checks
This review found 34 issues worth fixing on sereneherbs.com, 14 of them high impact, across 82 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
Site score
79C- #43,677 of 96,258 reviewed websitesbeats 49%
- #27,642 of 52,106 online storesbeats 41%
- #26,428 of 47,195 Shopify storesbeats 38%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 155 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 172 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 168 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 166 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 177 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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Reduce unused JavaScript
2.4 s · 768 KiBAbout 768 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.3 s
A phone's processor spends 8.3 s on main-thread work while loading, 3.9 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, Shopify and Google Tag Manager and others), adding 2.1 MB and 1.8 s of main-thread time.
Use efficient cache lifetimes
400 ms · 541 KiB28 files are served with short cache lifetimes, so returning visitors download them again (541 KiB).
alia-prod.com adds 556 ms
556 msalia-prod.com costs a phone 556 ms of main-thread work and 916 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.
Improve image delivery
300 ms · 310 KiB8 images could be 310 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
550 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Duplicated JavaScript
400 ms · 124 KiB124 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 400 ms faster on a phone.
Shopify adds 335 ms
335 msShopify costs a phone 335 ms of main-thread work and 502 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.
1,811 HTML elements
The page has 1,811 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 231 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need.
Minify JavaScript
8 KiB8 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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.1 s
17.1 sYour largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Loved by 300,000+ Customers No Tricks. Just A Gut Reset Tre…”.
Time to Interactive: 29.5 s
29.5 sThe page becomes fully interactive after 29.5 s. Good is under 3.8 s.
Speed Index: 15.1 s
15.1 sVisually, the page fills in at 15.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 699 ms
699 msScripts block taps and scrolling for 699 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 155 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 164 ms
164 msReal visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (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.
Real-user TTFB: 777 ms
777 msReal visitors wait 777 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 376 requests
5.4 MBYour homepage downloads 5.4 MB in 376 requests on a phone: scripts 2.1 MB (128), images 1.1 MB (38) and fonts 1.0 MB (16). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (55 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 3 mores 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 (12 characters)
Your title is only 12 characters: “Serene Herbs”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “Natural wellness for your whole home”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
60 internal links, 7 external
The homepage links to 60 pages on sereneherbs.com and 7 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://sereneherbs.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://sereneherbs.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 (1,850 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sereneherbs.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://sereneherbs.com/collections/all, https://sereneherbs.com/pages/contact, https://sereneherbs.com/pages/frequently-asked-questions, https://sereneherbs.com/pages/wellness-guides, https://sereneherbs.com/pages/quiz-bloating and https://sereneherbs.com/collections/metabolism and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://sereneherbs.com/collections/best-sellers-serene-herbs and https://sereneherbs.com/collections/bundles-1 use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://sereneherbs.com/pages/frequently-asked-questions and https://sereneherbs.com/pages/quiz-bloating have 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 27 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot set property prefix of #<Element> which has only a getter”.
1 checks passed
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.
About 1,320 words of copy
The homepage carries about 1,320 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Contact”, “Shop All” and “Get Your Offer”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 138 testimonial or review blocks, a star rating, 18 trust badges and “Loved by 300,000+ Customers”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email 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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
39 cookies set on arrival
39Opening the homepage sets 39 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.
65 other companies contacted
Loading the homepage contacts 65 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 sereneherbs.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 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Onward · Instant Ai Page Builder · Gempages Builder · Triplewhale · Pagefly Ai Page Builder · Ta Mappy Store Locator Maps · Applovin Shop Integration · Trakt · Ali Reviews · Discount Kit · Zobi · Upcart · web.app · trustpilot.com · socialsnowball.io · loox.io · amazonaws.com · archive-digger.com · kount.com · gandalf.ee
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
- 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 34 issues on sereneherbs.com, including 17 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.