regenbogenmamas.de website review

110 files are served with short cache lifetimes, so returning visitors download them again (19.2 MB).

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

About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

7 third-party services load with your homepage (Calendly, coredelivr.com and Stripe and others), adding 3.7 MB and 1.2 s of main-thread time.

Calendly costs a phone 757 ms of main-thread work and 3.2 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.

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

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

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

Stripe costs a phone 171 ms of main-thread work and 305 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.

37 KiB could be saved by minifying CSS.

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

1 image could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

10 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.

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

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

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

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

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

The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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 22.6 MB in 136 requests on a phone: media 16.2 MB (1), scripts 3.7 MB (60) and stylesheets 2.0 MB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example luma-pimentel-1vnB2l7j3bY-unsplash-web-1zu1.jpg at 1,280 px wide, shown at 312 px. Resized copies would save about 23 KiB.

1 image (49 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 6.39 g of CO₂e: 767.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

14 tap targets are too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 23 characters: “Start - Regenbogenmamas”. Between 30 and 65 characters leaves room to say what you do and for whom.

There is no robots.txt at regenbogenmamas.de/robots.txt, the first file search crawlers ask for.

The homepage links to 22 pages on regenbogenmamas.de and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://regenbogenmamas.de/regenbogenmamas-2-be has no <h1> headline, so visitors and search engines get no clear main topic.

https://regenbogenmamas.de/regenbogenmamas-2-be has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://regenbogenmamas.de/masterclass-in-vertrauen-durch-das-1-trimester and https://regenbogenmamas.de/podcast took over 3 s to send their HTML from our server.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

1 of 5 tappable elements near the top of the page is 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”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

Your longest form asks for 13 fields (6 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Hotjar (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 3 cookies, 1 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.