pinnacleretirementadvisors.com

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

• 01
  FAIL · technical

  Robots.txt

  The robots.txt file was not found at /robots.txt. Without it, Google + Bing + Yandex crawl with default permissions, AI search engines (ChatGPT, Claude, Perplexity, Gemini) may lack explicit policy, and AI training crawlers (GPTBot, CCBot, anthropic-ai, Bytespider) will assume permission to ingest your content silently. A missing robots.txt also means no Sitemap directive, so crawl-budget routing is suboptimal.
  Sign up to see how to fix this
• 02
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 2228 ms (2.23 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.23s. Every downstream Core Web Vital (LCP, INP, CLS) inherits this delay, and Page Experience signals trigger a soft demotion in Google + Bing rankings.
  Sign up to see how to fix this
• 03
  FAIL · technical

  Internal link health

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

  Indexability

  Blocked by <meta name="robots" content="noindex"> — <meta name="robots" content="noindex, nofollow"> tells search engines not to index this page.
  Sign up to see how to fix this
• 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.
  Sign up to see how to fix this
• 06
  FAIL · technical

  HTTP Redirects

  HTTP-to-HTTPS redirect is not configured. Users accessing the site via the insecure protocol (http://) are not being redirected to the HTTPS version.
  Sign up to see how to fix this
• 07
  FAIL · performance

  Render-Blocking Resources

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

  HTTP Requests Count

  The page loads 73 external resources — this is too many (20 CSS, 28 JS, 19 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
• 09
  FAIL · security

  Security Headers

  Only 0 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, strict-transport-security, 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
• 10
  FAIL · security

  Server Signature

  The Server header contains a generic name: "cloudflare". This is acceptable — the specific version is not exposed. The X-Powered-By header reveals the framework in use: "WP Engine". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Sign up to see how to fix this