This website audit report analyzes https://karmamodernindian.com/ across 12 critical dimensions with actionable recommendations.
https://karmamodernindian.com/
43Poorout of 100
Website Audit Report
Best Indian Restaurant in Washington, DC | Karma Modern Indian
August 4, 2026 at 3:22 AM GMT+5:30 1121ms response HTTPS Secure
Executive Summary
https://karmamodernindian.com/ scores 43/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, Security. The site has 172 words, 7 images, and 1 schema blocks. Data confidence: 80%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
1121ms
Response Time
172
Word Count
7
Images
36
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (62 chars — may be truncated in SERPs)
2[SEO] Meta description may be truncated (211 chars)
3[SEO] No H1 heading found
4[SEO] No Open Graph tags found
5[SEO] No Twitter Card tags found
6[SEO] Thin content (172 words)
7[SEO] 17 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8[SEO] High dofollow external link count (17) — excessive link equity leakage
9[SEO] Primary keyword missing from first paragraph
10[SEO] Weak E-E-A-T signals (1 indicators)
Top Recommendations
1[Impact: High | Effort: Low] Shorten your title to under 60 characters to prevent truncation in search results
2[Impact: High | Effort: Low] Trim your meta description to under 160 characters to prevent truncation
3[Impact: High | Effort: Low] Add exactly one H1 tag with your primary keyword to establish page topic
4[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
5[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
6[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
7[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
8[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
10[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
11[Impact: High | Effort: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
12[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
Detailed Category Analysis
Key Findings
1Clean heading hierarchy with no skipped levels
2Canonical URL is set and matches the page URL
3HTML lang attribute set to "en-US"
4Favicon present
519 internal links help establish site architecture
617 external links provide reference signals
736 total links — within recommended range
8URL length (30 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 53% of links are internal
11Primary keyword not in URL — acceptable for homepage/root URLs
12Moderate entity presence: Chef Tasting Menu Reservation, Ala Carte Menu Menu Large Parties, Private Dining Takeout Gift Cards Catering In
13Social share buttons detected: ShareThis
Issues Found
1Title tag is too long (62 chars — may be truncated in SERPs)
2Meta description may be truncated (211 chars)
3No H1 heading found
4No Open Graph tags found
5No Twitter Card tags found
6Thin content (172 words)
717 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8High dofollow external link count (17) — excessive link equity leakage
9Primary keyword missing from first paragraph
10Weak E-E-A-T signals (1 indicators)
11Low readability score (27 Flesch) — content is hard to read
12Primary keyword "best indian restaurant" not found in body content
13Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Trim your meta description to under 160 characters to prevent truncation
3Add exactly one H1 tag with your primary keyword to establish page topic
4Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
5Add Twitter Card meta tags for better social media previews
6Expand your content to at least 300+ words for better search rankings
7Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
8Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9Include your primary keyword naturally in the first paragraph to establish topical relevance early
10Include your primary keyword in the URL slug for improved crawlability and click-through rates
11Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
12Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
13Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
14Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
15Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
16SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Lean HTML document: 93KB
23/7 images use lazy loading
3Responsive images with srcset detected
4Most images have explicit width/height attributes (prevents layout shift)
5Preloaded resources: font
6Cache-Control header with max-age is set
7Gzip compression enabled
81 font(s) preloaded for faster text rendering
9Estimated CLS: 0.1 — within Google's "good" threshold (<0.1)
10Estimated INP: ~132ms — within Google's "good" threshold (<200ms)
11Variable fonts detected — reduces total font file downloads
Issues Found
1Slow server response: 1121ms
211 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
4No font-display property found
5Large CSS payload (~539KB across 17 files) — slows rendering
6Moderate JavaScript payload (~556KB)
7HTTP/1.1 detected — no multiplexing
8No CDN detected
917 render-blocking CSS files — delays first paint
10Estimated CSS bundle ~709KB — above optimal
11Potentially unused CSS detected (large stylesheet count relative to page complexity)
12Estimated LCP: ~3981ms — needs improvement (goal: <2.5s)
13No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Investigate server performance — consider upgrading hosting, adding caching layers, or using a CDN
2Convert all non-critical scripts to async/defer to eliminate render-blocking resources
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
5Add font-display: swap to web font declarations to show fallback text while fonts load
6Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
7Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
8Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
9Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
10Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
11Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
12Audit CSS with Chrome DevTools Coverage tab to identify and remove unused CSS rules
13Optimize Largest Contentful Paint: preload hero image, reduce render-blocking resources, use CDN for static assets
14Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Responsive images via srcset serve appropriate sizes per device
63 images with lazy loading benefit mobile data users
7Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
4Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recommendations to Reach 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
3Consider implementing a service worker for offline support and faster repeat visits
4Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
5Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
6Add env(safe-area-inset-*) CSS for proper display on notched/island devices
7Add :active / touch-action CSS for tactile feedback on mobile interactions
8Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
9Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2No cookie security issues detected
3Cookie consent mechanism detected
4No stack traces or sensitive error details exposed in responses
5No raw email addresses exposed in page source
6No obvious secret/API-key patterns exposed in page source
7Client-side library inventory (SBOM): WordPress
811 script resource(s) catalogued for software-composition review
9No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
7Server header exposes technology: Apache
8X-Powered-By header exposes: PHP/8.2.31
917 external links missing rel="noopener noreferrer" — security risk
10No privacy policy detected
11Server-side software version disclosed: PHP/8.2.31 — enables version-based vulnerability (CVE) lookups
12Additional technology fingerprints exposed: Server: Apache; X-Powered-By: PHP/8.2.31
13security.txt file is missing — no standardized channel for reporting vulnerabilities
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Remove or obfuscate the Server header to avoid exposing your technology stack
10Remove X-Powered-By header
11Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
12Add a privacy policy link — required by GDPR, CCPA, and builds user trust
13Suppress version numbers in the Server / X-Powered-By headers and generator meta tag, and keep the framework patched to its latest release to close known CVEs [Impact: High | Effort: Low]
14Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
15A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 7 images have alt attributes
5All 3 buttons have accessible labels
69 ARIA-attributed elements found
7Focus styles detected for keyboard navigation
Issues Found
11 minor HTML validity issue(s)
Recommendations to Reach 100%
1Review and fix HTML structure issues for better accessibility and cross-browser compatibility
2Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
11 schema block(s): WebPage, ImageObject, BreadcrumbList, WebSite, Organization
2Strong semantic markup: header, nav, main, article, footer
3Social presence signals: facebook, instagram
45 call-to-action elements detected
5No AI crawlers blocked via meta tags — content accessible to AI search engines
6robots.txt file found
7robots.txt references 1 sitemap(s) — aids AI crawler discoverability
8High RAG-friendliness (100/100): 0 headings with IDs, 12 section anchors
9Content provenance signals detected (citations with sources, attributed claims)
10Content freshness signals present (dateModified/datePublished/time elements)
11Good HTML-to-text ratio (41%) — AI crawlers can extract content efficiently
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No FAQ or Q&A content patterns found
4No sitemap reference found
5No llms.txt file found — AI models cannot find structured guidance for your site
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Add an FAQ section with FAQPage schema to increase chances of AI engine citations
5Create and reference an XML sitemap for AI crawler discoverability
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9AI Readiness (multimodal): only 29% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Structured content: 3 lists, 0 tables — easily parsed by AI
2Good paragraph length for readability and AI parsing
315 external citations — strong reference density for AI model training
42 call-to-action element(s) detected
5Clear value proposition detected in heading elements
Issues Found
1Very thin content (172 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 127 divs vs 8 semantic elements
5Weak E-E-A-T schema signals
6No author or expertise signals
7No CTA above the fold
8Insufficient trust signals for conversion optimization
9No social proof elements
Recommendations to Reach 100%
1AI models value comprehensive, authoritative content — aim for 1000–2000+ words covering the topic thoroughly
2Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
3Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
4Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
5Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
6Add Speakable schema markup to help voice assistants identify the most important content
7Include specific statistics, percentages, and data points that AI models can extract and cite in responses
8Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
9Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
10Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
11Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
12Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
13Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
13 lists detected
2Content is fresh (updated within 30 days) — strong recency signal
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Content too thin for AI citation value
4Insufficient structured data for generative engine context
5thin content — may not provide enough depth for AI engines
6No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
6Include unique statistics, expert quotes, and original insights that generative AI would want to cite
7Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
8Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
10GEO: only 0/6 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
11GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
1Short paragraphs are well-suited for answer extraction
23 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Consider adding video content with VideoObject schema for multimedia search results
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8AEO: no 40–60 word concise answer directly follows a question heading. Lead each question section with a self-contained ~40–60 word answer to win featured snippets and voice answers.
Key Findings
1NAP information detected: phone: 6677339
2Phone number(s) visible: 6677339, 4214990
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
7Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
Key Findings
11 JSON-LD block(s) with types: WebPage, ImageObject, BreadcrumbList, WebSite, Organization
2Comprehensive schema implementation
3Strong top-tier schema coverage: Organization, BreadcrumbList, WebSite
4BreadcrumbList schema → breadcrumb rich results
5Rich schema diversity: 5 distinct types with properties
62 sameAs link(s) for entity matching
7Rich results potential: Breadcrumbs
8SearchAction schema present — eligible for sitelinks search box in Google
9Schema.org: a connected @graph with 5 entity types is present — strong structured-data maturity.
Issues Found
1Microdata or RDFa detected alongside JSON-LD
2BreadcrumbList has very few properties (1)
3BreadcrumbList missing common identifiers (name/headline/url)
4Schema property completeness averaging 79%
Recommendations to Reach 100%
1Migrate all structured data to JSON-LD format — it's easier to maintain, debug, and is Google's preferred format
2Add FAQPage schema to FAQ content — enables expandable rich results
3Consider adding HowTo schema for instructional content
4Add more properties to schema types — aim for at least 5 meaningful properties per type
5Fill in missing recommended properties for each schema type
6Schema.org (maximize): long-form article content detected but no Article/BlogPosting schema. Add Article with headline, author, datePublished, dateModified, image and publisher for maximal eligibility.
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Focus styles detected for keyboard navigation visibility
4Page language declared — aids assistive technology
5All ARIA roles are valid
6Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Low semantic-to-div ratio — 127 divs vs 8 semantic elements
Recommendations to Reach 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
Limited-Time Offer
All 12 Optimizations — Bundled Into Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.