Website review, no card needed
honeybalm.com website review
Visit site (opens in a new tab)Reviewed 20 November 202619 issues · 60 checks
This review found 19 issues worth fixing on honeybalm.com, 5 of them high impact, across 60 checks. The most urgent: page weight: 5.1 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 177 ms |
| Oct 31, 2026 | 195 ms |
| Nov 7, 2026 | 199 ms |
| Nov 14, 2026 | 196 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
Speed
Not measured in this review.
Core Web Vitals
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 134 ms to 196 ms 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 your site (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 199 ms
199 msReal visitors wait 199 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 522 ms
522 msReal visitors wait 522 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.1 MB
5.1 MBYour homepage downloads 5.1 MB on a phone, 604 KiB of it images (12%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
bf-menu-banner-en-mobile-2x.png 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).
1 image below the first screen load straight away
1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.3 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
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (5 elements)
Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.
39 images without alt text
39 images have no alt text, which hurts accessibility and image search.
Contentinfo landmark should not be contained in another landmark (2 elements)
Contentinfo landmark should not be contained in another landmark: 2 elements on the page fail 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.
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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“FREEZING DEALS ALL MONTH.UP TO 50% OFF.”, “FREEZING DEALS ALL MONTH.1+1 FREE.” and “black friday IS HERE. UP TO 50% OFF.”). 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.
132 internal links, 8 external
The homepage links to 132 pages on honeybalm.com and 8 external pages.
5 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Honeybalm lip Care: natural beeswax + propolis, no PFAS or paraffin, 100% cruelty-free. Instant hydration and playful f…”.
Title: 42 characters
Your title is a healthy 42 characters: “Joyful & Cruelty-Free Lip Care | Honeybalm”.
Canonical URL set
The canonical URL is https://honeybalm.com/.
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://honeybalm.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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,620 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://honeybalm.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://honeybalm.com/pages/rewards and https://honeybalm.com/collections/limited-editions have 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 41 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
6 broken images
6 images failed to load on a phone, for example https://files.alia-prod.com/2834/509ad2d81aa68189.webp.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “window.Shopify.customerPrivacy.subscribe is not a function”.
2 checks passed
Tap targets are thumb-sized
36 of 40 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 561 words of copy
The homepage carries about 561 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BLACK FRIDAY”.
20 calls to action
The homepage has 20 calls to action, for example “Contact us”, “Shop” and “Shop Black Friday”.
25 short forms
25 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 27 testimonial or review blocks, a star rating and “600,000+ customers”.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and PostHog.
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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
54 other companies contacted
Loading the homepage contacts 54 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 honeybalm.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Triplewhale · Klaviyo Email Marketing Sms · Trackbee Connect · Loyalty Rewards And Referrals · Gdpr Cookie Consent · Applovin Shop Integration · Pixiehog · Upcart · 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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar | PostHog | 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 19 issues on honeybalm.com, including 1 speed issue, 3 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.