999.md

Showing top 10 issues. Full audit with code-level fixes available on the free plan.

• 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.
  Sign up to see how to fix this
• 02
  FAIL · security

  Exposed Paths

  Publicly-readable sensitive paths detected: /.env, /backup.zip, /.DS_Store, /sitemap.xml.bak. These should not be accessible without auth — they often leak source code, credentials, or backups.
  Sign up to see how to fix this
• 03
  FAIL · content

  Thin Content

  Thin content detected on this page — only 71 words. Text-to-HTML ratio: 0.2%. Search engines (Google, Bing) demote pages with insufficient unique content in their rankings.
  Sign up to see how to fix this
• 04
  FAIL · technical

  Internal link health

  2/10 sampled internal links failed: 0 4xx, 0 5xx, 0 broken redirects, 2 timeouts, 0 errors.
  Sign up to see how to fix this
• 05
  FAIL · onpage

  H1 Heading

  The H1 heading is missing. Google + Bing + Yandex use H1 as a secondary ranking signal (after <title>) to confirm page topic. ChatGPT / Claude / Perplexity also lean on H1 when extracting page summaries for citation — a missing H1 forces them to infer the topic from <title> and body text, often less accurately. Accessibility screen readers also rely on H1 for page-level navigation.
  Sign up to see how to fix this
• 06
  FAIL · onpage

  Content Length

  Only 71 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.
  Sign up to see how to fix this
• 07
  FAIL · performance

  Browser Caching

  Only 1 out of 4 caching headers found (Cache-Control). Missing: Expires, ETag, Last-Modified. Caching is virtually unconfigured, causing resources to be reloaded on every visit.
  Sign up to see how to fix this
• 08
  FAIL · performance

  Render-Blocking Resources

  Found 10 render-blocking resources (9 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).
  Sign up to see how to fix this
• 09
  FAIL · performance

  Image Lazy Loading

  None of the 48 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.
  Sign up to see how to fix this
• 10
  FAIL · performance

  HTTP Requests Count

  The page loads 153 external resources — this is too many (9 CSS, 47 JS, 48 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.
  Sign up to see how to fix this