musikhin.ru

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

• 01
  FAIL · security

  Exposed Paths

  Publicly-readable sensitive paths detected: /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
• 02
  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
• 03
  FAIL · performance

  Render-Blocking Resources

  Found 17 render-blocking resources (7 CSS, 10 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
• 04
  FAIL · performance

  Image Lazy Loading

  Only 4 out of 21 images (19%) 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 · performance

  HTTP Requests Count

  The page loads 55 external resources — this is too many (7 CSS, 17 JS, 21 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
• 06
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "октября" — 7 times (4.2%). 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
• 07
  WARN · ai-readiness

  Structured Data Completeness

  Only 1 schema type found (Article). 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