www.advisorysouth.com

Показано 10 проблем. Полный аудит с кодом исправлений доступен на бесплатном плане.

• 01
  FAIL · performance

  HTTP Requests Count

  The page loads 117 external resources — this is too many (45 CSS, 55 JS, 16 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.
  Войдите, чтобы увидеть как исправить
• 02
  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.
  Войдите, чтобы увидеть как исправить
• 03
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "learn" — 10 times (3.1%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Войдите, чтобы увидеть как исправить
• 04
  FAIL · ai-readiness

  Structured Data Completeness

  No structured data (JSON-LD / Schema.org) found. AI search engines rely heavily on structured data to understand and cite content. Without it, your pages are much less likely to appear in AI-generated answers.
  Войдите, чтобы увидеть как исправить
• 05
  FAIL · security

  Email Authentication (SPF / DMARC / DKIM)

  SPF: fail · DMARC: fail · DKIM: info. Missing or broken: SPF, DMARC. Without SPF/DKIM/DMARC, your emails are likely flagged as spam by Gmail/Outlook, and your domain can be spoofed by phishers.
  Войдите, чтобы увидеть как исправить
• 06
  FAIL · ai-readiness

  Knowledge Panel Readiness

  Low knowledge-panel readiness — score 0/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.
  Войдите, чтобы увидеть как исправить
• 07
  WARN · onpage

  H1 Heading

  Found 5 <h1> tags. HTML5 spec technically allows multiple H1s (one per sectioning element), but Google + Bing + Yandex treat the first H1 as primary and dilute topical relevance when multiple competing H1s exist. AI engines (ChatGPT / Claude / Perplexity) extract the first H1 as the page label — competing H1s produce ambiguous citations. Screen readers may also announce all H1s, confusing assistive-tech users.
  Войдите, чтобы увидеть как исправить
• 08
  FAIL · onpage

  Image Alt Attributes

  15 out of 15 images are missing the alt attribute (only 0% have alt). A significant portion of images is inaccessible to search engines and users with disabilities.
  Войдите, чтобы увидеть как исправить
• 09
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 1657 ms (1.66 sec). Google flags this as "needs improvement" (800 ms – 1.8 s per web.dev). LCP is bounded by TTFB, so reaching the "good LCP" 2.5s threshold becomes harder as TTFB grows.
  Войдите, чтобы увидеть как исправить
• 10
  FAIL · performance

  Render-Blocking Resources

  Found 47 render-blocking resources (44 CSS, 3 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).
  Войдите, чтобы увидеть как исправить