biooneoceanside.com

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

• 01
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 756 ms (0.76 sec) — this is too slow. The server takes a significant amount of time to process the request before it starts sending a response. This negatively affects all Core Web Vitals metrics, as the browser cannot begin rendering until the first byte is received.
  Regístrate para ver cómo corregir esto
• 02
  WARN · technical

  HTTP Redirects

  WWW canonicalization is not configured. The site is accessible with both www and non-www addresses simultaneously, which leads to duplicate content issues for search engines.
  Regístrate para ver cómo corregir esto
• 03
  FAIL · technical

  WWW Canonicalization

  WWW/non-www canonicalization is not configured. The site is accessible at both addresses (biooneoceanside.com and www.biooneoceanside.com), which results in duplicate content. Search engines may index both versions and split link equity between them.
  Regístrate para ver cómo corregir esto
• 04
  FAIL · performance

  Render-Blocking Resources

  Found 9 render-blocking resources (8 CSS, 1 JS) — this is too many. The browser must download and process all of these files before it can start rendering the page. This critically delays First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
  Regístrate para ver cómo corregir esto
• 05
  FAIL · performance

  Image Lazy Loading

  None of the 55 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 135 external resources — this is too many (10 CSS, 12 JS, 110 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, strict-transport-security, 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
  WARN · ai-readiness

  Structured Data Completeness

  Only 2 schema types found (LocalBusiness, Service). AI search engines benefit from richer structured data to accurately cite your content. Aim for 3+ distinct types.
  Regístrate para ver cómo corregir esto
• 09
  WARN · onpage

  Meta Title

  The <title> meta tag is too long (109 chars). The recommended length is between 30 and 60 characters. Search engines may truncate long titles in search results.
  Regístrate para ver cómo corregir esto
• 10
  WARN · onpage

  Meta Description

  The meta description is too long (199 chars). The recommended length is between 120 and 160 characters. Search engines will truncate text that exceeds the allowed limit.
  Regístrate para ver cómo corregir esto