supabase.com

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

• 01
  FAIL · technical

  Internal link health

  5/10 sampled internal links failed: 0 4xx, 0 5xx, 0 broken redirects, 5 timeouts, 0 errors.
  Sign up to see how to fix this
• 02
  WARN · ai-readiness

  Structured Data Completeness

  Only 2 schema types found (Organization, WebSite). AI search engines benefit from richer structured data to accurately cite your content. Aim for 3+ distinct types.
  Sign up to see how to fix this
• 03
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "supabase" — 97 times (7.1%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Sign up to see how to fix this
• 04
  FAIL · performance

  Image Lazy Loading

  Only 86 out of 185 images (46%) use lazy loading — this is very low. The browser is forced to load most images immediately, even if they are far outside the visible area.
  Sign up to see how to fix this
• 05
  FAIL · security

  Security Headers

  Only 1 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, content-security-policy, 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.
  Sign up to see how to fix this
• 06
  FAIL · performance

  HTTP Requests Count

  The page loads 249 external resources — this is too many (2 CSS, 27 JS, 185 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
• 07
  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.
  Sign up to see how to fix this
• 08
  FAIL · security

  Security Headers Grade (Mozilla Observatory)

  Security grade D+ (50/100 baseline, Mozilla Observatory rubric). Top issues: Content-Security-Policy header missing (-25); X-Frame-Options + CSP frame-ancestors both missing (-20); X-Content-Type-Options: nosniff missing (-5)
  Sign up to see how to fix this