Website Audit Report

Source diagnostic wording is preserved.

1. [Impact 3/3 · v6:psi-performance] Review the Lighthouse diagnostics for this category and retest.

2. Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression

3. Set a Cache-Control header with an appropriate max-age (and immutable for versioned assets) to enable browser caching [Impact: Medium | Effort: Low]

4. Add width and height attributes (or CSS aspect-ratio) to every image to reserve space and prevent layout shift [Impact: Medium | Effort: Low]

5. Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.

Evidence and checks

Excellent server response time: 296ms

HTML size is 101KB — acceptable

2 framework-managed script(s) — optimized by build pipeline

1/2 images use lazy loading

Modern image formats (WebP/AVIF) detected

Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com, https://www.googletagmanager.com

Preloaded resources: image, script, script

font-display property detected — reduces invisible text during font loading

16 async and 0 deferred scripts

Cache-Control header with max-age is set

11 inline scripts (framework hydration/data — standard for SSR apps)

Lean CSS payload (~60KB)

JavaScript payload (~922KB) is acceptable for framework app

HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level

CDN detected: Cloudflare — reduces latency for global users

Gzip compression enabled

1 third-party script(s) — manageable count

8 resource hints (preconnect/prefetch/preload) optimize loading

Variable fonts detected — reduces total font file downloads

Good analytics setup: GA4 + event tracking

DOM size is reasonable (650 elements)

Lab-proxy estimates — Speed Index ~1692ms, TTI ~4262ms, TBT ~1026ms (estimated from resource composition, not third-party field data)

Runtime JavaScript was not executed by this HTML scan. Use the JavaScript error diagnostics on the auditor page to analyze browser evidence; absence of logs is not a pass.

v6:psi-performance · Lighthouse Performance: 87/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

1. Consider implementing a service worker for offline support and faster repeat visits

2. Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content

3. Add a service worker to complete PWA install requirements (manifest + SW + HTTPS)

4. Add env(safe-area-inset-*) CSS for proper display on notched/island devices

5. Add :active / touch-action CSS for tactile feedback on mobile interactions

6. Mobile/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.

Evidence and checks

Viewport meta tag present: width=device-width, initial-scale=1

HTML5 doctype declared

Character encoding declared

Theme color meta tag set for mobile browsers

Web app manifest detected — PWA-ready

Apple touch icons present

1 images with lazy loading benefit mobile data users

Mobile-responsive hamburger menu detected

Web app manifest includes 6 icon sizes — good coverage

1 image(s) without explicit width/height — most impactful for layout stability (CLS) on mobile (see Performance for remediation)

v6:psi-mobile · Lighthouse mobile usability evidence: 100/100 — [{"id":"meta-viewport","score":100,"title":"`[user-scalable=\"no\"]` is not used in the `<meta name=\"viewport\">` element and the `[maximum-scale]` attribute is not less than 5."},{"id":"target-size","score":100,"title":"Touch targets have sufficient size and spacing."}]

Source diagnostic wording is preserved.

1. Include your primary keyword in the H1 heading for strongest on-page SEO signal

2. Include your primary keyword naturally in the first paragraph to establish topical relevance early

3. Include your primary keyword in the URL slug for improved crawlability and click-through rates

4. Add <meta property="article:published_time"> for content freshness signals in social shares

5. Add <meta property="article:modified_time"> to signal content freshness

6. Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text

7. Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals

8. SEO (E-E-A-T): no author linkage or sameAs identity markup detected. Add a verifiable author byline with rel="author" and sameAs links to strengthen Experience/Expertise signals.

9. SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.

Evidence and checks

Title tag is 52 characters — within optimal 50–60 range (Google 2025-2026)

Meta description is 159 characters — within optimal 140–160 range (2025-2026)

Single H1 tag present: "Find an Accredited Addiction Treatment CenterNear You"

Clean heading hierarchy with no skipped levels

Canonical URL is set and matches the page URL

Complete Open Graph tags (title, description, image, url, type)

Complete Twitter Card tags present

HTML lang attribute set to "en"

Favicon present

23 internal links help establish site architecture

4 external links provide reference signals

Content length of 1231 words is adequate

28 total links — within recommended range

URL length (34 chars) is within optimal range

All external links have proper rel attributes (nofollow/noopener)

No redirect chain — direct URL resolution

Healthy internal link ratio: 82% of links are internal

Good anchor text diversity: 80% unique anchor texts

Good keyword alignment between title and H1

Optimal dofollow outbound links: 4 (ideal 2–5 per page for link authority signals)

Primary keyword not in URL — acceptable for homepage/root URLs

Moderate E-E-A-T signals (3 indicators)

og:locale set to "en_US"

OG image uses WebP format — optimal for quality/size balance

OG image dimensions ≥1200×630px — optimal for all platforms

Twitter card uses summary_large_image — maximum visual impact

Internal link density (18.7/1k words) — above average but acceptable for navigation-heavy pages

Low passive voice ratio (12%) — clear, active writing style

Zero-click optimized: 0 TL;DR/summary block(s) + 6 definition-style lead paragraph(s)

Moderate entity presence: Joint Commission, Listed Connecting People, Accredited Addiction Treatment

OG sharing completeness: 100% — all tags present for optimal social previews

2 hreflang annotation(s) present for international targeting

Character encoding declared as UTF-8

v6:description-presence · Meta description presence: 100/100 — Search a verified directory of accredited addiction treatment centers. Compare evidence-based programs, levels of care, and specialties to find the right help.

v6:description-length · Meta description length: 100/100 — 159 characters; diagnostic range 70–170, not a ranking rule

v6:description-quality · Meta description quality heuristic: 100/100 — Placeholder and lexical-diversity checks; not semantic quality certification

v6:psi-seo · Lighthouse SEO: 100/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

Evidence and checks

v6:technical-status · Document HTTP status: 100/100 — HTTP 200

v6:technical-canonical · Canonical syntax: 100/100 — https://addictiontreatment.center

v6:technical-language · Document language: 100/100 — en

v6:technical-refresh · Meta refresh: 100/100 — Meta refresh count: 0

Source diagnostic wording is preserved.

1. Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks

2. Implement a cookie consent banner for GDPR/ePrivacy compliance

3. Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks

4. Strengthen CSP: consider nonce-based policies when feasible

5. When feasible, migrate to nonce-based CSP for inline scripts/styles

6. If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]

7. A09 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.

Evidence and checks

HTTPS enabled — encrypted connection

HTTP → HTTPS 301 redirect detected — properly forces secure connections

HSTS header present — enforces HTTPS

Content Security Policy header present

X-Content-Type-Options: nosniff is set

Referrer-Policy set to: strict-origin-when-cross-origin

Permissions-Policy header restricts browser features

Cross-Origin-Opener-Policy set

Cross-Origin-Resource-Policy set

Server via CDN proxy (cloudflare) — header added by infrastructure, not application

All external links have security-safe rel attributes

HSTS with preload and adequate max-age — eligible for browser preload list

No cookie security issues detected

Privacy policy link detected

CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts

CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks

Permissions-Policy restricts 7 browser features (camera, microphone, geolocation, payment)

No server software/technology fingerprints exposed in headers or markup

security.txt present and valid (/.well-known/security.txt) — provides a channel for vulnerability disclosure

No stack traces or sensitive error details exposed in responses

No obvious secret/API-key patterns exposed in page source

18 script resource(s) catalogued for software-composition review

No common sensitive paths (.git, .env, server-status, …) were publicly accessible

Source diagnostic wording is preserved.

1. Ensure all text meets WCAG AA contrast ratio of at least 4.5:1

2. Review HTML structure for any non-framework-related nesting issues

3. Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.

Evidence and checks

Language declared: en

Skip navigation link present

All key landmarks present (main, nav, footer)

All 2 images have alt attributes

All 3 buttons have accessible labels

Rich ARIA implementation: 21 elements with ARIA attributes

Focus styles detected for keyboard navigation

4 minor HTML validity issue(s) — common in modern framework component patterns

1 table(s) have captions/labels

v6:psi-accessibility · Lighthouse Accessibility: 91/100 — Mobile-strategy Lighthouse category

Source diagnostic wording is preserved.

1. Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features

2. Add missing high-impact schemas: HowTo

3. Consider adding HowTo schema for instructional content

4. Add more properties to schema types — aim for at least 5 meaningful properties per type

5. Add more properties to schema types — aim for at least 5 meaningful properties per type

6. Add more properties to schema types — aim for at least 5 meaningful properties per type

7. Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles

8. Schema.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.

Evidence and checks

7 JSON-LD block(s) with types: Organization, MedicalOrganization, WebSite, BreadcrumbList, MedicalWebPage, FAQPage, Organization, WebPage

All structured data uses JSON-LD format — Google's recommended format

Comprehensive schema implementation

Strong top-tier schema coverage: Organization, FAQPage, BreadcrumbList, WebSite

BreadcrumbList schema → breadcrumb rich results

FAQPage schema → expandable FAQ rich results

Rich schema diversity: 7 distinct types with properties

Average schema property completeness: 86% — well-implemented

Rich results potential: FAQ, Breadcrumbs

Schema nesting depth: 2 levels — rich entity relationships

SearchAction schema present. Google retired the sitelinks search box in November 2024; this markup does not establish eligibility for that feature.

v6:social-tags · Open Graph and Twitter metadata: 100/100 — Four core sharing tags checked; not a direct ranking factor

Source diagnostic wording is preserved.

1. Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals

2. Add links to your social media profiles to strengthen brand entity signals

3. Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness

4. Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals

5. Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates

6. Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing

7. Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs

Evidence and checks

Rich structured data: 7 schema blocks (Organization, MedicalOrganization, WebSite, BreadcrumbList, MedicalWebPage)

Hreflang tags: en-us, x-default

Strong semantic markup: header, nav, main, section, article, time, mark, figure, figcaption, details, summary, aside, footer

Complete social metadata (OG + Twitter Card)

FAQ/Q&A content patterns detected — highly valuable for AI citation

Sitemap reference detected

4 call-to-action elements detected

No AI crawlers blocked via meta tags — content accessible to AI search engines

robots.txt file found

robots.txt references 1 sitemap(s) — aids AI crawler discoverability

llms.txt detected (score: 85/100, quality: comprehensive)

llms-full.txt companion file detected (6KB)

llms.txt has proper title and description block

llms.txt has 6 well-organized sections

llms.txt references 5 URLs for AI navigation

llms.txt includes service/product catalog

llms.txt uses proper Markdown formatting for machine readability

llms.txt links to detailed documentation (llms-full.txt)

llms.txt referenced in HTML for discoverability

llms.txt uses canonical domain in URLs

High RAG-friendliness (97/100): 10 headings with IDs, 7 section anchors

Content provenance signals detected (citations with sources, attributed claims)

Content freshness signals present (dateModified/datePublished/time elements)

Good HTML-to-text ratio (36%) — AI crawlers can extract content efficiently

Moderate content depth (1231 words)

Rich Q&A content (14 FAQ/accordion elements)

5 emphasized entities

Good semantic-to-div ratio: 41 semantic elements

Structured content: 3 lists, 1 tables — easily parsed by AI

Speakable schema detected — content optimized for voice assistants

4 external citation(s)

3 blockquotes/quotes enhance authority signals

1 call-to-action element(s) detected

Trust signals present: HTTPS Security, Privacy Policy

Clear value proposition detected in heading elements

Source diagnostic wording is preserved.

1. Include unique statistics, expert quotes, and original insights that generative AI would want to cite

2. Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise

Evidence and checks

Direct question-answer patterns found — good for Google SGE and AI citations

1 comparison/data table(s) — highly extractable by AI

3 lists detected

How-to instructional patterns detected — valued by AI answer engines

1 definition list(s) — excellent for AI glossary extraction

Comprehensive content depth (1231 words) supports AI citation

7 schema blocks help AI engines understand content context

Hreflang includes self-referencing tag

x-default hreflang fallback present

4 original data elements (charts, figures, data tables)

3 quotation elements enhance credibility for GEO

Source diagnostic wording is preserved.

1. Add HowTo schema to your instructional content for rich result eligibility

2. Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals

3. Consider adding video content with VideoObject schema for multimedia search results

4. Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results

5. AEO: 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.

Evidence and checks

FAQPage schema markup present — eligible for rich FAQ results

Question-answer heading patterns support featured snippet capture

Speakable schema supports voice search optimization

3 lists provide scannable answers for People Also Ask

23 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction

Source diagnostic wording is preserved.

1. Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates

2. Add an embedded Google Map to your contact or about page for local search signals

3. Add PostalAddress schema or itemprop="address" microdata to your address elements

4. Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates

5. Local SEO: local business signals present but no explicit city/region in the title, H1 or opening paragraph. Add "City, State" to your title/H1 and intro to reinforce local relevance.

Evidence and checks

NAP information detected: phone: +1-800-662-4357, email: [email protected]

Phone number(s) visible: +1-800-662-4357, 18006624357

Email address found: [email protected]

Geo meta tags present for location targeting

Service area defined in schema

Source diagnostic wording is preserved.

1. Audit color contrast ratios — ensure at least 4.5:1 for normal text and 3:1 for large text (WCAG 1.4.3)

2. Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)

Evidence and checks

prefers-reduced-motion support detected — respects user motion preferences

High contrast / forced-colors mode supported

Links are visually distinguishable (underline or decoration detected)

Relative units (rem/em/clamp) detected — supports text resizing

Good semantic element usage (41 semantic elements)

Focus styles detected for keyboard navigation visibility

Page language declared — aids assistive technology

All ARIA roles are valid

Moderate cognitive load — acceptable for interactive modern web apps with rich UI patterns

Focus not obscured by sticky/fixed elements (WCAG 2.4.11)

prefers-reduced-motion detected but enforcement unclear

Source diagnostic wording is preserved.

1. [Impact 3/3 · v6:cwv-lcp] Prioritize above-fold resources and remove render-blocking dependencies.

Evidence and checks

v6:cwv-lcp · LCP: 53/100 — 3901.036762240226 ms; lab

v6:cwv-inp · INP: unavailable — Unavailable; not estimated

v6:cwv-cls · CLS: 100/100 — 0 ratio; lab

v6:cwv-fcp · FCP: 99/100 — 1831.0205647287507 ms; lab

v6:cwv-ttfb · TTFB: 100/100 — 4 ms; lab

v6:cwv-tbt · TBT: 100/100 — 18.5 ms; lab

Source diagnostic wording is preserved.

Evidence and checks

v6:robots-valid · Robots syntax and response: 100/100 — HTTP 200; 404 means no robots file

v6:robots-access · Googlebot path access: 100/100 — /

v6:meta-indexability · Meta robots indexability: 100/100 — index, follow

v6:header-indexability · X-Robots-Tag indexability: 100/100 — No restrictive response header

v6:crawl-budget · Parameter crawl signals: 100/100 — 0 parameterized internal destinations

Source diagnostic wording is preserved.

Evidence and checks

v6:sitemap-detection · Sitemap response: 100/100 — HTTP 200

v6:sitemap-xml · Sitemap XML validity: 100/100 — urlset

v6:sitemap-count · Sitemap entry count: 100/100 — 19 URLs in fetched document

v6:sitemap-lastmod · Lastmod integrity / freshness: 100/100 — 19 dated entries; 0 invalid/future; oldest age days: 135

v6:sitemap-robots-reference · Sitemap discovery in robots: 100/100 — Referenced

Source diagnostic wording is preserved.

Evidence and checks

v6:internal-links · Internal destinations: 100/100 — 10 unique destinations

v6:link-depth · Linked URL path depth: 100/100 — URL path depth ≤4 proxy; click depth beyond sampled edges is unknown

v6:external-hygiene · External transport quality: 100/100 — 4 unique external destinations; 0 HTTP links. Authority/relevance not inferred.

v6:broken-links · Broken link sample: 100/100 — [{"url":"https://addictiontreatment.center/","status":200,"depth":1,"outgoing":28},{"url":"https://addictiontreatment.center/directory","status":200,"depth":1,"outgoing":20},{"url":"https://addictiontreatment.center/blog","status":200,"depth":1,"outgoing":22},{"url":"https://addictiontreatment.center/contact","status":200,"depth":1,"outgoing":23},{"url":"https://www.samhsa.gov/find-help/national-helpline","status":200,"depth":1,"outgoing":null},{"url":"https://nida.nih.gov/","status":200,"depth":1,"outgoing":null}]

v6:anchor-diversity · Descriptive anchor diversity: 100/100 — 22 distinct anchors; 0 empty/generic of 27