blossholm.de website review

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

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

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

8 third-party services load with your homepage (Shopify, alia-prod.com and Clarity and others), adding 2.6 MB and 1.6 s of main-thread time.

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

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

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

alia-prod.com costs a phone 343 ms of main-thread work and 333 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.

Clarity costs a phone 263 ms of main-thread work and 28 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.

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

rebuyengine.com costs a phone 163 ms of main-thread work and 331 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 69 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.

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

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

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

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

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

Your homepage downloads 10.7 MB in 485 requests on a phone: media 5.7 MB (2), images 1.8 MB (261) and scripts 1.6 MB (100). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ac.svg at 1,000 px wide, shown at 20 px. Resized copies would save about 121 KiB.

9 images further down the page (357 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 3.03 g of CO₂e: 363.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

26 images have no alt text, which hurts accessibility and image search.

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.

3 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. (1 element).

There are 3 <h1> headlines (“Blossholm.com”, “Black Friday Has Started” and “Black Friday”). One clear main headline is easier for people and search engines.

The homepage links to 93 pages on blossholm.de and 7 external pages.

Your homepage links to https://blossholm.com/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

https://blossholm.com/products/aurie-portable-table-lamp-linen-calacatta-viola-marble-us, https://blossholm.com/products/aurie-portable-table-lamp-linen-travertine-us and https://blossholm.com/products/aurie-portable-table-lamp-linen-white-marble all use the title “The Portable Auríe Table Lamp - Blossholm”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://blossholm.com/collections/lamps, https://blossholm.com/customer_authentication/redirect, https://blossholm.com/policies/contact-information, https://blossholm.com/policies/shipping-policy and https://blossholm.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://blossholm.com/products/aurie-portable-table-lamp-linen-calacatta-viola-marble-us, https://blossholm.com/products/aurie-portable-table-lamp-linen-travertine-us and https://blossholm.com/products/aurie-portable-table-lamp-linen-white-marble use the same meta description. A description written for each page earns more clicks.

https://blossholm.com/collections/sale-blossholm, https://blossholm.com/collections/lamps, https://blossholm.com/collections/black-friday, https://blossholm.com/collections/best-sellers, https://blossholm.com/customer_authentication/redirect and https://blossholm.com/pages/about-us and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

27 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

The homepage carries about 1,387 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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