Skip to main content

ziina.com — Website Report

Scored 65/100 · Scanned with Foglift

Site Technical HealthMean of SEO, Performance, Security, and Accessibility. AI Readiness is reported separately.
D
Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

ziina.com scored 65. Addressing the 18 listed issues could raise its estimated score to 93.

SEOSearch Engine Optimization — how well your site ranks in traditional search engines like Google
AI ReadinessAI Readiness: this saved audit's weighted combination of Technical (T1) and Authority (T2) signals.
PerformancePerformance — how fast your site loads (Core Web Vitals, page weight, render speed)
SecuritySecurity — how well your site protects against threats (HTTPS, headers, CSP, HSTS)
AccessibilityAccessibility — how usable your site is for people with disabilities, including screen readers and keyboard navigation
2 critical11 warnings18 total issues

Quick wins

~139 min total fix time
1Missing X-Content-Type-Options header~2m
2Missing Referrer Policy header~2m
3Missing Permissions Policy header~2m

https://ziina.com/ · 2026-05-13

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://ziina.com/ Your site scores 65/100 overall, but AI engines may be missing you. Your AI Visibility is 63/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 2 critical issues and 11 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks.

2. 20 third-party scripts loaded — Your page loads 20 scripts from external domains. Each requires a separate connection. Audit analytics, chat widgets, and trackers; remove or defer non-essential ones. 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 page, and you'll significantly increase your chances of being cited in AI-generated answers. 2. Missing X-Cont

12 more critical fixes + quick wins in your full report

Create a free account to save this audit and unlock the complete action plan.

Save and unlock my full report

Free account. No credit card required.

Share This Technical Audit

Send this Technical Audit to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

70C
Technical69
Authority70
Set up all 6 tiers free →
100
Brand Mentions
Found 20+ web mentions of "ziina"
46
Domain Authority
PageRank: 3.5/10, 6+ external references
10
Content Freshness
44 pages in sitemap but none updated recently
69
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>
Add an FAQ only when it reflects real customer questions. Never add one solely to contact, about, legal, or listing/index pages. FAQPage schema labels genuine questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.
Content is hard for AI to scaninfo

Your page relies on plain text without lists, tables, or comparison charts. AI assistants extract and cite structured content (bullet points, comparison tables, step-by-step lists) far more accurately than long paragraphs.

How does AI see Ziina?

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

G
C
P
Ge
A

Start with weekly Perplexity checks for Ziina. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

SEO & Technical Issues (16)

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.
20 third-party scripts loadedcriticalPerformance

Your page loads 20 scripts from external domains. Each requires a separate connection. Audit analytics, chat widgets, and trackers; remove or defer non-essential ones.

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 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.
Meta description too longwarningSEO

Your description is 165 characters. Keep it under 160 for best display.

Multiple H1 headings foundwarningSEO

Found 2 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.

3 images missing alt textwarningSEO

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

7% of images lack alt textwarningAccessibility

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

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.

Large HTML documentwarningPerformance

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

6 images without lazy loadingwarningPerformance

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

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.
Heavy inline stylesinfoPerformance

Found 17 elements with large inline styles. Move these to external CSS for better caching and maintainability.

Your Potential Score

65

Now

93

Estimated potential

+28 points estimated improvement from addressing 18 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 Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, 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.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+24Ahead
AI Readiness
Avg: 35+35Ahead
Performance
Avg: 55+9On par
Security
Avg: 40-5Behind
Accessibility
Avg: 68+5On par

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: 35/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 →