Skip to main content

www.kellyhayes.com — Website Report

Scored 66/100 · Scanned with Foglift

D
Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

kellyhayes.com scored 66. Addressing the 22 listed issues could raise its estimated score to 80.

3 critical12 warnings22 total issues

Quick wins

~179 min total fix time
1Zooming is disabled~2m
2Missing Referrer Policy header~2m
3Missing Permissions Policy header~2m

https://www.kellyhayes.com/ · 2026-09-17

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://www.kellyhayes.com/ Site Technical Health: 66/100. AI Readiness is 59/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 3 critical issues and 12 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. AI engines can't understand your business — Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.

2. Zooming is disabled — Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content. 3. 7 render-blocking scripts — 7 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. No FAQ section found — A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it re

14 more critical fixes + quick wins in your full report

Create a free account to save this audit and unlock the complete action plan.

Save and unlock my full report

Free account. No credit card required.

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

59D
Technical52
Authority64
Set up all 6 tiers free →
100
Brand Mentions
Found 20+ web mentions of "kellyhayes"
27
Domain Authority
PageRank: 2.0/10, 3+ external references
77
Content Freshness
122 of 500 pages updated in the last 30 days
52
Technical Readiness
Moderate technical readiness — some improvements possible

Technical Issues

AI engines can't understand your businesscritical~10 min fix

Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://yoursite.com",
  "description": "Brief description of your business",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>
Add JSON-LD structured data so AI models understand your business entity and can cite you accurately.
No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>
FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.
AI doesn't know who you areinfo~10 min fix

Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany",
    "https://github.com/yourorg"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@yoursite.com",
    "contactType": "customer service"
  }
}
</script>
Entity markup tells AI models who you are, making them more likely to cite your brand accurately.
Page summary too short for AIinfo~5 min fix

Your meta description is under 80 characters. AI engines use this as a quick summary of your page. Write a clear, factual description (120-160 characters) that explains what your business does and why it matters.

Quick Fix
<!-- Aim for 120-160 characters with clear, factual information -->
<meta name="description" content="[Your Company] provides [specific service] for [target audience]. Founded in [year], we serve [number]+ customers with [key differentiator].">
AI models extract meta descriptions to understand what your business does. Make it factual and specific.

How does AI see Kellyhayes?

When users ask AI about your industry, are you recommended?

G
C
P
Ge
A

Start with weekly Perplexity checks for Kellyhayes. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

SEO & Technical Issues (18)

Zooming is disabledcriticalAccessibility~2 min fix

Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.

Quick Fix
<!-- Replace your viewport meta tag with this (allows zooming) -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Do NOT use: maximum-scale=1, user-scalable=no -->
Preventing zoom is an accessibility violation. Users with low vision need to zoom to read content.
7 render-blocking scriptscriticalPerformance

7 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Referrer Policy headerwarningSecurity~2 min fix

Add a Referrer-Policy header to control information leakage.

Quick Fix
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }
Controls how much referrer information is sent with requests, protecting user privacy.
Missing Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }
Permissions-Policy restricts which browser features your site can use, reducing attack surface.
Missing Open Graph tagswarningSEO~10 min fix

Missing og:title, og:description, og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.

Quick Fix
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">
Open Graph tags control how your page looks when shared on Facebook, LinkedIn, and other social platforms.
Missing canonical URLwarningSEO~3 min fix

Add a canonical link to prevent duplicate content issues in search engines.

Quick Fix
<link rel="canonical" href="https://yoursite.com/current-page">
Canonical URLs prevent duplicate content issues by telling search engines which version of a page is the original.
3 images missing alt textwarningSEO

Found 3 of 27 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).

11% of images lack alt textwarningAccessibility

3 of 27 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.

8 form inputs may lack labelswarningAccessibility

Form inputs should have associated labels or aria-label attributes so screen readers can identify them.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.

Large HTML documentwarningPerformance

Your HTML is 268KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

28 external stylesheetswarningPerformance

Loading 28 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.

5 images without lazy loadingwarningPerformance

5 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

No structured data foundinfoSEO

Add JSON-LD structured data (Schema.org) to help search engines understand your content and earn rich snippets in search results.

Missing Twitter Card tagsinfoSEO~5 min fix

Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.

Quick Fix
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">
Twitter Card tags control how your page appears when shared on Twitter/X.
Few internal linksinfoSEO

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix
<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>
Skip links let keyboard users bypass repetitive navigation and jump straight to content.
HTML contains many commentsinfoPerformance

Found 62 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

66

Now

80

Estimated potential

+14 points estimated improvement from addressing 22 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+11Ahead
AI Readiness
Avg: 35+24Ahead
Performance
Avg: 55+4On par
Security
Avg: 40+35Ahead
Accessibility
Avg: 68-10Behind

Based on 120+ websites scanned across industries. See full benchmark report →

What This Score Means for You

Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.

Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).

Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.

Recent scans on Foglift

Scan your own site free →