This website audit report analyzes https://www.theplasticsurgerycenter.com/ across 12 critical dimensions with actionable recommendations.
https://www.theplasticsurgerycenter.com/
46Poorout of 100
Website Audit Report
Plastic Surgery Maryland | Plastic Surgeon Near Me Baltimore
May 28, 2026 at 11:06 AM EDT 255ms response HTTPS Secure
Executive Summary
https://www.theplasticsurgerycenter.com/ scores 46/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 918 words, 27 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 50/100. Focus on the top recommendations below to improve your score.
255ms
Response Time
918
Word Count
27
Images
186
Links
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Multiple H1 tags found (2)
2[SEO] Missing OG tags: og:image
3[SEO] Missing Twitter tags: twitter:title, twitter:description, twitter:image
4[SEO] 4 empty/unlabeled links found
5[SEO] High link count (186) — approaching search engine limits
6[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
7[SEO] Title and H1 share no keywords — misaligned topic signals
8[SEO] Primary keyword "plastic surgery maryland" not found in H1
9[SEO] Primary keyword missing from first paragraph
10[SEO] High internal link density (177.6/1k words) — may appear spammy
Top Recommendations
1[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
2[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:image
3[Impact: Medium | Effort: Medium] Add descriptive anchor text to all links for better SEO and accessibility
4[Impact: Medium | Effort: Medium] Aim for ≤100–150 total links per page including nav, footer, and content links
5[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
8[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
9[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
10[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
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] Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
Detailed Category Analysis
Key Findings
1Title tag is 60 characters — within optimal 50–60 range (Google 2025-2026)
2Meta description is 157 characters — within optimal 140–160 range (2025-2026)
3Clean heading hierarchy with no skipped levels
4Canonical URL is set and matches the page URL
5HTML lang attribute set to "en-US"
6Favicon present
7163 internal links help establish site architecture
820 external links provide reference signals
9Content length of 918 words is adequate
10URL length (40 chars) is within optimal range
11No redirect chain — direct URL resolution
12Healthy internal link ratio: 88% of links are internal
13Optimal dofollow outbound links: 3 (ideal 2–5 per page for link authority signals)
14Strong E-E-A-T signals detected (5 indicators)
15og:locale set to "en_US"
16article:modified_time present — update recency signal
17Twitter card uses summary_large_image — maximum visual impact
18Low passive voice ratio (2%) — clear, active writing style
19Table of Contents detected — improves dwell time and jump-link navigation
20Strong entity salience: Last Name, Brazilian Butt Lift, Procedure Of (score: 56)
21Social share buttons detected: ShareThis
Issues Found
1Multiple H1 tags found (2)
2Missing OG tags: og:image
3Missing Twitter tags: twitter:title, twitter:description, twitter:image
44 empty/unlabeled links found
5High link count (186) — approaching search engine limits
6Title and description are identical to Open Graph tags — missed optimization opportunity
7Title and H1 share no keywords — misaligned topic signals
8Primary keyword "plastic surgery maryland" not found in H1
9Primary keyword missing from first paragraph
10High internal link density (177.6/1k words) — may appear spammy
11Low keyword density (0.3%) for "plastic surgery maryland"
Recommendations to Reach 100%
1Consolidate to a single H1 tag — use H2–H6 for subtopics
2Add missing Open Graph tags: og:image
3Add descriptive anchor text to all links for better SEO and accessibility
4Aim for ≤100–150 total links per page including nav, footer, and content links
5Customize og:title and og:description separately from page title/meta description for better social sharing CTR
6Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7Include your primary keyword in the H1 heading for strongest on-page SEO signal
8Include your primary keyword naturally in the first paragraph to establish topical relevance early
9Include your primary keyword in the URL slug for improved crawlability and click-through rates
10Add <meta property="article:published_time"> for content freshness signals in social shares
11Reduce internal link density to 2–5 per 1,000 words — excessive linking dilutes individual link value
12Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
13Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
14OG sharing completeness at 83% — add missing tags for better social previews
Key Findings
1Excellent server response time: 255ms
2HTML size is 256KB — acceptable
3font-display property detected — reduces invisible text during font loading
43 async and 8 deferred scripts
5Cache-Control header with max-age is set
6HTTP/3 (QUIC) detected — fastest connection protocol
7CDN detected: CDN (unidentified) — reduces latency for global users
8Brotli compression enabled — best-in-class compression
9Good analytics setup: GA4 + event tracking
Issues Found
127 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5Only 3/27 images have width/height attributes
614 inline <style> blocks
759 inline scripts
8Large CSS payload (~826KB across 26 files) — slows rendering
9Heavy JavaScript payload (~1981KB across 38 files)
108 third-party scripts detected
1111 font files loaded — excessive font weight
1226 render-blocking CSS files — delays first paint
13Estimated CSS bundle ~1086KB — above optimal
14Estimated JS bundle ~2361KB — heavy payload
15Potential long-task scripts: Inline script (~17KB)
16Poor estimated LCP: ~5435ms — exceeds 4s threshold
17High estimated CLS: 0.35 — exceeds Google's 0.25 threshold
18Estimated INP: ~280ms — needs improvement (goal: <200ms)
19Web fonts loaded without preload — causes FOIT/FOUT flash
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add loading="lazy" to below-the-fold images to improve initial page load
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Use srcset and sizes attributes on images to serve appropriately sized images per device
5Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
6Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
7Preload critical resources (fonts, hero images) with <link rel="preload">
8Extract inline styles into external CSS files for better caching and maintainability
9Move inline scripts to external files with defer attributes
10Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
11Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
12Review third-party scripts and defer non-essential ones to improve page load time
13Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
14Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
15Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
16Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
17Reduce JS bundle with code splitting, tree shaking, and dynamic imports. Target <500KB initial JS
18Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
19Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
20Fix CLS: add explicit width/height to all images and iframes, preload fonts, avoid injecting content above existing content
21Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
22Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
23Complete 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
5Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3No responsive image srcset — mobile users may download oversized images
4Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
5Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
6Estimated page weight ~5053KB — 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
4Implement srcset to serve smaller images on mobile devices, saving bandwidth
5Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
6Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
7Add env(safe-area-inset-*) CSS for proper display on notched/island devices
8Add :active / touch-action CSS for tactile feedback on mobile interactions
9Reduce 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
83 external link(s) without noopener/noreferrer
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11Outdated libraries detected: jQuery 1.11.3 (latest 3.7+)
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
13Update outdated JavaScript libraries to latest versions — older versions have known security vulnerabilities (CVEs)
14Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Key Findings
1Language declared: en-US
2All 12 buttons have accessible labels
3Rich ARIA implementation: 164 elements with ARIA attributes
4Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
2Missing landmarks: main, nav
36 of 27 images (22%) missing alt text
42 form(s) missing proper labels
51 iframe(s) missing title
64 minor HTML validity issue(s)
724 images missing explicit dimensions — causes layout shifts for screen reader users
81 focusable element(s) inside aria-hidden containers
949 duplicate ID(s) — breaks ARIA references and label associations
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>
3Add descriptive alt text to all images — use empty alt="" only for decorative images
4Add <label> elements associated with every form input via for/id attributes
5Add descriptive title attributes to all iframes
6Review and fix HTML structure issues for better accessibility and cross-browser compatibility
7Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
8Remove focusable elements (links, buttons, inputs) from aria-hidden regions — they trap keyboard users in invisible content
9Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
11 schema block(s): WebPage, BreadcrumbList, WebSite, Organization
2Strong semantic markup: header, section, footer, aside, figure
3Complete social metadata (OG + Twitter Card)
4Sitemap reference detected
5Social presence signals: facebook, instagram, twitter, youtube
610 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 1 sitemap(s) — aids AI crawler discoverability
10High RAG-friendliness (100/100): 0 headings with IDs, 32 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
12Content freshness signals present (dateModified/datePublished/time elements)
13Good HTML-to-text ratio (35%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns 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
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Create 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 (918 words)
2Good semantic-to-div ratio: 17 semantic elements
3Structured content: 35 lists, 0 tables — easily parsed by AI
49 external citations — strong reference density for AI model training
5Strong CRO: 9 clear call-to-action elements detected
6Above-the-fold CTA detected — captures immediate visitor attention
7Good form usability score: 100/100
8Trust signals present: Reviews/Testimonials, HTTPS Security, Privacy Policy
9Social proof elements detected — builds credibility and conversion confidence
10Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Weak E-E-A-T schema signals
4Paragraphs are too long for optimal AI consumption
5No author or expertise signals
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
3Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
4Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
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
Key Findings
135 lists provide scannable, AI-friendly content
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
4paragraphs may be too long for featured snippets
5No hreflang tags — generative engines cannot determine language/region targeting
6No 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
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
135 lists provide scannable answers for People Also Ask
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
4Paragraphs too long for answer engine extraction
5No breadcrumb navigation
6No direct answer patterns ("X is defined as...", "X refers to...")
7Paragraphs too long for voice assistant extraction
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
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
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
9Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Key Findings
1NAP information detected: phone: 5595528, email: [email protected]
2Phone number(s) visible: 5595528, 575-5476229
3Email address found: [email protected]
4Google Maps embed present — provides visual location confirmation
Issues Found
1No LocalBusiness structured data
2No address microdata
3No geo meta tags
4No review/rating schema
Recommendations to Reach 100%
1Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
2Add PostalAddress schema or itemprop="address" microdata to your address elements
3Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
4Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
11 JSON-LD block(s) with types: WebPage, BreadcrumbList, WebSite, Organization
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Strong top-tier schema coverage: Organization, BreadcrumbList, WebSite
5BreadcrumbList schema → breadcrumb rich results
6Rich schema diversity: 4 distinct types with properties
7Average schema property completeness: 81% — well-implemented
8Rich results potential: Breadcrumbs
9SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
1BreadcrumbList has very few properties (1)
2BreadcrumbList missing common identifiers (name/headline/url)
3No sameAs properties in schema — missing entity disambiguation
Recommendations to Reach 100%
1Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
2Add missing high-impact schemas: Review
3Add FAQPage schema to FAQ content — enables expandable rich results
4Consider adding HowTo schema for instructional content
5Add more properties to schema types — aim for at least 5 meaningful properties per type
6Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Form error/validation feedback detected
3Relative units (rem/em/clamp) detected — supports text resizing
4Good semantic element usage (17 semantic elements)
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Form error identification mechanisms present (WCAG 3.3.1)
9Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
38 elements with tabindex="-1" — may hide content from keyboard users
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
3Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
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)
5Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
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.