cantonsdelest.com — Website Report
Scored 45/100 · Scanned with Foglift
Fixing "AI engines can't understand your business" would move cantonsdelest.com from 45 to 65.
Quick wins
~158 min total fix timehttps://cantonsdelest.com/ · 2026-06-16
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://cantonsdelest.com Your site scores 45/100 overall, but AI engines may be missing you. Your AI Visibility is 48/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 8 critical issues and 8 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI engines can't understand your business — Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.
2. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections. 3. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 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. 50 images missing alt text — Found 50 of 51 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (i
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
Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://yoursite.com",
"description": "Brief description of your business",
"sameAs": [
"https://twitter.com/yourhandle",
"https://linkedin.com/company/yourcompany"
]
}
</script>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 Cantonsdelest?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Cantonsdelest
SEO & Technical Issues (20)
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'" }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. -->Found 50 of 51 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
50 of 51 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.
<!-- Replace your viewport meta tag with this (allows zooming) -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Do NOT use: maximum-scale=1, user-scalable=no -->11 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=()' }Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
Server responded in 2.4s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
51 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add JSON-LD structured data (Schema.org) to help search engines understand your content and earn rich snippets in search results.
Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.
<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>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 22 elements with large inline styles. Move these to external CSS for better caching and maintainability.
Found 24 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
45
Now
67
Potential
+22 points possible by fixing 23 issues
That moves you from F to D — 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
Not AI-ready — ChatGPT, Perplexity, and Google AI Overviews likely cannot cite your site. You're invisible to the fastest-growing search channel.
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.