addlly.ai

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

• 01
  WARN · technical

  Robots.txt

  The robots.txt file was found but does not contain a Sitemap directive. The Sitemap directive helps search engine crawlers discover all pages on your website more efficiently.
  Regístrate para ver cómo corregir esto
• 02
  WARN · onpage

  Meta Title

  The <title> tag is long (67 chars). Google has no hard character limit, but SERPs truncate by pixel width (~600px on desktop, ~78px less on mobile). Wide letters (W, M, capitals) push the cutoff lower — 30–65 chars is the safe zone across Google + Bing + Yandex. Beyond ~70 chars, the tail keyword is invisible in classic SERPs (still cited fully by ChatGPT / Claude / Perplexity).
  Regístrate para ver cómo corregir esto
• 03
  FAIL · performance

  Page Size

  The total HTML page size is 1.38 MB, which significantly exceeds the recommended limit of 100 KB. Heavy pages load slowly, especially on mobile devices and slow internet connections. This negatively impacts Core Web Vitals and search rankings.
  Regístrate para ver cómo corregir esto
• 04
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 985 ms (0.98 sec). Google flags this as "needs improvement" (800 ms – 1.8 s per web.dev). LCP is bounded by TTFB, so reaching the "good LCP" 2.5s threshold becomes harder as TTFB grows.
  Regístrate para ver cómo corregir esto
• 05
  FAIL · performance

  Image Lazy Loading

  None of the 60 images on the page use lazy loading (loading="lazy"). All images are loaded simultaneously when the page opens, significantly slowing down initial load and consuming user bandwidth.
  Regístrate para ver cómo corregir esto
• 06
  FAIL · performance

  HTTP Requests Count

  The page loads 177 external resources — this is too many (0 CSS, 56 JS, 118 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 6 modern security headers found. Missing: x-frame-options, x-content-type-options, strict-transport-security, referrer-policy, permissions-policy. The site is exposed to XSS (no CSP), clickjacking (no X-Frame-Options / CSP frame-ancestors), MIME-sniffing (no X-Content-Type-Options), and HTTPS-stripping MITM (no HSTS). Mozilla Observatory grades sites with <4 headers as D or F.
  Regístrate para ver cómo corregir esto
• 08
  FAIL · ai-readiness

  Knowledge Panel Readiness

  Low knowledge-panel readiness — score 25/100. AI search engines and Google Knowledge Panel cannot confidently identify this brand. The cheapest, fastest fixes are: (1) add Organization JSON-LD with a sameAs chain (Wikipedia, Wikidata, LinkedIn, Crunchbase, GitHub, social), (2) make NAP (Name/Address/Phone) visible in the footer or contact page, (3) create a Wikidata entry (low notability bar), then (4) pursue Wikipedia once notability is established.
  Regístrate para ver cómo corregir esto
• 09
  FAIL · security

  Security Headers Grade (Mozilla Observatory)

  Security grade D (45/100 baseline, Mozilla Observatory rubric). Top issues: Strict-Transport-Security missing (-20); X-Frame-Options + CSP frame-ancestors both missing (-20); X-Content-Type-Options: nosniff missing (-5)
  Regístrate para ver cómo corregir esto
• 10
  FAIL · security

  Server Signature

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