Skip to main content

callvin.com — Website Report

Scored 51/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

callvin.com scored 51. One fix would take it to 71.

4 critical13 warnings23 total issues

Quick wins

~169 min total fix time
1Missing HSTS header~2m
2Missing X-Content-Type-Options header~2m
3Missing X-Frame-Options header~2m

https://callvin.com/ · 2026-07-14

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://callvin.com Your site scores 51/100 overall, but AI engines may be missing you. Your AI Visibility is 58/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 4 critical issues and 13 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. 7 images missing alt text — Found 7 of 123 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 4. 5 render-blocking scripts — 5 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 love Q&A con

16 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.

Email to Contact

AI Visibility

How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand

58D

Some external data sources were unavailable. Score is based on partial data.

100
Brand Mentions
Found 20+ web mentions of "callvin"
40
Domain Authority
PageRank: 2.6/10, 6+ external references
0
Content Freshness
Unable to analyze content freshness: Sitemap not found (404)
63
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.
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.

How does AI see Callvin?

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

G
C
P
Ge
A

See how ChatGPT, Claude, Perplexity, and Gemini talk about Callvin

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.
7 images missing alt textcriticalSEO

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

5 render-blocking scriptscriticalPerformance

5 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 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.
No sitemap.xml foundwarningSEO~15 min fix

Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.

Quick Fix
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yoursite.com/</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yoursite.com/about</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>0.8</priority>
  </url>
</urlset>
A sitemap.xml helps search engines discover and index all your pages. Place it at your site root.
6% of images lack alt textwarningAccessibility

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

1 form input may lack labelswarningAccessibility

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

Server response could be fasterwarningPerformance

Server responded in 1.1s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.

Large HTML documentwarningPerformance

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

6 external stylesheetswarningPerformance

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

123 images without lazy loadingwarningPerformance

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

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.
No navigation landmarkinfoAccessibility~5 min fix

Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.

Quick Fix
<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>
The <nav> landmark lets screen reader users quickly jump to navigation (WCAG 2.4.1).
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.
No resource hintsinfoPerformance~5 min fix

Add <link rel='preconnect'> for critical third-party domains to reduce connection setup time.

Quick Fix
<!-- Add to <head> for your critical third-party domains -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://cdn.example.com">
Preconnect and DNS-prefetch reduce connection time to third-party domains by starting the handshake early.

Your Potential Score

51

Now

75

Potential

+24 points possible by fixing 23 issues

That moves you from D to Cabove 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+15Ahead
AI Readiness
Avg: 35+30Ahead
Performance
Avg: 55-11At risk
Security
Avg: 40-30At risk
Accessibility
Avg: 68-4Behind

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: 10/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.

Recent scans on Foglift

Scan your own site free →