Website review, no card needed
honeybalm.se website review
Visit site (opens in a new tab)Reviewed 16 November 202642 issues · 85 checks
This review found 42 issues worth fixing on honeybalm.se, 12 of them high impact, across 85 checks. The most urgent: avoid multiple page redirects. 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- #55,333 of 123,845 reviewed websitesbeats 50%
- #36,393 of 69,695 online storesbeats 42%
- #34,868 of 63,403 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 117 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 106 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 133 ms |
| Sep 19, 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
Speed
Avoid multiple page redirects
3.6 sThe page goes through 2 redirects before it starts loading, costing about 3.6 s. Link and advertise the final URL directly.
Render-blocking requests
1.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 10.3 s
A phone's processor spends 10.3 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 (posthog.com, alia-prod.com and Google Tag Manager and others), adding 5.1 MB and 2.4 s of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
905 KiBAbout 905 KiB of JavaScript is downloaded but never used on this page.
posthog.com adds 726 ms
726 msposthog.com costs a phone 726 ms of main-thread work and 212 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.
alia-prod.com adds 580 ms
580 msalia-prod.com costs a phone 580 ms of main-thread work and 541 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.
Use efficient cache lifetimes
581 KiB20 files are served with short cache lifetimes, so returning visitors download them again (581 KiB).
honeybalm.eu adds 215 ms
215 mshoneybalm.eu costs a phone 215 ms of main-thread work and 2.5 MB 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.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 733 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
353 KiB12 images could be 353 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 296 ms. During a long task the page ignores taps.
Shopify adds 191 ms
191 msShopify costs a phone 191 ms of main-thread work and 538 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,952 HTML elements
The page has 1,952 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
150 msThe HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need.
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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Time to Interactive: 28.5 s
28.5 sThe page becomes fully interactive after 28.5 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK FRIDAY IS HERE. UP TO 50% OFF.”.
Real-user INP: 285 ms
285 msReal visitors wait 285 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 462 ms
462 msScripts block taps and scrolling for 462 ms in total while the page loads. Good is under 200 ms.
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) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 127 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 532 ms
532 msReal visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 689 requests
6.3 MBYour homepage downloads 6.3 MB in 689 requests on a phone: scripts 2.8 MB (202), other files 1.4 MB (297) and images 1.0 MB (148). 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.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 214.5 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
23 text elements with low contrast
23 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.
101 images without alt text
101 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Läppbalsam med smaksättning | Honeybalm Sverige – Honeybalm Sweden”.
2 H1 headlines
There are 2 <h1> headlines (“.cls-1 { fill: #000; stroke-width: 0px; }” and “Try-out box”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Product: image is not an absolute URL ("https:files/Tryout_1.webp")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
146 internal links, 7 external
The homepage links to 146 pages on honeybalm.se and 7 external pages.
4 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Hos Honeybalm hittar du läppbalsam med utsökta smaker! Säg hejdå till torra läppar och upplev kvaliteten hos naturliga …”.
Canonical URL set
The canonical URL is https://honeybalm.se/.
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.se/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,516 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://honeybalm.se/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 59 found) and read each the way a search engine does.
1 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Best practices
4 JavaScript errors while loading
4 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 41 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 593 words of copy
The homepage carries about 593 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BLACK FRIDAY” and “Shop all products”.
4 calls to action
The homepage has 4 calls to action, for example “Try-out box”, “SPF Try-out box” and “Try-out box 53% Rabatt”.
33 short forms
33 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 42 testimonial or review blocks and 13 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and PostHog.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 4 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.
41 other companies contacted
Loading the homepage contacts 41 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.se, 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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Klaviyo Email Marketing Sms · Trackbee Connect · Loyalty Rewards And Referrals · Gdpr Cookie Consent · 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
- Framework
- Tailwind CSS
- 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 42 issues on honeybalm.se, including 25 speed issues and 5 SEO issues. 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.