← Back to Home

familienwecker.de SEO Analysis

familienwecker.de scores 82/100 for SEO, 62/100 for performance, and 90/100 for AI crawler readability as of Apr 18, 2026.

https://familienwecker.de
15 checks
25 issues
Apr 18, 2026
https://familienwecker.de
Desktop preview
Desktop
Mobile preview
Mobile
Score Analysis
LIVE
84OF 100
Needs Work
82
SEO
62
Perf
90
AI
Page Title

FamWake – Die smarte Familienwecker & Bad-Planer App

Google Search Preview|How your page appears in search results
SERP Score
0/ 100
Good
familienwecker.de
https://familienwecker.de
FamWake – Die smarte Familienwecker & Bad-Planer App
Schluss mit dem Chaos am Morgen! FamWake koordiniert Bad-Zeiten, Frühstück und Aufstehen für deine ganze Familie – automatisch und stressfrei.
Snippet Quality
Title Length52 chars
030–60 optimal90
Description Length142 chars
070–160 optimal240
Power Word
CTA
URL Readable
HTTPS
No Truncation
Recommendations2 found
infoTitle lacks CTR-boosting power words
Consider adding words like "free", "guide", "best" to improve click-through rate
infoMeta description lacks a call-to-action
Add action verbs like "Learn", "Discover" to encourage clicks
Performance Report|Google PageSpeed Insights
Lighthouse v13.0.1Apr 18, 2026, 01:45 PM
Status200OK
Load Time0.19sFAST
HTML Size71 KBOK
CompressionGZIPON
HTTPSSecureSECURE
Render-Block3 scriptsFOUND
0/ 100
Needs Improvement
LCPPOOR
8.1 s
Largest Contentful Paint
FCPPOOR
5.1 s
First Contentful Paint
TBTGOOD
0 ms
Total Blocking Time
CLSGOOD
0
Cumulative Layout Shift
SINEEDS WORK
5.4 s
Speed Index
TTFBGOOD
Root document took 10 ms
Time to First Byte
FIDGOOD
50 ms
First Input Delay
Page Load FilmstripVisual timeline of how your page renders
Frame at 0.4s
0.4s
Frame at 0.8s
0.8s
Frame at 1.1s
1.1s
Frame at 1.5s
1.5s
Frame at 1.9s
1.9s
Frame at 2.3s
2.3s
Frame at 2.6s
2.6s
Frame at 3.0s
3.0s
Issues Found10 found
criticalLargest Contentful Paint: 8.1 s (poor)high
How to fixOptimize images, preload LCP element, reduce server response time. Target < 2.5s
What this meansLCP measures when the largest visible element finishes rendering.
SEO ImpactSlow LCP increases bounce rate and hurts Core Web Vitals ranking signal.
warningFirst Contentful Paint: 5.1 s (poor)medium
How to fixReduce server response time, eliminate render-blocking resources, inline critical CSS. Target < 1.8s
What this meansFCP measures when the first piece of content is rendered on screen.
SEO ImpactSlow FCP means users see a blank page for too long.
warningAvoid multiple page redirects - Est savings of 1,520 ms (potential savings: 1515ms)
How to fixRedirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
warningReduce unused JavaScript - Est savings of 184 KiB (potential savings: 1050ms) / 184 KB
How to fixReduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
warningMinify CSS - Est savings of 2 KiB (potential savings: 150ms) / 2 KB
How to fixMinifying CSS files can reduce network payload sizes. Learn how to minify CSS.
warningMinify JavaScript - Est savings of 12 KiB (potential savings: 12 KB)
How to fixMinifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
infoAvoid enormous network payloads - Total size was 5,477 KiB
How to fixLarge network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
infoAvoid large layout shifts
How to fixThese are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due …
infoImage elements do not have explicit `width` and `height`
How to fixSet an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
warning3 render-blocking scripts in <head>
How to fixAdd async or defer to scripts
OpportunitiesPotential savings to improve load time
Avoid multiple page redirectsEst savings of 1,520 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
1.5s potential savings
Reduce unused JavaScriptEst savings of 184 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
1.1s potential savings 184 KB transferable
Minify CSSEst savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
0.1s potential savings 2 KB transferable
Minify JavaScriptEst savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
12 KB transferable
Avoid enormous network payloadsTotal size was 5,477 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
DiagnosticsAdditional performance insights
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due …
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Forced reflow
Server Backend Latencies
Screenshot Thumbnails
Script Treemap Data
Total Blocking Time
Tasks
Layout shift culprits
Optimize viewport for mobile
Legacy JavaScript
Duplicated JavaScript
JavaScript execution time
Cumulative Layout Shift
Max Potential First Input Delay
Minimizes main-thread work
Diagnostics
Final Screenshot
Optimize DOM size
Avoid long main-thread tasks
Document request latency
Metrics
Network Requests
Resources Summary
LCP breakdown
Initial server response time was short
Font display
3rd parties
Network Round Trip Times
Reduce unused CSS
Heading Structure|Content hierarchy and heading tags
100 / 100
H1
1
ideal: 1
H2
8
ideal: 2+
H3
20
ideal: optional
H4
0
ideal: optional
Heading Hierarchy29 total
H1FamWake Familien-Wecker
H2✨ Euer Morgen als perfekt eingespieltes Team
H2📱 Ein Blick in die App
H2🚀 Die Highlights der App
H2🚀 Demnächst verfügbar
H2💬 Was Familien sagen
H2🤔 Häufig gestellte Fragen (FAQ)
H2Mach dem morgendlichen Chaos ein Ende.
H2👋 Hallo, ich bin Daniel!
H3Einladung per Klick
H3Fairer Bad-Check
H3Synchronisiertes Aufstehen
H3Stressfreie Struktur
H3Flexibler Drag & Drop Plan
H3Maximale Schlafzeit
H3Kein Bad-Stau mehr
H3Absolut zuverlässig
H3📅 Wochentag-Profile
H3📋 Alles im Blick
H3🧩 Mitdenkende Weck-Logik
H3👁️ Live-Status für alle
H3☀️ "Bin schon wach"
H3💤 Smarter Snooze
H3💬 Konflikt-Diagnose
H3🔑 Sicherer Login
+4 more headings
Structured Data|Schema markup, Open Graph and Twitter Cards
100 / 100
JSON-LD Schema
2 found
SoftwareApplication, FAQPage
Open Graph
6 tags
Twitter Cards
4 tags
Microdata
Not found
Schema Types Detected
SoftwareApplicationFAQPage
Open Graph Tags
og:titleFamWake – Dein smarter Familien-Fahrplan
og:descriptionKeine Schlange vor dem Bad, kein Stress – nur perfekt abgestimmte Routinen für die ganze Familie. Jetzt kostenlos im Google Play Store!
og:imagehttps://familienwecker.de/images/og-image-de.jpg
og:urlhttps://familienwecker.de/
og:typewebsite
og:site_nameFamWake
missing: og:locale
Image Optimization|Alt text, lazy loading and dimensions
85 / 100
Total Images
9
Missing Alt Text
0
100% have alt text
Missing Dimensions
9
Lazy Loaded
67%
6 of 9 images
Recommendations1
info9 images without explicit dimensions
Add width/height to prevent layout shifts (CLS)
Indexability|Robots, canonical and sitemap
100 / 100
Canonical URL
Set
https://familienwecker.de/
Noindex
Allowed
meta robots: index, follow
Robots.txt
Found
Sitemap
Found
https://familienwecker.de/sitemap.xml
Crawl Directives
Meta Robotsindex, follow
X-Robots-TagNot set
GooglebotNot set
NofollowNo — links followed
Canonicalhttps://familienwecker.de/
Page URLhttps://familienwecker.de
Content Structure|Content quality and semantic HTML
95 / 100
Word Count
4560
Paragraphs
49
All good length
Lists
0
Words per Heading
157
Ideal: 100-300
Title vs H1 Alignment5710% similar
TITLE TAG
FamWake – Die smarte Familienwecker & Bad-Planer App
H1 TAG
FamWake Familien-Wecker
Semantic HTML Elements9 sections
<main>
<article>
<nav>
<header>
<footer>
Recommendations1
infoH2 headings don't relate to the main H1 topic
Ensure H2s support the main topic for better coherence
AI Readability|How easily AI models can process your content
90 / 100
51Flesch
Reading Level
Fairly Easy
Moderately complex
Total Words
4560
Sentences
397
Avg Sentence Length
12 words
Vocabulary Richness
38%
1734 unique words
Opening Paragraph8 words
Dein smarter Fahrplan für den stressfreien Morgen.
Recommendations1
infoFirst paragraph is too short for AI summarization
Make the first paragraph a comprehensive summary (30-50 words)
AI Citation Potential|How likely AI will quote your content
85 / 100
Named Entities
387
849% density
FAQ Patterns
0
FAQ Schema found
Citations
11
Lists & Tables
0 items, 0 tables
Top Named Entities
App28FamWake26Konzept13Idee12Familienwecker12Familie10Wecker9Morgen7Algorithmus7Bad7Die App7Store6Tag6Familien6Zeit5Design5Badezimmer5Play5Klick4Ein4
Quotable Content
FamWake
FamWake
FamWake
Recommendations2
warningNo FAQ-style content detected
Add question-and-answer sections with heading questions (H2/H3 with "?")
infoNo lists or tables - content may be hard for AI to structure
Break information into bullet lists, numbered steps, or comparison tables
Content Freshness|Date signals and cache headers
85 / 100
Date Signals
Found
Search engines can determine content freshness
Cache Control
Not set
ETag
Set
Date Signals
Last-Modified HeaderApril 18, 2026
Published DateNot found
Modified DateNot found
Recommendations1
warningNo datePublished or dateModified in structured data
Add datePublished and dateModified to your JSON-LD schema.
Security Headers|HTTP security headers analysis
25 / 100
Content-Security-Policy
Prevents XSS and injection attacks
MISSING
Strict-Transport-Security
Forces HTTPS connections
MISSING
X-Frame-Options
Prevents clickjacking attacks
MISSING
X-Content-Type-Options
Prevents MIME-type sniffing
MISSING
Referrer-Policy
Controls referrer information
MISSING
Permissions-Policy
Controls browser features
MISSING
Recommendations6
criticalMissing Content-Security-Policy header
Add Content-Security-Policy header to prevent XSS and data injection attacks
warningMissing Strict-Transport-Security header
Add Strict-Transport-Security header with max-age of at least 31536000
warningMissing X-Frame-Options header
Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
warningMissing X-Content-Type-Options header
Add X-Content-Type-Options: nosniff to prevent MIME-type sniffing
Trust Signals|Essential trust-building pages
90 / 100
Contact Page
MISSING
A contact page builds trust with visitors and search engines
About Page
MISSING
An about page establishes credibility and expertise
Privacy Policy
FOUND
Required for compliance and builds user trust
privacy-policy.html
Terms of Service
FOUND
Protects both the site owner and users
terms.html
Recommendations1
infoMissing trust pages: contact, about
Consider adding links to: contact, about
Tech Stack|2 technologies detected
60 / 100
Frameworks2
🛠️
Ember.js
Script signature
javascript
🛠️
Fetch API
Script signature
javascript