elternforen.com website review

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

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

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

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

About 31 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.

1 third-party service load with your homepage (wum.rocks), adding 61 KiB and 133 ms of main-thread time.

1 long task block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website nutzt Cookies und vergleichbare Funktionen zu…”. Most of its time is element render delay (2.0 s).

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

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

3 images 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 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 link inside paragraphs relies on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 336 pages on elternforen.com and 15 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.

There is no https://www.elternforen.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.elternforen.com/whats-new/posts and https://www.elternforen.com/whats-new/latest-activity are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.elternforen.com/whats-new/posts, https://www.elternforen.com/whats-new, https://www.elternforen.com/featured, https://www.elternforen.com/whats-new/latest-activity and https://www.elternforen.com/Blog have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.elternforen.com/threads/fkk-familie-stellt-sich-vor.43902/post-806954, whose canonical is https://www.elternforen.com/threads/fkk-familie-stellt-sich-vor.43902/page-3. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.elternforen.com/Blog has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.elternforen.com/featured 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 1 cookie (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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.