dot.vu — Website Report
Scored 65/100 · Scanned with Foglift
dot.vu scored 65. One fix would take it to 85.
Quick wins
~154 min total fix timehttps://dot.vu/ · 4/24/2026, 3:26:38 AM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://dot.vu/ Great news — your site has strong AI visibility (73/100). Overall score: 65/100. AI engines like ChatGPT and Perplexity are likely to find and cite your content. We found 3 critical issues and 11 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. 5 images missing alt text — Found 5 of 8 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
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. 9 render-blocking scripts — 9 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 content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your
13 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
Technical Issues
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.
<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 Dot?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Dot
SEO & Technical Issues (18)
Found 5 of 8 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
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 -->9 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
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=()' }Your description is 219 characters. Keep it under 160 for best display.
Found 46 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
2 of 8 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
Server responded in 2.8s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 4986KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Your page loads 10 external JavaScript files. Consider bundling some together and deferring non-critical scripts.
8 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.
<!-- 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>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 13 elements with large inline styles. Move these to external CSS for better caching and maintainability.
Found 19 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
65
Now
78
Potential
+13 points possible by fixing 19 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.
Free tier available · No credit card required
Industry Benchmark
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
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.