actini.com — Website Report
Scored 55/100 · Scanned with Foglift
actini.com scored 55. Addressing the 20 listed issues could raise its estimated score to 78.
Quick wins
~145 min total fix timehttps://actini.com/ · 2026-08-07
Scanned with Foglift · Technical Audit + AI Readiness analysis
Share This Report
Send this scan to a teammate or contact. The shareable link includes all scores and issues.
AI Readiness
Technical and authority signals that support AI systems in accessing, understanding, and reusing your content
Some external data sources were unavailable. Score is based on partial data.
Technical Issues
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.
<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>How does AI see Actini?
When users ask AI about your industry, are you recommended?
Start with weekly Google AI Overview checks for Actini. Paid plans add ChatGPT, Perplexity, Gemini, and Claude.
SEO & Technical Issues (19)
Enable HTTP Strict Transport Security to force HTTPS connections.
# 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' }Add a Content-Security-Policy header to prevent XSS and injection attacks.
# 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'" }Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.
<!-- 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 -->Your page loads 22 scripts from external domains. Each requires a separate connection. Audit analytics, chat widgets, and trackers; remove or defer non-essential ones.
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Set X-Frame-Options to prevent clickjacking attacks.
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }Add a Referrer-Policy header to control information leakage.
# 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' }Add a Permissions-Policy header to control browser feature access.
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }Missing og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.
<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">Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.
<?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>Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology.
Server responded in 1.4s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Loading 12 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
34 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.
Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
<h1>Page Title</h1>
<p>Your primary content here...</p>
</main>Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.
<!-- 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>Found 9 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
55
Now
78
Estimated potential
+23 points estimated improvement from addressing 20 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 Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, 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.
Weekly Google AI Overview while active · No credit card required
Compare paid plans — from $49/moIndustry Benchmark
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.
AI visibility preview
See which brands Google AI Overview surfaces for your category.