Website review, no card needed
honeybeeherb.com website review
Visit site (opens in a new tab)Reviewed 13 November 202628 issues · 87 checks
This review found 28 issues worth fixing on honeybeeherb.com, 8 of them high impact, across 87 checks. The most urgent: page weight: 5.2 MB in 353 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
87B- #7,648 of 109,350 reviewed websitesbeats 90%
- #4,460 of 61,859 online storesbeats 89%
- #4,330 of 56,401 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 135 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 132 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 133 ms |
| Nov 7, 2026 | 137 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.0 s
1.9 s
2.9 s
3.8 s
4.8 s
5.7 s
6.7 s
7.6 s
Speed
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
1,006 KiBAbout 1,006 KiB of JavaScript is downloaded but never used on this page.
Mobile performance score: 72
72/100Your mobile performance score is 72. 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 (leadconnectorhq.com, Shopify and loox.io and others), adding 1.5 MB and 803 ms of main-thread time.
Render-blocking requests
600 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
leadconnectorhq.com adds 192 ms
192 msleadconnectorhq.com costs a phone 192 ms of main-thread work and 867 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.
2,258 HTML elements
The page has 2,258 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 171 ms
171 msShopify costs a phone 171 ms of main-thread work and 318 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
150 ms · 98 KiBAbout 98 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 230 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
83 KiB7 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).
Improve image delivery
42 KiB5 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 504 ms
504 msScripts block taps and scrolling for 504 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 135 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 353 requests
5.2 MBYour homepage downloads 5.2 MB in 353 requests on a phone: other files 2.3 MB (131), scripts 1.6 MB (131) and fonts 393 KiB (14). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
November-Giveaway_-Blown-Glass-Gift-Set-4.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
3 images in older formats
3 images (166 KiB) 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 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 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 (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 173 images in the HTML carry an alt attribute.
50 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: 50 passed and 6 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 (“Honeybee Herb” and “The most trusted online smoke shop for quartz ban…”). One clear main headline is easier for people and search engines.
217 internal links, 6 external
The homepage links to 217 pages on honeybeeherb.com and 6 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Honeybee Herb, an online head shop provides high-quality dabbing & smoking accessories ex: quartz bangers, titanium nai…”.
Title: 56 characters
Your title is a healthy 56 characters: “Buy Top-Rated Smoking Accessories Online | Honeybee Herb”.
Canonical URL set
The canonical URL is https://honeybeeherb.com/.
Structured data in place
Structured data found: Brand, OnlineStore, 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://honeybeeherb.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,152 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://honeybeeherb.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://pixel.sitescout.com/iap/3760f89342ec9529.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 low-resolution images
6 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
24 of 25 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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 744 words of copy
The homepage carries about 744 words of visible text.
5 checks passed
10 calls to action
The homepage has 10 calls to action, for example “SHOP BY CATEGORIES”, “ORDER SUPPORT” and “Shop Honeybee picks”.
3 short forms
3 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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, 3 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.
29 other companies contacted
Loading the homepage contacts 29 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 honeybeeherb.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klickly Connector · Paywhirl Subscriptions · Also Bought · Onward · Flashx Price Editor · Frequently Bought · Trakt · TEPO Product Options (Qikify) · loox.io
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
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on honeybeeherb.com, including 12 speed issues, 1 SEO issue 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.