www.alanxai.com

Mostrando los 8 problemas principales. La auditoría completa con correcciones a nivel de código está disponible en el plan gratuito.

• 01
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "film" — 22 times (4.1%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Regístrate para ver cómo corregir esto
• 02
  FAIL · ai-readiness

  Structured Data Completeness

  No structured data (JSON-LD / Schema.org) found. AI search engines rely heavily on structured data to understand and cite content. Without it, your pages are much less likely to appear in AI-generated answers.
  Regístrate para ver cómo corregir esto
• 03
  WARN · ai-readiness

  E-E-A-T Signals

  2/4 E-E-A-T signals found. Present: About/Team page link, Contact information. Missing: Author attribution, Publication/modification date. AI search engines prioritize content from sources that demonstrate clear authorship, timeliness, and trustworthiness.
  Regístrate para ver cómo corregir esto
• 04
  WARN · onpage

  Meta Description

  The meta description is too short (114 chars). The recommended length is between 120 and 160 characters. A short description does not fully utilize the available snippet space in search results.
  Regístrate para ver cómo corregir esto
• 05
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 320 ms (0.32 sec). This is acceptable but there is room for improvement. The optimal value is less than 200 ms. A slow TTFB delays the start of page rendering.
  Regístrate para ver cómo corregir esto
• 06
  FAIL · performance

  HTTP Requests Count

  The page loads 42 external resources — this is too many (1 CSS, 19 JS, 15 images). A high number of HTTP requests critically slows down page loading, as browsers are limited to 6 simultaneous connections per domain. This negatively affects all performance metrics.
  Regístrate para ver cómo corregir esto
• 07
  FAIL · security

  Security Headers

  Only 1 out of 7 recommended security headers found. Missing: x-frame-options, x-content-type-options, content-security-policy, x-xss-protection, referrer-policy, permissions-policy. The site is vulnerable to multiple attack types, including XSS, clickjacking, and MIME-sniffing.
  Regístrate para ver cómo corregir esto
• 08
  FAIL · security

  Server Signature

  The Server header is present: "Vercel". Although the exact version is not revealed, minimizing server information is recommended. The X-Powered-By header reveals the framework in use: "Next.js". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Regístrate para ver cómo corregir esto