cuesine.ca — Website Report
Scored 54/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
cuesine.ca scored 54. Addressing the 21 listed issues could raise its estimated score to 83.
Quick wins
~168 min total fix timehttps://cuesine.ca/ · 2026-09-09
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Search Readiness Risk
Your AI Readiness score of 48/100 identifies technical and content barriers that may make this page harder for AI systems to access, understand, or reuse. It does not show whether AI assistants recommend or cite your site. Check answer-level AI visibility →
AI Action Plan
Website Analysis for https://cuesine.ca/ Site Technical Health: 54/100. AI Readiness is 48/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 13 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections.
2. 67 images missing alt text — Found 67 of 100 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 3. 67% of images lack alt text — 67 of 100 images have no alt attribute. Screen readers cannot describe these images to visually impaired users. 4. 29 render-blocking scripts — 29 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. Structured data nee
16 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
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.
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>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 Free monitoring →
How does AI see Cuesine?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Cuesine. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
SEO & Technical Issues (18)
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' }Found 67 of 100 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
67 of 100 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
29 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=()' }Your title is 69 characters. Keep it under 60 for best display in search results.
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.1s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 327KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Loading 49 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
100 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.
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>Found 39 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
54
Now
83
Estimated potential
+29 points estimated improvement from addressing 21 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
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: 25/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.