felicialewisgroup.com — Website Report
Scored 56/100 · Scanned with Foglift
felicialewisgroup.com scored 56. One fix would take it to 76.
Quick wins
~124 min total fix timehttps://felicialewisgroup.com/blog/how-do-carmel-valley-homeowners-hire-a-realtor-they-trust · 2026-07-15
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://felicialewisgroup.com/blog/how-do-carmel-valley-homeowners-hire-a-realtor-they-trust Your site scores 56/100 overall, but AI engines may be missing you. Your AI Visibility is 69/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. Missing X-Content-Type-Options header — Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing. 2. Missing X-Frame-Options header — Set X-Frame-Options to prevent clickjacking attacks. 3. Missing Referrer Policy header — Add a Referrer-Policy header to control information leakage. 4. Missing Permissions Policy header — Add a Permissions-Poli
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
How does AI see Felicialewisgroup?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Felicialewisgroup
Issues Found (19)
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-Content-Type-Options: nosniff to prevent MIME-type sniffing.
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }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=()' }Add a lang attribute to your <html> tag (e.g., lang="en"). This helps search engines and screen readers understand your content's language.
<html lang="en">
<!-- For other languages: lang="es", lang="fr", lang="de", lang="ja", etc. -->Found 3 of 11 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
3 of 11 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.
Server responded in 1.1s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 402KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Your page loads 11 scripts from external domains. Consider auditing trackers and widgets and deferring non-critical ones.
2 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
7 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
<h1>Page Title</h1>
<p>Your primary content here...</p>
</main>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 32 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
56
Now
85
Potential
+29 points possible by fixing 19 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: 0/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.
Score of 0 means your site has no security headers at all. Browsers may show security warnings to visitors.