This website audit report analyzes http://Harbour-House.org across 12 critical dimensions with actionable recommendations.
http://Harbour-House.org
44Poorout of 100
Website Audit Report
Harbour House – Residential Crisis Services
May 28, 2026 · 10:18 (America/New_York) 516ms response Not Secure
Executive Summary
http://Harbour-House.org scores 44/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, Security. The site has 195 words, 2 images, and 0 schema blocks. Data confidence: 75%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
516ms
Response Time
195
Word Count
2
Images
9
Links
Score History
Current scan2 scans recorded· Tap or hover a point for score & time↑ 1 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is short (43 chars)
2[SEO] Missing meta description
3[SEO] No Open Graph tags found
4[SEO] No Twitter Card tags found
5[SEO] Thin content (195 words)
6[SEO] Only 1 dofollow external link — consider adding a few more to authoritative sources
7[SEO] Weak E-E-A-T signals (2 indicators)
8[SEO] Low readability score (1 Flesch) — content is hard to read
9[SEO] Keyword stuffing detected: "harbour house" appears 6 times (6.2% density — exceeds 3%)
10[SEO] Low OG sharing completeness (0%) — social previews will be poor
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2[Impact: High | Effort: Low] Add a compelling meta description of 140–160 characters with target keywords (2025-2026 best practice)
3[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
4[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
5[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
6[Impact: Medium | Effort: Low] Aim for 2–5 dofollow outbound links per page to demonstrate topical authority
7[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
8[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
9[Impact: High | Effort: Low] Reduce keyword density from 6.2% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
10[Impact: High | Effort: Low] Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
11[Impact: High | Effort: High] Optimize server response time to under 500ms with caching or a CDN
12[Impact: High | Effort: Medium] Convert all non-critical scripts to async/defer to eliminate render-blocking resources
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Harbour House"
2Canonical URL is set and matches the page URL
3HTML lang attribute set to "en"
4Favicon present
58 internal links help establish site architecture
61 external links provide reference signals
79 total links — within recommended range
8URL length (29 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 89% of links are internal
11Good anchor text diversity: 100% unique anchor texts
12Primary keyword "harbour house" found in H1 — strong on-page signal
13Primary keyword appears in first paragraph — excellent content signal
14Primary keyword present in URL — good URL optimization
15Moderate entity presence: Harbour House, Contact Us, Harbour House Residential Crisis Services
16Social share buttons detected: ShareThis
Issues Found
1Title tag is short (43 chars)
2Missing meta description
3No Open Graph tags found
4No Twitter Card tags found
5Thin content (195 words)
6Only 1 dofollow external link — consider adding a few more to authoritative sources
7Weak E-E-A-T signals (2 indicators)
8Low readability score (1 Flesch) — content is hard to read
9Keyword stuffing detected: "harbour house" appears 6 times (6.2% density — exceeds 3%)
10Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2Add a compelling meta description of 140–160 characters with target keywords (2025-2026 best practice)
3Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
4Add Twitter Card meta tags for better social media previews
5Expand your content to at least 300+ words for better search rankings
6Aim for 2–5 dofollow outbound links per page to demonstrate topical authority
7Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
8Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
9Reduce keyword density from 6.2% to 0.5–2.5% — Google penalizes keyword stuffing. Use synonyms and natural language variations
10Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
Key Findings
1Acceptable response time: 516ms
2Lean HTML document: 25KB
3JavaScript payload (~302KB) is acceptable
4Gzip compression enabled
51 third-party script(s) — manageable count
6Estimated LCP: ~2476ms — within Google's "good" threshold (<2.5s)
7Estimated INP: ~101ms — within Google's "good" threshold (<200ms)
Issues Found
16 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No font-display property found
4No effective Cache-Control header
5Moderate CSS payload (~369KB)
6HTTP/1.1 detected — no multiplexing
7No CDN detected
812 render-blocking CSS files — delays first paint
9Estimated CSS bundle ~489KB — above optimal
10Potentially unused CSS detected (large stylesheet count relative to page complexity)
11Moderate estimated CLS: 0.13 — above 0.1 "good" threshold
12No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or 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
5Preload critical resources (fonts, hero images) with <link rel="preload">
6Add font-display: swap to web font declarations to show fallback text while fonts load
7Set Cache-Control headers with appropriate max-age to leverage browser caching
8Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
9Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
10Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
11Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
12Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
13Audit CSS with Chrome DevTools Coverage tab to identify and remove unused CSS rules
14Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
15Install 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
5Mobile-responsive hamburger menu detected
6Lightweight page (~976KB) — fast on mobile networks
Issues Found
1No theme-color meta tag
2No web app manifest found
3Only 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
4Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Add :active / touch-action CSS for tactile feedback on mobile interactions
Issues Found
1Site does not use HTTPS
2Missing Strict-Transport-Security header
3Missing Content-Security-Policy header
4Missing X-Content-Type-Options header
5Missing X-Frame-Options header
6Missing Referrer-Policy header
7Missing Permissions-Policy header
8Server header exposes technology: Apache
9X-Powered-By header exposes: PHP/7.4.33
101 external link(s) without noopener/noreferrer
11No privacy policy detected
12No cookie consent banner detected
13No Subresource Integrity (SRI) on external scripts
Recommendations to Reach 100%
1Migrate to HTTPS immediately — it's essential for security, SEO, and user trust
2Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
3Implement a Content Security Policy to prevent XSS and injection attacks
4Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
5Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
6Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
7Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
8Add Cross-Origin-Opener-Policy: same-origin-allow-popups
9Add Cross-Origin-Resource-Policy: cross-origin
10Remove or obfuscate the Server header to avoid exposing your technology stack
11Remove X-Powered-By header
12Add rel="noopener noreferrer" to external links for security
13Add a privacy policy link — required by GDPR, CCPA, and builds user trust
14Implement a cookie consent banner for GDPR/ePrivacy compliance
15Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
Key Findings
1Language declared: en
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 1 buttons have accessible labels
54 ARIA-attributed elements found
6No major HTML nesting or validity issues detected
Issues Found
11 of 2 images (50%) missing alt text
2No focus styles detected
Recommendations to Reach 100%
1Add descriptive alt text to all images — use empty alt="" only for decorative images
2Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Key Findings
1Strong semantic markup: header, nav, main, article, footer
21 call-to-action elements detected
3No AI crawlers blocked via meta tags — content accessible to AI search engines
4robots.txt file found
5robots.txt references 1 sitemap(s) — aids AI crawler discoverability
6Good HTML-to-text ratio (46%) — AI crawlers can extract content efficiently
Issues Found
1No structured data (Schema.org) found
2Incomplete social metadata
3No breadcrumb navigation
4No FAQ or Q&A content patterns found
5No sitemap reference found
6No social media links found
7Low RAG-friendliness (28/100) — AI systems cannot anchor into specific sections
8No content freshness signals (dateModified, datePublished, <time> elements)
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
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
6Add links to your social media profiles to strengthen brand entity signals
7Create an llms.txt file to guide AI models on how to access and interpret your content (emerging standard for AI SEO)
8Add id attributes to all H2/H3 headings and wrap content sections in <section id="..."> for vector-embeddable, RAG-friendly content chunks
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Good semantic-to-div ratio: 5 semantic elements
2Good paragraph length for readability and AI parsing
31 external citation(s)
41 call-to-action element(s) detected
5Above-the-fold CTA detected — captures immediate visitor attention
6Clear value proposition detected in heading elements
Issues Found
1Very thin content (195 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Weak E-E-A-T schema signals
5No author or expertise signals
6Insufficient trust signals for conversion optimization
7No 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
4Add structured content (lists, comparison tables) that AI models can easily extract and reference
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
11Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
12Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
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
6thin content — may not provide enough depth for AI engines
7No 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
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
9Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
10Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
11Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1Short paragraphs are well-suited for answer extraction
25 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
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
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
8Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Key Findings
1NAP information detected: phone: 410-255-3539
2Phone number(s) visible: 410-255-3539, 15720244311
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
Issues Found
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite
Recommendations to Reach 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
2Priority schema types to add: Organization, WebSite — these have the highest SEO impact for your page type
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Good semantic element usage (5 semantic elements)
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
3No 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
3Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
Limited-Time Offer
Audit-informed Optimizations for 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.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.