loxenpearl.com — Website Report
Scored 47/100 · Scanned with Foglift
Fixing "Missing HSTS header" would move loxenpearl.com from 47 to 67.
Quick wins
~106 min total fix timehttps://loxenpearl.com/ · 4/30/2026, 12:09:16 AM
Scanned with Foglift · SEO + AI Visibility analysis
AI Search Readiness Risk
Your AI Readiness score of 47/100 means AI assistants like ChatGPT and Perplexity may not recommend your site. Monitor your AI visibility →
AI Action Plan
Website Analysis for https://loxenpearl.com/ Your site scores 47/100, but AI search engines can barely find you. AI Visibility: 29/100. When customers ask ChatGPT or Perplexity about your industry, you're likely not in the answer. We found 6 critical issues and 9 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. 3. Missing meta description — No meta description found. Search engines use this as the snippet in results. Add one for better CTR. 4. Missing H1 heading — Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility. 5. 17 external scripts loaded — Your page loads 17 external JavaScript files. Each requires a network r
14 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
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>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 Loxenpearl?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Loxenpearl
SEO & Technical Issues (16)
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'" }No meta description found. Search engines use this as the snippet in results. Add one for better CTR.
<meta name="description" content="Clear, compelling description of your page in 120-160 characters. Include your main keyword naturally.">Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility.
<h1>Your Main Page Heading</h1>
<!-- Only use one H1 per page. Make it descriptive and include your target keyword. -->Your page loads 17 external JavaScript files. Each requires a network request. Bundle scripts and defer non-critical ones to improve load time.
17 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
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=()' }Missing 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">Server responded in 1.5s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 201KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Loading 29 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
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 <link rel='preconnect'> for critical third-party domains to reduce connection setup time.
<!-- Add to <head> for your critical third-party domains -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://cdn.example.com">Your Potential Score
47
Now
77
Potential
+30 points possible by fixing 17 issues
That moves you from F to C — above average
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.