jollein.de website review

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

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

8 third-party services load with your homepage (jollein.nl, Clarity and Cookie-Script.com and others), adding 1.4 MB and 1.2 s of main-thread time.

jollein.nl costs a phone 655 ms of main-thread work and 759 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 long tasks block the main thread while loading, the longest for 723 ms. During a long task the page ignores taps.

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

14 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

7 KiB could be saved by minifying JavaScript.

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 25.9 s. Good is under 3.8 s.

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

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

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

Real visitors wait 263 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 5.4 MB in 391 requests on a phone: images 2.4 MB (93), scripts 1.7 MB (112) and other files 925 KiB (162). Under 2 MB keeps phones on slow connections fast.

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

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

9 buttons have no accessible name, so screen readers announce just “button”.

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 7 characters: “Jollein”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (Brand and WebSite) but with 3 problems, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 134)”.

The homepage links to 380 pages on jollein.de and 16 external pages.

https://jollein.de/collections/pflege has no <h1> headline, so visitors and search engines get no clear main topic.

https://jollein.de/collections/wickelauflage took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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