lucybalu.ch website review

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

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

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

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

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

About 566 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

11 KiB could be saved by minifying CSS.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

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.

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.

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

Real visitors wait 814 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LucyBalu Moderne Katzenmöbel - SWING Katzenhängematte im Mo…”.

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

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

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

Your homepage downloads 3.2 MB in 280 requests on a phone: scripts 1.6 MB (93), other files 1,018 KiB (135) and images 254 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

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

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (15 elements).

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 222 pages on lucybalu.ch and 7 external pages.

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.

https://lucybalu.com/en/collections/shop, https://lucybalu.com/en/collections/cat-furniture, https://lucybalu.com/en/collections/cat-wall, https://lucybalu.com/en/collections/kratzmoebel, https://lucybalu.com/en/collections/schlafplatz and https://lucybalu.com/en/collections/futterplatz-katzennapf have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://lucybalu.com/en?shpxid=e2c8f729-cd7b-4bfa-a59c-6d3fba090d6d.

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

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

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