mybacs.ch website review

18 images could be 1,007 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Shopify, hive.app and Klaviyo and others), adding 1.2 MB and 564 ms of main-thread time.

About 516 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Shopify costs a phone 107 ms of main-thread work and 308 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.

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

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

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

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

21 KiB JavaScript is shipped twice across bundles.

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

12 KiB could be saved by minifying JavaScript.

About 12 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 10.4 MB in 331 requests on a phone: media 6.1 MB (1), scripts 1.7 MB (116) and images 1.3 MB (38). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example DE___Collection_Page_-_Radiant_Glow.jpg at 1,620 px wide, shown at 280 px. Resized copies would save about 285 KiB.

1 image (241 KiB) is 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.

By the Sustainable Web Design model, a visit to your homepage emits about 2.94 g of CO₂e: 352.8 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.

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.

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

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

Alternative text of images should not be repeated as text: 8 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.

Elements with visible text labels do not have matching accessible names. (1 element).

Your <h1> is empty.

The homepage links to 90 pages on mybacs.ch and 9 external pages.

https://mybacs.ch/collections/mybacs-produkte, https://mybacs.ch/products/dailybacs-women and https://mybacs.ch/pages/widerrufsformular are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://mybacs.ch/pages/herbst-sale, https://mybacs.ch/collections/mybacs-produkte-by-goal, https://mybacs.ch/pages/bestseller-page, https://mybacs.ch/pages/quiz, https://mybacs.ch/pages/about-us and https://mybacs.ch/pages/ingredients and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mybacs.ch/pages/herbst-sale, https://mybacs.ch/pages/bestseller-page and https://mybacs.ch/pages/womens-line have no <h1> headline, so visitors and search engines get no clear main topic.

https://mybacs.ch/collections/mybacs-produkte and https://mybacs.ch/pages/bestseller-page took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.

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

Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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