thesissbliss.com website review

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

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

38 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 1.4 MB and 786 ms of main-thread time.

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

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

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

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

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

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

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

18 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 13 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.

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

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

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. Most of its time is resource load delay (2.2 s).

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

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

Your homepage downloads 24.4 MB in 1,064 requests on a phone: images 21.2 MB (650), other files 1.4 MB (273) and scripts 1.4 MB (108). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 13 elements on the page fail this check, rated serious by axe-core.

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is 71 characters, so Google will cut it off around 60: “Personalisierter, handgefertigter Echtgoldschmuck – The SISS BLISS GmbH”.

Your meta description is 253 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 186 pages on thesissbliss.com and 0 external pages.

The HTML your server sends has 723 of the 2,402 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://thesissbliss.com/pages/showroom, https://thesissbliss.com/pages/bliss-bang-capital-fragebogen, https://thesissbliss.com/pages/sonderanfrage, https://thesissbliss.com/collections/alle-schmuckstucke, https://thesissbliss.com/collections/ringe and https://thesissbliss.com/pages/newsletter and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://thesissbliss.com/collections/muster-sale, https://thesissbliss.com/products/ringgroessenmesser, https://thesissbliss.com/products/gift-card, https://thesissbliss.com/collections/lifestyle-accessoires, https://thesissbliss.com/pages/newsletter and https://thesissbliss.com/pages/roadshow took over 3 s to send their HTML from our server.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 2,402 words of visible text.

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