Website review, no card needed

elternwissen.com logo

elternwissen.com website review

Visit site (opens in a new tab)Reviewed 11 November 202622 issues · 74 checks

This review found 22 issues worth fixing on elternwissen.com, 6 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sMay 23Nov 71.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
241 ms202 msMay 23Nov 7230 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026229 ms
May 30, 2026227 ms
Jun 6, 2026223 ms
Jun 13, 2026222 ms
Jun 20, 2026228 ms
Jun 27, 2026228 ms
Jul 4, 2026235 ms
Jul 11, 2026227 ms
Jul 18, 2026227 ms
Jul 25, 2026224 ms
Aug 1, 2026226 ms
Aug 8, 2026228 ms
Aug 15, 2026235 ms
Aug 22, 2026236 ms
Aug 29, 2026235 ms
Sep 5, 2026235 ms
Sep 12, 2026220 ms
Sep 19, 2026214 ms
Sep 26, 2026206 ms
Oct 3, 2026212 ms
Oct 10, 2026219 ms
Oct 17, 2026230 ms
Oct 24, 2026230 ms
Oct 31, 2026233 ms
Nov 7, 2026230 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of elternwissen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elternwissen.com at 0.4 s0.4 s
  2. elternwissen.com at 0.8 s0.8 s
  3. elternwissen.com at 1.1 s1.1 s
  4. elternwissen.com at 1.5 s1.5 s
  5. elternwissen.com at 1.9 s1.9 s
  6. elternwissen.com at 2.3 s2.3 s
  7. elternwissen.com at 2.6 s2.6 s
  8. elternwissen.com at 3.0 s3.0 s

Speed

6 to fix77
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 77

    77/100

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

  • Reduce unused JavaScript

    610 ms · 132 KiB

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

  • Use efficient cache lifetimes

    500 ms · 49 KiB

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

  • Improve image delivery

    300 ms · 92 KiB

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

  • Reduce unused CSS

    310 ms · 71 KiB

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

  • Legacy JavaScript

    150 ms · 43 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (ccm19.de and office.net), adding 78 KiB and 76 ms of main-thread time.

  • 1 long task on the main thread

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

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 181 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir, Elternwissen, ein Unternehmensbereich der VNR Verlag f…”.

  • Real-user INP: 228 ms

    228 ms

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

  • Real-user TTFB: 817 ms

    817 ms

    Real visitors wait 817 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0.034

    0.034

    The layout barely moves while loading (CLS 0.034, good is under 0.1).

  • Total Blocking Time: 15 ms

    15 ms

    Scripts block the page for only 15 ms while loading. Good is under 200 ms.

Images and page weight

100
  • 3 images in older formats

    3 images (132 KiB) are 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.

  • About 0.2 g of CO₂ per visit

    0.20 g

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

3 checks passed
  • Page weight: 730 KiB in 37 requests

    730 KiB

    Your homepage downloads 730 KiB in 37 requests on a phone: scripts 337 KiB (7), images 154 KiB (8) and stylesheets 102 KiB (12). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9293
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.elternwissen.de/sitemap_index.xml, so Google discovers your pages only by following links.

  • 263 internal links, 6 external

    The homepage links to 263 pages on elternwissen.com and 6 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Elternratgeber für 👶 Schwangerschaft, 🌱 Kindergesundheit, ✔️ Erziehung und erfolgreiches Lernen >> Jetzt informieren!”.

  • One H1 headline

    Your main headline reads: “Herzlich Willkommen bei Elternwissen!”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Elternwissen.com 👪 Ihr kompetenter Eltern-Ratgeber”.

  • Canonical URL set

    The canonical URL is https://www.elternwissen.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

    There is no https://www.elternwissen.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,068 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 6 pages slow to respond

    https://www.elternwissen.com/erziehung-entwicklung/baby-entwicklung/bobath-konzept-babyentwicklung-durch-gezielte-griffe-foerdern, https://www.elternwissen.com/erziehung-entwicklung/baby-entwicklung/wenn-kinder-schreien-bis-zur-bewusstlosigkeit-diese-tipps-helfen-bei-affektkraempfen, https://www.elternwissen.com/erziehung-entwicklung/kleinkind-entwicklung, https://www.elternwissen.com/erziehung-entwicklung/trotzphase, https://www.elternwissen.com/erziehung-entwicklung/kleinkind-entwicklung/laufen-lernen-so-unterstuetzen-sie-ihr-kind-bei-seiner-motorischen-entwicklung and https://www.elternwissen.com/erziehung-entwicklung/kleinkind-entwicklung/knick-senk-oder-spreizfuss-vermeiden-so-entwickeln-sich-die-fuesse-ihres-kindes-gesund took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    18 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No risk reducer

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

  • About 931 words of copy

    The homepage carries about 931 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Start in den Kindergarten” and “Shop”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • No consent tool detected

    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.

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at elternwissen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Hosting
CloudFront

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on elternwissen.com, including 14 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25