lunasol-orthos.de — Website Report
Scored 69/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
lunasol-orthos.de scored 69. Addressing the 14 listed issues could raise its estimated score to 83.
Quick wins
~130 min total fix timehttps://lunasol-orthos.de/ · 2026-09-10
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://lunasol-orthos.de/ Site Technical Health: 69/100. AI Readiness is 51/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 4 critical issues and 7 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks.
2. 11 images missing alt text — Found 11 of 20 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 3. 55% of images lack alt text — 11 of 20 images have no alt attribute. Screen readers cannot describe these images to visually impaired users. 4. 13 render-blocking scripts — 13 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. No FAQ section found
10 more critical fixes + quick wins in your full report
Create a free account to save this audit and unlock the complete action plan.
Save and unlock my full reportFree account. No credit card required.
Share This Report
Send this scan to a teammate or contact. The shareable link includes all scores and issues.
AI Readiness
Technical and authority signals that support AI systems in accessing, understanding, and reusing your content
Technical Issues
A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What does your company do?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We provide [your service]. Our solution helps..."
}
}]
}
</script>How does AI see Lunasol-orthos?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Lunasol-orthos. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
SEO & Technical Issues (13)
Add a Content-Security-Policy header to prevent XSS and injection attacks.
# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;
# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"
# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }Found 11 of 20 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
11 of 20 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
13 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Missing og:title, og:description, og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">Found 3 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.
Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.
Loading 6 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
8 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.
<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
Skip to main content
</a>
<!-- Add id to your main content area -->
<main id="main-content">
...
</main>Found 20 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
69
Now
83
Estimated potential
+14 points estimated improvement from addressing 14 listed issues
Estimate based on the measured category scores and the issues listed in this audit.
Track your AI visibility over time
AI Visibility Monitoring
Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.
Competitor Tracking
Compare your AI visibility against competitors. Know when they overtake you.
Weekly Digest
Get AI-generated insights emailed every Monday with action items.
Weekly Perplexity while active · No credit card required
Compare paid plans — from $49/moIndustry Benchmark
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.