Website review, no card needed
herbsdaily.com website review
Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 99 checks
This review found 47 issues worth fixing on herbsdaily.com, 15 of them high impact, across 99 checks. The most urgent: mobile performance score: 31. 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
67D- #108,008 of 120,386 reviewed websitesbeats 9%
- #64,460 of 68,161 online storesbeats 4%
- #59,288 of 62,115 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 359 ms |
| May 23, 2026 | 363 ms |
| May 30, 2026 | 366 ms |
| Jun 6, 2026 | 364 ms |
| Jun 13, 2026 | 360 ms |
| Jun 20, 2026 | 350 ms |
| Jun 27, 2026 | 362 ms |
| Jul 4, 2026 | 362 ms |
| Jul 11, 2026 | 378 ms |
| Jul 18, 2026 | 371 ms |
| Jul 25, 2026 | 366 ms |
| Aug 1, 2026 | 371 ms |
| Aug 8, 2026 | 363 ms |
| Aug 15, 2026 | 362 ms |
| Aug 22, 2026 | 369 ms |
| Aug 29, 2026 | 366 ms |
| Sep 5, 2026 | 370 ms |
| Sep 12, 2026 | 379 ms |
| Sep 19, 2026 | 378 ms |
| Sep 26, 2026 | 376 ms |
| Oct 3, 2026 | 371 ms |
| Oct 10, 2026 | 363 ms |
| Oct 17, 2026 | 357 ms |
| Oct 24, 2026 | 354 ms |
| Oct 31, 2026 | 349 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.0 s
Speed
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,209 HTML elements
The page has 4,209 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
600 ms · 347 KiBAbout 347 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
800 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (gsitrix.com, omnisnippet1.com and Other Google APIs/SDKs and others), adding 812 KiB and 591 ms of main-thread time.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 501 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 88 KiBAbout 88 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.
Improve image delivery
344 KiB26 images could be 344 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
262 KiB36 files are served with short cache lifetimes, so returning visitors download them again (262 KiB).
Shopify adds 78 ms
78 msShopify costs a phone 78 ms of main-thread work and 338 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.
Minify CSS
100 ms · 9 KiB9 KiB could be saved by minifying CSS.
Legacy JavaScript
80 KiBPolyfills for old browsers add 80 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
18 KiB18 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: 11 ms
11 msYour server sent the HTML in 11 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.
Real-user CLS: 0.39
0.39For real visitors the layout shifts by 0.39 (75th percentile). Good is under 0.1.
Time to Interactive: 18.9 s
18.9 sThe page becomes fully interactive after 18.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.874
0.874The layout shifts by 0.874 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We value your privacy We use cookies and tracking technolog…”.
Total Blocking Time: 673 ms
673 msScripts block taps and scrolling for 673 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 318 ms
318 msReal visitors wait 318 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
58 images without width and height
58 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 359 ms to 349 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.8 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.2 MB in 298 requests
3.2 MBYour homepage downloads 3.2 MB in 298 requests on a phone: scripts 1.2 MB (101), images 968 KiB (78) and other files 743 KiB (97). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
149 KiB1 image is downloaded at several times the size a phone draws it, for example Untitled_design_2_-Picsart-AiImageEnhancer_2048x.png at 3,100 px wide, shown at 390 px. Resized copies would save about 149 KiB.
About 0.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Orphan list items
Some list items are not inside a list.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (132 elements)
All page content should be contained by landmarks: 132 elements on the page fail 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
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
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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
Meta description is long (249 characters)
Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization, Store and WebSite) but with 2 problems, for example “Organization: missing name”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
800 internal links, 4 external
The homepage links to 800 pages on herbsdaily.com and 4 external pages.
5 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “HerbsDaily: Vitamins, Nutrition And Herbal Supplements Store”.
Canonical URL set
The canonical URL is https://www.herbsdaily.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.herbsdaily.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.herbsdaily.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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,272 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.herbsdaily.com/pages/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 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.
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 4 pages that loaded have a <title>.
Best practices
37 small tap targets
37 of 124 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 584 words of copy
The homepage carries about 584 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BY BRAND” and “Buy Now”.
21 calls to action
The homepage has 21 calls to action, for example “Login / Register”, “Contact Us” and “Shop by Brand”.
21 short forms
21 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 1 more (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 2 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.
56 other companies contacted
Loading the homepage contacts 56 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 herbsdaily.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Multifeeds · Nova Multi Currency Converter · Omnisend · b-cdn.net · trafficmanager.net · gtranslate.io · amazonaws.com · shareasale.com · cloudfront.net · useamp.com · Swym Wishlist Plus
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 Tag Manager | Hotjar | 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 47 issues on herbsdaily.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.