Skip to main content

mf.nipponindiaim.com — Website Report

Scored 58/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.

mf.nipponindiaim.com scored 58. Addressing the 22 listed issues could raise its estimated score to 82.

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
6 critical13 warnings22 total issues

Quick wins

~184 min total fix time
1AI search engines can't read your site~2m
2Zooming is disabled~2m
3Missing Permissions Policy header~2m

https://mf.nipponindiaim.com/ · 2026-05-05

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

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

FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). 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 Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. Missing H1 heading — Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility. 4. 4 images missing alt text — Found 4 of 43 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 5. Zooming is disabled — Your viewport meta tag prevents users from zooming. Th

18 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

58D
Technical55
Authority61
Set up all 6 tiers free →
70
Brand Mentions
Found 12+ web mentions of "mf"
56
Domain Authority
PageRank: 3.5/10, 14+ external references
30
Content Freshness
500 pages in sitemap but none updated recently
55
Technical Readiness
Moderate technical readiness — some improvements possible

Technical Issues

AI search engines can't read your sitecritical~2 min fix

Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). 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.

Quick Fix
# 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: /
Allow AI crawlers to index your content so you appear in ChatGPT, Perplexity, and Google AI Overviews.
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.

How does AI see Mf?

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

G
C
P
Ge
A

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

SEO & Technical Issues (20)

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.
Missing H1 headingcriticalSEO~3 min fix

Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility.

Quick Fix
<h1>Your Main Page Heading</h1>
<!-- Only use one H1 per page. Make it descriptive and include your target keyword. -->
Every page needs exactly one H1 that describes the main topic. It's a key SEO signal.
4 images missing alt textcriticalSEO

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

Zooming is disabledcriticalAccessibility~2 min fix

Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.

Quick Fix
<!-- 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 -->
Preventing zoom is an accessibility violation. Users with low vision need to zoom to read content.
25 render-blocking scriptscriticalPerformance

25 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

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.
Title tag too longwarningSEO

Your title is 85 characters. Keep it under 60 for best display in search results.

Meta description too longwarningSEO

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

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.
9% of images lack alt textwarningAccessibility

4 of 43 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.

Skipped heading levelwarningAccessibility

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

Potential low contrast textwarningAccessibility

Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.

Server response could be fasterwarningPerformance

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

Large HTML documentwarningPerformance

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

16 external stylesheetswarningPerformance

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

43 images without lazy loadingwarningPerformance

43 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 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.
HTML contains many commentsinfoPerformance

Found 101 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

58

Now

82

Estimated potential

+24 points estimated improvement from addressing 22 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+9On par
AI Readiness
Avg: 35+23Ahead
Performance
Avg: 55-11At risk
Security
Avg: 40+20Ahead
Accessibility
Avg: 68-11At risk

Based on 120+ websites scanned across industries. See full benchmark report →

What This Score Means for You

Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.

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.

Recent scans on Foglift

Scan your own site free →