This website audit report analyzes https://www.dentisteaston.com/ across 12 critical dimensions with actionable recommendations.
https://www.dentisteaston.com/
43Poorout of 100
Website Audit Report
Dentists | Easton, MD | Nicholas F. DiBenedetto, DDS
September 16, 2026 at 11:39 AM EDT 274ms response HTTPS Secure
Executive Summary
https://www.dentisteaston.com/ scores 43/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 291 words, 3 images, and 0 schema blocks. Data confidence: 75%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
274ms
Response Time
291
Word Count
3
Images
46
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is short (97 chars)
2[SEO] Multiple H1 tags found (3)
3[SEO] Heading hierarchy gaps: h2 → h6 (skips h3)
4[SEO] Missing OG tags: og:image
5[SEO] Missing Twitter tags: twitter:image
6[SEO] Thin content (291 words)
7[SEO] Deprecated HTML tags found: <font> (19)
8[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
9[SEO] Title and H1 share no keywords — misaligned topic signals
10[SEO] Primary keyword "dentists" not found in H1
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:image
5[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
6[Impact: Medium | Effort: Medium] Replace deprecated HTML tags with modern semantic equivalents
7[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
8[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
9[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
10[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
11[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
12[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
Detailed Category Analysis
Key Findings
1Title tag is 52 characters — within optimal 50–60 range (Google 2025-2026)
2Canonical URL is set and matches the page URL
3HTML lang attribute set to "en"
4Favicon present
537 internal links help establish site architecture
64 external links provide reference signals
746 total links — within recommended range
8URL length (30 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 80% of links are internal
11Good anchor text diversity: 64% unique anchor texts
12Optimal dofollow outbound links: 2 (ideal 2–5 per page for link authority signals)
13Primary keyword not in URL — acceptable for homepage/root URLs
14Moderate entity presence: Contact Insurance, General Dentistry Surgical Procedures Additional Services, Closed Monday
15Character encoding declared as UTF-8
Issues Found
1Meta description is short (97 chars)
2Multiple H1 tags found (3)
3Heading hierarchy gaps: h2 → h6 (skips h3)
4Missing OG tags: og:image
5Missing Twitter tags: twitter:image
6Thin content (291 words)
7Deprecated HTML tags found: <font> (19)
8Title and description are identical to Open Graph tags — missed optimization opportunity
9Title and H1 share no keywords — misaligned topic signals
10Primary keyword "dentists" not found in H1
11Primary keyword missing from first paragraph
12Weak E-E-A-T signals (1 indicators)
13Low readability score (21 Flesch) — content is hard to read
14Missing og:locale tag — social platforms may guess language/region
15Primary keyword "dentists" not found in body content
16Moderate passive voice (19%)
17No social sharing buttons/widgets detected
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Consolidate to a single H1 tag — use H2–H6 for subtopics
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4Add missing Open Graph tags: og:image
5Expand your content to at least 300+ words for better search rankings
6Replace deprecated HTML tags with modern semantic equivalents
7Customize og:title and og:description separately from page title/meta description for better social sharing CTR
8Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
9Include your primary keyword in the H1 heading for strongest on-page SEO signal
10Include your primary keyword naturally in the first paragraph to establish topical relevance early
11Include your primary keyword in the URL slug for improved crawlability and click-through rates
12Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
13Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
14Link to a Contact page — essential trust signal for E-E-A-T and local SEO
15Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
16Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
17Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
18Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
19Reduce passive voice to under 15% for clearer, more engaging content that AI and readers prefer
20Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
21OG sharing completeness at 67% — add missing tags for better social previews
22SEO (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.
23SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Excellent server response time: 274ms
2HTML size is 113KB — acceptable
3Most images have explicit width/height attributes (prevents layout shift)
4Preconnect hints for: https://irp.cdn-website.com, https://irp.cdn-website.com, https://static.cdn-website.com
5Preloaded resources: style, style, style, style, style
6font-display property detected — reduces invisible text during font loading
7Lean CSS payload (~37KB)
8JavaScript payload (~231KB) is acceptable
9Gzip compression enabled
104 third-party script(s) — manageable count
118 resource hints (preconnect/prefetch/preload) optimize loading
12Estimated LCP: ~474ms — within Google's "good" threshold (<2.5s)
13Estimated INP: ~107ms — within Google's "good" threshold (<200ms)
14Alternative analytics platform detected (Plausible/Umami/Matomo)
15DOM size is reasonable (430 elements)
16Lab-proxy estimates — Speed Index ~1527ms, TTI ~1786ms, TBT ~432ms (estimated from resource composition, not third-party field data)
Issues Found
14 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No effective Cache-Control header
417 inline <style> blocks
519 inline scripts
6HTTP/1.1 detected — no multiplexing
7No CDN detected
8Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
9Web fonts loaded without preload — causes FOIT/FOUT flash
10Inline JavaScript does not appear minified
11No efficient cache policy (Cache-Control max-age) on the main document
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Convert images to WebP or AVIF format for 30–50% file size reduction
3Set Cache-Control headers with appropriate max-age to leverage browser caching
4Extract inline styles into external CSS files for better caching and maintainability
5Move inline scripts to external files with defer attributes
6Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
7Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
8Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
9Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
10Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
11Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
12Minify JavaScript to reduce parse and transfer time [Impact: Low | Effort: Low]
13Set a Cache-Control header with an appropriate max-age (and immutable for versioned assets) to enable browser caching [Impact: Medium | Effort: Low]
14Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
15Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
Key Findings
1Viewport meta tag present: initial-scale=1, minimum-scale=1, maximum-scale=5, viewport-fit=cover
2HTML5 doctype declared
3Character encoding declared
4Service worker detected — offline capability possible
5Lightweight page (~571KB) — fast on mobile networks
Issues Found
1Viewport does not include width=device-width
2No theme-color meta tag
3No web app manifest found
4Missing Apple touch icon
5Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
6Only 1 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recommendations to Reach 100%
1Set viewport to width=device-width, initial-scale=1 for proper mobile scaling
2Add <meta name="theme-color"> for browser chrome styling on mobile
3Create a manifest.json for PWA capabilities and add-to-homescreen support
4Add <link rel="apple-touch-icon"> for iOS homescreen icons
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
9Mobile/PWA: incomplete Apple web-app meta tags (missing status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3Content Security Policy header present
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Server via CDN proxy (nginx) — header added by infrastructure, not application
7HSTS with preload and adequate max-age — eligible for browser preload list
8No cookie security issues detected
9Privacy policy link detected
10CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts
11jQuery 3.7.0 — current version
12No stack traces or sensitive error details exposed in responses
13No obvious secret/API-key patterns exposed in page source
14Client-side library inventory (SBOM): jQuery 3.7.0
154 script resource(s) catalogued for software-composition review
16No common sensitive paths (.git, .env, server-status, …) were publicly accessible
17A09: a client-side error/monitoring integration (e.g. Sentry/Datadog) is present — supports security logging & alerting.
Issues Found
1Missing Referrer-Policy header
2Missing Permissions-Policy header
32 external link(s) without noopener/noreferrer
4No cookie consent banner detected
5No Subresource Integrity (SRI) on external scripts
6Server technology disclosed via response headers/markup: Server: nginx
7security.txt file is missing — no standardized channel for reporting vulnerabilities
82 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
9CSP is missing key hardening directive(s): base-uri, form-action, object-src
10Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment — potential DOM-based XSS vectors
Recommendations to Reach 100%
1Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
2Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
3Add Cross-Origin-Opener-Policy: same-origin-allow-popups
4Add Cross-Origin-Resource-Policy: cross-origin
5Add rel="noopener noreferrer" to external links for security
6Implement a cookie consent banner for GDPR/ePrivacy compliance
7Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
8Strengthen CSP: consider nonce-based policies when feasible
9Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
10Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
11If 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]
12Add the missing CSP directives (base-uri, form-action, object-src) — e.g. object-src 'none', base-uri 'self', frame-ancestors 'none' — to close common bypasses [Impact: Medium | Effort: Low]
13Avoid eval, document.write, innerHTML and Function() with untrusted input; prefer textContent, DOM APIs and a trusted-types policy [Impact: Medium | Effort: Medium]
14A03 Software Supply Chain: only 0% of 4 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
Key Findings
1Language declared: en
2Rich ARIA implementation: 39 elements with ARIA attributes
3No major HTML nesting or validity issues detected
Issues Found
1No skip navigation link
2Missing landmarks: footer
33 of 3 images (100%) missing alt text
44 button(s) missing accessible labels
5Heading hierarchy has gaps — confusing for screen readers
6No focus styles detected
7Deprecated HTML tags impact accessibility
86 focusable element(s) inside aria-hidden containers
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <footer>
3Add descriptive alt text to all images — use empty alt="" only for decorative images
4Add text content or aria-label to all buttons
5Add :focus-visible styles to all interactive elements for keyboard navigation visibility
6Remove focusable elements (links, buttons, inputs) from aria-hidden regions — they trap keyboard users in invisible content
7Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
8Accessibility (WCAG 2.2 3.2.6): no consistent help mechanism (contact/help/support link) detected. Provide help access in a consistent location across pages.
Key Findings
1Some semantic elements: nav
2Complete social metadata (OG + Twitter Card)
313 strong entity mentions (bold/emphasized text)
45 call-to-action elements detected
5No AI crawlers blocked via meta tags — content accessible to AI search engines
6robots.txt file found
7robots.txt references 1 sitemap(s) — aids AI crawler discoverability
8llms.txt detected (score: 47/100, quality: detailed)
9llms.txt references 12 URLs for AI navigation
10llms.txt includes service/product catalog
11llms.txt uses proper Markdown formatting for machine readability
12llms.txt uses canonical domain in URLs
13High RAG-friendliness (100/100): 7 headings with IDs, 82 section anchors
14Content provenance signals detected (citations with sources, attributed claims)
15Good HTML-to-text ratio (54%) — AI crawlers can extract content efficiently
Issues Found
1No structured data (Schema.org) found
2No breadcrumb navigation
3No FAQ or Q&A content patterns found
4No sitemap reference found
5No social media links found
6llms.txt missing blockquote description
7No llms-full.txt companion file found
8llms.txt has fewer than 3 structured sections
9llms.txt is not referenced in HTML
10No 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
3Increase use of semantic HTML5 elements (article, section, aside, figure) for better AI understanding
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
7Add links to your social media profiles to strengthen brand entity signals
8Enhance llms.txt: add citation guidelines, version date, content usage policy, and expand URL list to cover all major pages
9Add a > blockquote summary on line 2-3 describing your business in 1-2 sentences
10Create /llms-full.txt with detailed documentation — services, pricing, case studies, technical specs — for AI models that want depth
11Organize llms.txt with clear ## sections: Overview, Core Services, Key Pages, Contact, Documentation
12Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your <head> for discoverability
13Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
14AI Readiness (multimodal): only 0% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Strong entity emphasis: 13 key terms highlighted
2Structured content: 8 lists, 0 tables — easily parsed by AI
3Good paragraph length for readability and AI parsing
44 external citation(s)
5Trust signals present: Reviews/Testimonials, HTTPS Security, Privacy Policy
6Social proof elements detected — builds credibility and conversion confidence
7Clear value proposition detected in heading elements
Issues Found
1Very thin content (291 words)
2No structured Q&A content
3Low semantic markup ratio — 121 divs vs 2 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
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
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
11AIO: no schema "name" property to anchor your primary entity. Declare a consistent Organization/Person/Product name in JSON-LD matching your title and H1.
Key Findings
18 lists provide scannable, AI-friendly content
213 emphasized terms suggest unique, quotable insights
318 original data elements (charts, figures, data tables)
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Content too thin for AI citation value
4Insufficient structured data for generative engine context
5thin content — may not provide enough depth for AI engines
6No 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
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
5Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
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 first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
9GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
1Short paragraphs are well-suited for answer extraction
28 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5Few concise answer paragraphs for snippet extraction
6No 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
7Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
8Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
9AEO: 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.
Key Findings
1NAP information detected: phone: 19019577, email: [email protected]
2Phone number(s) visible: 19019577, 17169420
3Email address found: [email protected]
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%
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
5Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
6Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
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
3Schema.org (maximize): local-business signals (address, hours, phone) detected but no LocalBusiness schema. Add LocalBusiness with address, geo, openingHoursSpecification and telephone for local rich results.
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Page language declared — aids assistive technology
4All ARIA roles are valid
5Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Low semantic-to-div ratio — 121 divs vs 2 semantic elements
4No 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
3Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
4Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
5WCAG 2.2 (1.4.13 Content on Hover/Focus): 6 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
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.