Foglift
cnettleman.net — Website Report
Scored 53/100 · Scanned with Foglift
D
cnettleman.net scored 53. One fix would take it to 73.
4 critical15 warnings22 total issues
Quick wins
~160 min total fix time1Missing HSTS header~2m
2Zooming is disabled~2m
3Missing X-Content-Type-Options header~2m
https://cnettleman.net/ · 2026-06-12
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://cnettleman.net/ Great news — your site has strong AI visibility (72/100). Overall score: 53/100. AI engines like ChatGPT and Perplexity are likely to find and cite your content. We found 4 critical issues and 15 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. 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. 4. 22 render-blocking scripts — 22 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 — AI assistants l
18 more critical fixes + quick wins in your full report
Enter your email and we'll send the complete action plan to your inbox.
No spam. Just your report.
Share This Report
Send this scan to a teammate or contact. The shareable link includes all scores and issues.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
72C
85
Brand Mentions
Found 19+ web mentions of "cnettleman"
58
Domain Authority
PageRank: 2.4/10, 20+ external references
67
Content Freshness
6 of 66 pages updated in the last 30 days
75
Technical Readiness
Moderate technical readiness — some improvements possible
Technical Issues
No FAQ section foundwarning~15 min fix
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
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>AI models frequently cite FAQ content. Add FAQPage schema to boost your chances of appearing in AI-generated answers.
How does AI see Cnettleman?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Cnettleman
SEO & Technical Issues (21)
Missing HSTS headercriticalSecurity~2 min fix
Enable HTTP Strict Transport Security to force HTTPS connections.
Quick Fix
# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }HSTS forces browsers to use HTTPS, preventing downgrade attacks and cookie hijacking.
Missing Content Security Policy headercriticalSecurity~5 min fix
Add a Content-Security-Policy header to prevent XSS and injection attacks.
Quick Fix
# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;
# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"
# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.
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.
22 render-blocking scriptscriticalPerformance
22 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Missing X-Content-Type-Options headerwarningSecurity~2 min fix
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
Quick Fix
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Prevents browsers from MIME-type sniffing, which can lead to security vulnerabilities.
Missing X-Frame-Options headerwarningSecurity~2 min fix
Set X-Frame-Options to prevent clickjacking attacks.
Quick Fix
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }X-Frame-Options prevents clickjacking by controlling who can embed your page in an iframe.
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.
Multiple H1 headings foundwarningSEO
Found 4 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
1 image missing alt textwarningSEO
Found 1 of 43 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
2% of images lack alt textwarningAccessibility
1 of 43 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Skipped heading levelwarningAccessibility
Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology.
10 links with vague textwarningAccessibility
Links with text like "click here" or "read more" don't make sense out of context. Use descriptive link text that explains the destination.
Potential low contrast textwarningAccessibility
Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.
Server response could be fasterwarningPerformance
Server responded in 1.7s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Large HTML documentwarningPerformance
Your HTML is 313KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
12 external stylesheetswarningPerformance
Loading 12 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
24 images without lazy loadingwarningPerformance
24 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
No main landmarkinfoAccessibility~3 min fix
Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.
Quick Fix
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
<h1>Page Title</h1>
<p>Your primary content here...</p>
</main>The <main> element identifies the primary content area, letting screen reader users skip to it directly.
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 27 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
53
Now
76
Potential
+23 points possible by fixing 22 issues
That moves you from D to C — above average
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Start monitoring — from $49/mo
Free tier available · No credit card required
Industry Benchmark
SEO
Avg: 62+31Ahead
AI Readiness
Avg: 35+38Ahead
Performance
Avg: 55-11At risk
Security
Avg: 40-40At risk
Accessibility
Avg: 68-14At risk
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
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.
Security score: 0/100
Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.
Score of 0 means your site has no security headers at all. Browsers may show security warnings to visitors.