florika.lt — Website Report
Scored 62/100 · Scanned with Foglift
florika.lt scored 62. One fix would take it to 82.
Quick wins
~107 min total fix timehttps://florika.lt/ · 4/29/2026, 8:47:26 AM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://florika.lt/ Your site scores 62/100 overall, but AI engines may be missing you. Your AI Visibility is 69/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 4 critical issues and 10 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 5 AI crawlers (GPTBot, ChatGPT-User, ClaudeBot...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
2. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections. 3. 45 external scripts loaded — Your page loads 45 external JavaScript files. Each requires a network request. Bundle scripts and defer non-critical ones to improve load time. 4. 35 render-blocking scripts — 35 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. Missing X-Content-Type-Options header — Set X-Content-Ty
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
Your site blocks 5 AI crawlers (GPTBot, ChatGPT-User, ClaudeBot...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /How does AI see Florika?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Florika
SEO & Technical Issues (15)
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' }Your page loads 45 external JavaScript files. Each requires a network request. Bundle scripts and defer non-critical ones to improve load time.
35 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
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=()' }Your title is 69 characters. Keep it under 60 for best display in search results.
Heading hierarchy jumps from H2 to H5. Don't skip heading levels — this confuses screen readers and assistive technology.
Server responded in 2.8s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 253KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Loading 46 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
9 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
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 20 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
62
Now
80
Potential
+18 points possible by fixing 16 issues
That moves you from D to B — top 15% of all websites
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
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: 25/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.