This website audit report analyzes https://charmcityplasticsurgery.com/ across 12 critical dimensions with actionable recommendations.
https://charmcityplasticsurgery.com/
56Needs Workout of 100
Website Audit Report
Charm City Plastic Surgery | Baltimore, MD
May 28, 2026 at 11:04 AM EDT 85ms response HTTPS Secure
Executive Summary
https://charmcityplasticsurgery.com/ scores 56/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, Security. The site has 667 words, 14 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 75/100. Focus on the top recommendations below to improve your score.
85ms
Response Time
667
Word Count
14
Images
108
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is short (42 chars)
2[SEO] Meta description is slightly short (132 chars)
3[SEO] 5 external links missing recommended rel attributes
4[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
5[SEO] 7 dofollow external links — slightly above optimal range
6[SEO] Primary keyword "charm city plastic" not found in H1
7[SEO] Primary keyword missing from first paragraph
8[SEO] Low readability score (14 Flesch) — content is hard to read
9[SEO] OG image dimensions too small for social platforms
10[SEO] High internal link density (148.4/1k words) — may appear spammy
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] Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
6[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
7[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
8[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
9[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
10[Impact: Medium | Effort: Medium] Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
11[Impact: High | Effort: Medium] Reduce internal link density to 2–5 per 1,000 words — excessive linking dilutes individual link value
12[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Plastic Surgery & Aesthetic Care in Baltimore, MD"
2Clean heading hierarchy with no skipped levels
3Canonical URL is set and matches the page URL
4Complete Open Graph tags (title, description, image, url, type)
5Complete Twitter Card tags present
6HTML lang attribute set to "en-US"
7Favicon present
899 internal links help establish site architecture
97 external links provide reference signals
10Content length of 667 words is adequate
11108 total links — within recommended range
12URL length (36 chars) is within optimal range
13No redirect chain — direct URL resolution
14Healthy internal link ratio: 92% of links are internal
15Good keyword alignment between title and H1
16Primary keyword present in URL — good URL optimization
17Moderate E-E-A-T signals (4 indicators)
18og:locale set to "en_US"
19article:published_time present — content freshness signal for social platforms
20article:modified_time present — update recency signal
21Twitter card uses summary_large_image — maximum visual impact
22Optimal keyword density: "charm city plastic" at 1.3% (3 occurrences)
23Low passive voice ratio (3%) — clear, active writing style
24Strong entity salience: Emily Clarke, Pearson Dr, Neurotoxins Dermal Fillers Collagen Stimulators (score: 64)
25Social share buttons detected: ShareThis
26OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Title tag is short (42 chars)
2Meta description is slightly short (132 chars)
35 external links missing recommended rel attributes
4Title and description are identical to Open Graph tags — missed optimization opportunity
57 dofollow external links — slightly above optimal range
6Primary keyword "charm city plastic" not found in H1
7Primary keyword missing from first paragraph
8Low readability score (14 Flesch) — content is hard to read
9OG image dimensions too small for social platforms
10High internal link density (148.4/1k words) — may appear spammy
Recommendations to Reach 100%
1Expand your title to 50–60 characters — Google now favors this range for optimal SERP display (2025-2026)
2Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
3Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
6Include your primary keyword in the H1 heading for strongest on-page SEO signal
7Include your primary keyword naturally in the first paragraph to establish topical relevance early
8Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
9Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
10Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
11Reduce internal link density to 2–5 per 1,000 words — excessive linking dilutes individual link value
12Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
Key Findings
1Excellent server response time: 85ms
28/14 images use lazy loading
3Responsive images with srcset detected
4Preloaded resources: font, font
52 async and 1 deferred scripts
6Cache-Control header with max-age is set
7HTTP/3 (QUIC) detected — fastest connection protocol
8CDN detected: CDN (unidentified) — reduces latency for global users
9Brotli compression enabled — best-in-class compression
102 third-party script(s) — manageable count
112 font(s) preloaded for faster text rendering
12Estimated INP: ~190ms — within Google's "good" threshold (<200ms)
13Variable fonts detected — reduces total font file downloads
14Good analytics setup: GA4 + event tracking
Issues Found
1Large HTML document: 318KB
216 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
4No font-display property found
515 inline <style> blocks
617 inline scripts
7Large CSS payload (~1370KB across 41 files) — slows rendering
8Moderate JavaScript payload (~917KB)
941 render-blocking CSS files — delays first paint
10Estimated CSS bundle ~1780KB — above optimal
11Poor estimated LCP: ~5365ms — exceeds 4s threshold
12Moderate estimated CLS: 0.22 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Reduce HTML size by minifying markup, removing inline styles, and deferring non-critical content
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
6Extract inline styles into external CSS files for better caching and maintainability
7Move inline scripts to external files with defer attributes
8Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
9Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
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
12Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
13Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
14Complete your analytics setup: add GTM for tag management and configure custom event tracking for deeper insights
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
68 images with lazy loading benefit mobile data users
7Mobile-responsive hamburger menu detected
8Touch feedback CSS detected (active states or touch-action)
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)
5Estimated page weight ~3895KB — heavy for mobile data plans
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
7Reduce page weight below 2MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Key Findings
1HTTPS enabled — encrypted connection
2Server via CDN proxy (cloudflare) — header added by infrastructure, not application
3No cookie security issues detected
4Privacy policy link detected
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
7X-Powered-By header exposes: WP Engine
85 external link(s) without noopener/noreferrer
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
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 X-Powered-By header
10Add rel="noopener noreferrer" to external links for security
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 14 images have alt attributes
5All 53 buttons have accessible labels
6Rich ARIA implementation: 66 elements with ARIA attributes
7Focus styles detected for keyboard navigation
Issues Found
11 minor HTML validity issue(s)
21 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Review and fix HTML structure issues for better accessibility and cross-browser compatibility
2Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
11 schema block(s): BreadcrumbList, LocalBusiness, Organization, WebPage, WebSite
2Strong semantic markup: header, nav, main, article, footer
3Complete social metadata (OG + Twitter Card)
4Social presence signals: facebook, instagram
59 call-to-action elements detected
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7robots.txt file found
8robots.txt references 3 sitemap(s) — aids AI crawler discoverability
9High RAG-friendliness (60/100): 0 headings with IDs, 9 section anchors
10Content provenance signals detected (citations with sources, attributed claims)
11Content freshness signals present (dateModified/datePublished/time elements)
12Good HTML-to-text ratio (51%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
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
6Use <strong> and <em> tags to highlight key entities, concepts, and terms
7Create an llms.txt file to guide AI models on how to access and interpret your content (emerging standard for AI SEO)
Key Findings
1Moderate content depth (667 words)
2Structured content: 22 lists, 0 tables — easily parsed by AI
35 external citations — strong reference density for AI model training
4Trust signals present: HTTPS Security, Privacy Policy
5Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Low semantic markup ratio — 305 divs vs 9 semantic elements
4Weak E-E-A-T schema signals
5No author or expertise signals
6No clear call-to-action elements detected
7No CTA above the fold
8No social proof elements
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
4Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
5Add Speakable schema markup to help voice assistants identify the most important content
6Include specific statistics, percentages, and data points that AI models can extract and cite in responses
7Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
8Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
9Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
10Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
11Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
122 lists provide scannable, AI-friendly content
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
3Insufficient structured data for generative engine context
4No hreflang tags — generative engines cannot determine language/region targeting
5No statistics or data points in substantial content
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
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
7Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
8Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
9Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
10Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
122 lists provide scannable answers for People Also Ask
210 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
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
Key Findings
1NAP information detected: phone: 443-885-9644
2Phone number(s) visible: 443-885-9644, 4716768789
3LocalBusiness schema: LocalBusiness
4Business hours/opening hours detected
Issues Found
1No Google Maps embed
2No address microdata
3No geo meta tags
4No review/rating schema
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
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
5Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
6Add areaServed property to your LocalBusiness schema to define your service radius
Key Findings
11 JSON-LD block(s) with types: BreadcrumbList, LocalBusiness, Organization, WebPage, WebSite
2Comprehensive schema implementation
3Strong top-tier schema coverage: LocalBusiness, 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
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 77%
Recommendations to Reach 100%
1Migrate all structured data to JSON-LD format — it's easier to maintain, debug, and is Google's preferred format
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Add missing high-impact schemas: Review
4Add FAQPage schema to FAQ content — enables expandable rich results
5Consider adding HowTo schema for instructional content
6Add more properties to schema types — aim for at least 5 meaningful properties per type
7Fill in missing recommended properties for each schema type
8Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
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
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Low semantic-to-div ratio — 305 divs vs 9 semantic elements
4Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
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
4Ensure sticky headers/footers do not fully obscure the keyboard focus indicator. Use scroll-padding-top or ensure focus remains visible under overlapping elements (WCAG 2.4.11 AA)
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.