trygulabo.com — Website Report
Scored 63/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
trygulabo.com scored 63. Addressing the 23 listed issues could raise its estimated score to 90.
Quick wins
~164 min total fix timehttps://trygulabo.com/ · 2026-03-27
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://trygulabo.com Your site scores 63/100 overall, but AI engines may be missing you. Your AI Search Readiness is 60/100, and AI Citability is 24/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 2 critical issues and 13 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 Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. QUICK WINS (Warnings): 1. No FAQ section found — 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. 2. Missing X-Content-Type-Options header — Set X-Content-Type-Options: nosniff to prevent MIME-type s
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 Search Readiness
Technical and content signals that affect whether AI systems can access, understand, and reuse your page
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>Your page relies on plain text without lists, tables, or comparison charts. AI assistants extract and cite structured content (bullet points, comparison tables, step-by-step lists) far more accurately than long paragraphs.
How does AI see Trygulabo?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Trygulabo. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
SEO & Technical Issues (19)
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=()' }Missing og:title, og:description, 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">Add a canonical link to prevent duplicate content issues in search engines.
<link rel="canonical" href="https://yoursite.com/current-page">Add H2 subheadings to organize your content. Good heading hierarchy helps search engines understand your page structure.
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 page loads 11 external JavaScript files. Consider bundling some together and deferring non-critical scripts.
1 script without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Add JSON-LD structured data (Schema.org) to help search engines understand your content and earn rich snippets in search results.
Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">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>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
63
Now
90
Estimated potential
+27 points estimated improvement from addressing 23 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
Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.
Security score: 20/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.