This website audit report analyzes https://queens-haein.com/storefront/sub-marine across 12 critical dimensions with actionable recommendations.
https://queens-haein.com/storefront/sub-marine
62Needs Workout of 100
Website Audit Report
Loading
May 18, 2026 at 8:59 PM EDT 256ms response HTTPS Secure
Executive Summary
https://queens-haein.com/storefront/sub-marine scores 62/100 (D-). Strong areas include Performance, Mobile, WCAG. Priority improvements needed in SEO, Security, AI Readiness. The site has 368 words, 0 images, and 0 schema blocks. Focus on the top recommendations below to improve your score.
256ms
Response Time
368
Word Count
0
Images
0
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too short (7 chars)
2[SEO] Meta description is short (12 chars)
3[SEO] No H1 heading found
4[SEO] Very few headings for content length
5[SEO] Missing canonical URL
6[SEO] No Open Graph tags found
7[SEO] No Twitter Card tags found
8[SEO] Missing favicon
9[Performance] No font-display property found
10[Performance] No effective Cache-Control header
Top Recommendations
1Expand your title to 30–60 characters for better click-through rates
2Expand your meta description to 120–160 characters for better SERP visibility
3Add exactly one H1 tag with your primary keyword to establish page topic
4Add more subheadings (H2, H3) to break up content and improve scannability
5Add a <link rel="canonical"> tag pointing to the preferred version of this page
6Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
7Add Twitter Card meta tags for better social media previews
8Add a favicon for brand recognition in browser tabs and bookmarks
9Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
10Add font-display: swap to web font declarations to show fallback text while fonts load
11Set Cache-Control headers with appropriate max-age to leverage browser caching
12Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
Detailed Category Analysis
Key Findings
1HTML lang attribute set to "en"
2Content length of 368 words is adequate
Issues Found
1Title tag is too short (7 chars)
2Meta description is short (12 chars)
3No H1 heading found
4Very few headings for content length
5Missing canonical URL
6No Open Graph tags found
7No Twitter Card tags found
8Missing favicon
Recommendations to Reach 100%
1Expand your title to 30–60 characters for better click-through rates
2Expand your meta description to 120–160 characters for better SERP visibility
3Add exactly one H1 tag with your primary keyword to establish page topic
4Add more subheadings (H2, H3) to break up content and improve scannability
5Add a <link rel="canonical"> tag pointing to the preferred version of this page
6Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
7Add Twitter Card meta tags for better social media previews
8Add a favicon for brand recognition in browser tabs and bookmarks
Key Findings
1Excellent server response time: 256ms
2Lean HTML document: 34KB
3No render-blocking scripts detected
4Preloaded resources: font, font, font, font, style
50 async and 20 deferred scripts
Issues Found
1No font-display property found
2No effective Cache-Control header
Recommendations to Reach 100%
1Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
2Add font-display: swap to web font declarations to show fallback text while fonts load
3Set Cache-Control headers with appropriate max-age to leverage browser caching
Key Findings
1Viewport meta tag present: width=device-width
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
Recommendations to Reach 100%
1Consider implementing a service worker for offline support and faster repeat visits
Key Findings
1HTTPS enabled — encrypted connection
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: rhino-core-shield
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
Key Findings
1Language declared: en
2Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
2Missing landmarks: main, nav, footer
3No ARIA attributes 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
Issues Found
1No structured data (Schema.org) found
2No semantic HTML elements detected
3Incomplete social metadata
4No breadcrumb navigation
5No FAQ or Q&A content patterns found
6No sitemap reference found
7No 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 (368 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 4 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: 8717328307, email: [email protected]
2Phone number(s) visible: 8717328307, 5497617
3Email address found: [email protected]
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
Recommendations to Reach 100%
1Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add 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
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
Issues Found
1No semantic HTML5 elements detected
Recommendations to Reach 100%
1Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
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.