This website audit report analyzes https://www.lewnessteakhouse.com/ across 12 critical dimensions with actionable recommendations.
https://www.lewnessteakhouse.com/
63Needs Workout of 100
Website Audit Report
Lewnes' Steakhouse
May 25, 2026 at 6:38 PM EDT 727ms response HTTPS Secure
Executive Summary
https://www.lewnessteakhouse.com/ scores 63/100 (D). Strong areas include Performance. Priority improvements needed in SEO, AI Readiness, AIO. The site has 399 words, 0 images, and 0 schema blocks. Focus on the top recommendations below to improve your score.
727ms
Response Time
399
Word Count
0
Images
0
Links
Score History
Current scan6 scans recorded· Tap or hover a point for score & time↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too short (18 chars)
2[SEO] No H1 heading found
3[SEO] Very few headings for content length
4[SEO] Missing canonical URL
5[SEO] Missing OG tags: og:url
6[SEO] Missing favicon
7[Performance] No font-display property found
8[Security] Missing Content-Security-Policy header
9[Security] Missing X-Frame-Options header
10[Security] Missing Permissions-Policy header
Top Recommendations
1Expand your title to 30–60 characters for better click-through rates
2Add exactly one H1 tag with your primary keyword to establish page topic
3Add more subheadings (H2, H3) to break up content and improve scannability
4Add a <link rel="canonical"> tag pointing to the preferred version of this page
5Add missing Open Graph tags: og:url
6Add a favicon for brand recognition in browser tabs and bookmarks
7Optimize server response time to under 500ms with caching or a CDN
8Preload critical resources (fonts, hero images) with <link rel="preload">
9Add font-display: swap to web font declarations to show fallback text while fonts load
10Implement a Content Security Policy to prevent XSS and injection attacks
11Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
12Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
Detailed Category Analysis
Key Findings
1Meta description is 153 characters — within optimal 120–160 range
2Complete Twitter Card tags present
3HTML lang attribute set to "en"
4Content length of 399 words is adequate
Issues Found
1Title tag is too short (18 chars)
2No H1 heading found
3Very few headings for content length
4Missing canonical URL
5Missing OG tags: og:url
6Missing favicon
Recommendations to Reach 100%
1Expand your title to 30–60 characters for better click-through rates
2Add exactly one H1 tag with your primary keyword to establish page topic
3Add more subheadings (H2, H3) to break up content and improve scannability
4Add a <link rel="canonical"> tag pointing to the preferred version of this page
5Add missing Open Graph tags: og:url
6Add a favicon for brand recognition in browser tabs and bookmarks
Key Findings
1Acceptable response time: 727ms
2Lean HTML document: 6KB
3No render-blocking scripts detected
4Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com
50 async and 1 deferred scripts
6Cache-Control header with max-age is set
Issues Found
1No font-display property found
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Preload critical resources (fonts, hero images) with <link rel="preload">
3Add font-display: swap to web font declarations to show fallback text while fonts load
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0
2HTML5 doctype declared
3Character encoding declared
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
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
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4Referrer-Policy set to: strict-origin-when-cross-origin
5Server via CDN proxy (cloudflare) — header added by infrastructure, not application
Issues Found
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Permissions-Policy header
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
3Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
4Add Cross-Origin-Opener-Policy: same-origin-allow-popups
5Add Cross-Origin-Resource-Policy: cross-origin
Key Findings
1Language declared: en
Issues Found
1No skip navigation link
2Missing landmarks: main, nav, footer
3No ARIA attributes detected
4No focus styles detected
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <nav>, <footer>
3Add ARIA attributes to interactive elements for better screen reader support
4Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Key Findings
1Complete social metadata (OG + Twitter Card)
Issues Found
1No structured data (Schema.org) found
2No semantic HTML elements detected
3No breadcrumb navigation
4No FAQ or Q&A content patterns found
5No sitemap reference found
6No social media links found
Recommendations to Reach 100%
1Implement JSON-LD structured data — start with Organization, BreadcrumbList, and page-specific types
2Add hreflang tags if your site serves multiple languages or regions
3Replace generic divs with semantic HTML5 elements to help AI models understand your content structure
4Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
5Add an FAQ section with FAQPage schema to increase chances of AI engine citations
6Create and reference an XML sitemap for AI crawler discoverability
7Use <strong> and <em> tags to highlight key entities, concepts, and terms
8Add links to your social media profiles to strengthen brand entity signals
Key Findings
1Good paragraph length for readability and AI parsing
Issues Found
1Content may be too thin for AI optimization (399 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 2 divs vs 0 semantic elements
5Weak E-E-A-T schema signals
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
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 structured content (lists, comparison tables) that AI models can easily extract and reference
6Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
7Add Speakable schema markup to help voice assistants identify the most important content
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Few or no lists
4Content too thin for AI citation value
5Insufficient structured data for generative engine context
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
3Use numbered and bulleted lists for step-by-step content — generative engines prefer structured, scannable formats
4Include how-to or step-by-step instructional content for generative AI answer inclusion
5Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
6Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
7Include unique statistics, expert quotes, and original insights that generative AI would want to cite
8Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
Key Findings
1Short paragraphs are well-suited for answer extraction
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
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
6Add more bullet/numbered lists — search engines frequently pull list content into People Also Ask results
7Consider adding video content with VideoObject schema for multimedia search results
Key Findings
1NAP information detected: phone: (410) 263-1617
2Phone number(s) visible: (410) 263-1617
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
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
Issues Found
1No Schema.org structured data found
Recommendations to Reach 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
Key Findings
1Page language declared — aids assistive technology
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4No relative units for text sizing detected
5No semantic HTML5 elements detected
6No focus styles detected
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
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Use rem, em, or clamp() for font sizes to allow users to resize text up to 200% without loss of content (WCAG 1.4.4)
5Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
6Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
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.