mybeebalmco.de website review

About 530 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

8 files are served with short cache lifetimes, so returning visitors download them again (180 KiB).

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.8 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Shopify and others), adding 1.2 MB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 571 ms of main-thread work and 505 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.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

9 long tasks block the main thread while loading, the longest for 309 ms. During a long task the page ignores taps.

8 images could be 285 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

12 KiB could be saved by minifying CSS.

About 13 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 15.9 s. Good is under 3.8 s.

Visually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 583 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

46 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.4 MB in 196 requests on a phone: scripts 1.3 MB (56), images 614 KiB (38) and fonts 244 KiB (24). Under 2 MB keeps phones on slow connections fast.

balm_360x.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 is downloaded at several times the size a phone draws it, for example 7S3A7109_1-min.jpg at 3,844 px wide, shown at 162 px. Resized copies would save about 231 KiB.

4 images further down the page (313 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 83.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

2 buttons have no accessible name, so screen readers announce just “button”.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 11 characters: “Bee Balm DE”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 25 pages on mybeebalmco.de and 11 external pages.

Your homepage links to https://mybeebalmco.de/apps/track123, https://mybeebalmco.de/pages/contact-us, https://mybeebalmco.de/collections/bee-balms, https://mybeebalmco.de/collections/skin-care, https://mybeebalmco.de/pages/bundle-and-save and https://mybeebalmco.de/pages/reviews, which answer with an error. Visitors hit a dead end and search engines drop them.

https://mybeebalmco.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://mybeebalmco.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://mybeebalmco.de/collections/frontpage, https://mybeebalmco.de/collections/all, https://mybeebalmco.de/pages/contact, https://mybeebalmco.de/pages/abonnement-verwalten and https://mybeebalmco.de/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://mybeebalmco.de/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://mybeebalmco.de/pages/zufriedene-kunden has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97043661&tm=shpfy_ui&Ver=2&mid=69010daf-45c1-4713-8e4e-561e688ff311&bo=1&sid=26fc74d0daf411f1a92233bd4f7d4d1a&vid=26fc9b90daf411f1b081f578a183728c&vids=1&msclkid=N&pi=.

6 errors were logged to the browser console while the page loaded, for example “GetRevenueValue is not defined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 745 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.

Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.