airbnb.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 · onpage

  Content Length

  Only 22 words were found on the page. This is extremely low for proper indexing. Pages with minimal text content (fewer than 100 words) are considered "thin content" by search engines and rank poorly.
  Regístrate para ver cómo corregir esto
• 02
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 2689 ms (2.69 sec) — Google flags this as "poor" (> 1.8 s per web.dev/articles/ttfb). The browser cannot begin rendering until the first byte arrives, so LCP cannot beat 2.69s. Every downstream Core Web Vital (LCP, INP, CLS) inherits this delay, and Page Experience signals trigger a soft demotion in Google + Bing rankings.
  Regístrate para ver cómo corregir esto
• 03
  FAIL · content

  Thin Content

  The page contains almost no text (22 words). This is critically insufficient for search engine indexing. Text-to-HTML ratio: 0%. Such pages may be classified as doorway pages or empty shells and excluded from search results.
  Regístrate para ver cómo corregir esto
• 04
  FAIL · onpage

  Image Alt Attributes

  1 out of 1 images are missing the alt attribute (only 0% have alt). A significant portion of images is inaccessible to search engines and users with disabilities.
  Regístrate para ver cómo corregir esto
• 05
  FAIL · technical

  XML Sitemap

  The sitemap.xml file was not found at /sitemap.xml. Without a sitemap, Google + Bing + Yandex must rely on internal-link discovery to find your pages — recently published or orphan content may not be indexed for weeks. AI search engines (ChatGPT search via OAI-SearchBot, Claude search, Perplexity) also crawl sitemap.xml to discover content, so missing sitemaps delay AI citation as well.
  Regístrate para ver cómo corregir esto
• 06
  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
• 07
  FAIL · technical

  WWW Canonicalization

  WWW/non-www canonicalization is not configured. The site is accessible at both addresses (airbnb.com and www.airbnb.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
• 08
  FAIL · performance

  Page Size

  The total HTML page size is 580.4 KB, 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
• 09
  FAIL · performance

  HTTP Requests Count

  The page loads 96 external resources — this is too many (1 CSS, 41 JS, 1 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
• 10
  WARN · security

  Security Headers

  Found 4 out of 6 modern security headers. Missing: referrer-policy, permissions-policy. Add the remaining headers to close defense-in-depth gaps. Note: Content-Security-Policy is the highest-impact header — if it is missing the site is exposed to XSS even when other headers are present.
  Regístrate para ver cómo corregir esto