mutua.es — Website Report
Scored 59/100 · Scanned with Foglift
mutua.es scored 59. One fix would take it to 79.
Quick wins
~141 min total fix timehttps://mutua.es/ · 2026-05-15
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://Mutua.es Your site scores 59/100 overall, but AI engines may be missing you. Your AI Visibility is 64/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 5 critical issues and 10 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 6 AI crawlers (GPTBot, ChatGPT-User, Claude-Web...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. 12 images missing alt text — Found 12 of 131 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 4. Zooming is disabled — Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content. 5. 9 render-blocking scripts — 9 scripts without async o
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
Your site blocks 6 AI crawlers (GPTBot, ChatGPT-User, Claude-Web...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /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>How does AI see Mutua?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Mutua
SEO & Technical Issues (17)
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'" }Found 12 of 131 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
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 -->9 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
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 73 characters. Keep it under 60 for best display in search results.
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">12 of 131 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 H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.
Your HTML is 274KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
131 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
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 <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 110 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
59
Now
78
Potential
+19 points possible by fixing 19 issues
That moves you from D 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
Not AI-ready — ChatGPT, Perplexity, and Google AI Overviews likely cannot cite your site. You're invisible to the fastest-growing search channel.
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.