surfpuertovallarta.info

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
  FAIL · onpage

  H1 Heading

  The H1 heading is missing from the page. The <h1> tag is the primary heading and one of the most important on-page ranking factors. Search engines use it to determine the main topic of the page.
  Regístrate para ver cómo corregir esto
• 03
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 2326 ms (2.33 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
• 04
  WARN · onpage

  Meta Title

  The <title> meta tag is too short (20 chars). The recommended length is between 30 and 60 characters. Short titles do not fully utilize the available space in search results.
  Regístrate para ver cómo corregir esto
• 05
  FAIL · technical

  HTTP Redirects

  HTTP-to-HTTPS redirect is not configured. Users accessing the site via the insecure protocol (http://) are not being redirected to the HTTPS version. 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
• 06
  FAIL · technical

  WWW Canonicalization

  WWW/non-www canonicalization is not configured. The site is accessible at both addresses (surfpuertovallarta.info and www.surfpuertovallarta.info), 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
• 07
  FAIL · performance

  Browser Caching

  Caching headers are completely absent. Without Cache-Control, Expires, ETag, and Last-Modified, the browser will reload all resources on every visit, significantly increasing load time and consuming user bandwidth.
  Regístrate para ver cómo corregir esto
• 08
  FAIL · performance

  Render-Blocking Resources

  Found 20 render-blocking resources (16 CSS, 4 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
• 09
  FAIL · performance

  Image Lazy Loading

  None of the 5 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
• 10
  FAIL · security

  Security Headers

  Only 3 out of 7 recommended security headers found. Missing: 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