www.aginghealth.website — Website Report
Scored 59/100 · Scanned with Foglift
aginghealth.website scored 59. One fix would take it to 79.
Quick wins
~143 min total fix timehttps://www.aginghealth.website/ · 2026-06-19
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Search Readiness Risk
Your AI Readiness score of 43/100 means AI assistants like ChatGPT and Perplexity may not recommend your site. Monitor your AI visibility →
AI Action Plan
Website Analysis for https://www.aginghealth.website/ Your site scores 59/100 overall, but AI engines may be missing you. Your AI Visibility is 47/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 2 critical issues and 14 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. QUICK WINS (Warnings): 1. Structured data needs more detail — You have basic structured data, but it's missing the rich types that AI engines look for — like FAQ sections, how-to guides, or product info. Adding these helps AI assistants extract and cite your content more accurately. 2. No FAQ section found — AI assistants love Q&A content — it's the easiest format for them to e
15 more critical fixes + quick wins in your full report
Enter your email and we'll send the complete action plan to your inbox.
No spam. Just your report.
Share This Report
Send this scan to a teammate or contact. The shareable link includes all scores and issues.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
Technical Issues
You have basic structured data, but it's missing the rich types that AI engines look for — like FAQ sections, how-to guides, or product info. Adding these helps AI assistants extract and cite your content more accurately.
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
<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>Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"sameAs": [
"https://twitter.com/yourhandle",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourorg"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}
</script>Pro tip: The biggest drivers of AI visibility are brand mentions and domain authority — not just technical setup. Set up AI visibility monitoring →
How does AI see Aginghealth?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Aginghealth
SEO & Technical Issues (15)
Enable HTTP Strict Transport Security to force HTTPS connections.
# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }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'" }Set X-Frame-Options to prevent clickjacking attacks.
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }Add a Referrer-Policy header to control information leakage.
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }Add a Permissions-Policy header to control browser feature access.
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }Found 3 of 6 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
3 of 6 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
Heading hierarchy jumps from H1 to H3. 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.
Server responded in 1.5s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 215KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
3 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
6 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
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>Your Potential Score
59
Now
81
Potential
+22 points possible by fixing 18 issues
That moves you from D to B — top 15% of all websites
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Free tier available · No credit card required
Industry Benchmark
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
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.
Security score: 15/100
Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.