mybacs.com website review

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

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

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

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

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

Shopify costs a phone 586 ms of main-thread work and 1.2 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 costs a phone 537 ms of main-thread work and 704 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.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

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

The page has 2,476 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 193 ms of main-thread work and 341 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.

49 KiB could be saved by minifying JavaScript.

About 32 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.

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

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need.

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.

4 KiB could be saved by minifying CSS.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mybacs loyalty banner mobile”.

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

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 159 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 508 requests on a phone: scripts 3.1 MB (220), other files 1.4 MB (175) and images 329 KiB (34). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

12 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 69 characters, so Google will cut it off around 60: “mybacs® - hochwertigen Nahrungsergänzungsmittel für das Darmmikrobiom”.

There are 2 <h1> headlines (“” and “DEINE GESUNDHEIT, DEINE ROUTINE”). One clear main headline is easier for people and search engines.

The homepage links to 85 pages on mybacs.com and 15 external pages.

https://mybacs.com/pages/womens-line, https://mybacs.com/pages/bestseller-page, https://mybacs.com/pages/refer-a-friend, https://mybacs.com/pages/rewards-portal, https://mybacs.com/pages/quiz and https://mybacs.com/pages/help-center have no meta description, so Google writes the search snippet from whatever text it finds.

https://mybacs.com/pages/womens-line, https://mybacs.com/collections/mybacs-produkte, https://mybacs.com/pages/bestseller-page, https://mybacs.com/pages/refer-a-friend, https://mybacs.com/pages/rewards-portal and https://mybacs.com/collections/mybacs-produkte-by-goal and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 24 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=355039361&tm=gtm002&Ver=2&mid=573dbf96-e91b-4724-84fd-6d189c11f1bc&bo=1&sid=86afe4b0db2d11f1a6c85b84752f16a3&vid=86b03230db2d11f1a4a063ed31927270&vids=1&msclkid=N&gtm_.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 359 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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 31 cookies (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 66 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.