This website audit report analyzes https://baltimoretrademarks.com/ across 12 critical dimensions with actionable recommendations.
https://baltimoretrademarks.com/
59Needs Workout of 100
Website Audit Report
Baltimore Trademark Attorney | Trademark Application Lawyer
May 29, 2026 · 09:38 (America/New_York) 43ms response HTTPS Secure
Executive Summary
https://baltimoretrademarks.com/ scores 59/100 (F). Priority improvements needed in SEO, Security, AIO. The site has 465 words, 2 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
43ms
Response Time
465
Word Count
2
Images
28
Links
Website Preview
Visit SiteLoading preview…
Score History
Current scan4 scans recorded· Tap or hover a point for score & time↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is slightly short (139 chars)
2[SEO] Multiple H1 tags found (3)
3[SEO] Missing Twitter tags: twitter:title, twitter:description, twitter:image
4[SEO] 13 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5[SEO] High dofollow external link count (14) — excessive link equity leakage
6[SEO] Primary keyword missing from first paragraph
7[SEO] Weak E-E-A-T signals (2 indicators)
8[SEO] Low readability score (22 Flesch) — content is hard to read
9[SEO] OG image dimensions too small for social platforms
10[Performance] 3 render-blocking scripts slow down initial paint
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
2[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
5[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
6[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
7[Impact: High | Effort: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
8[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
9[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
11[Impact: Medium | Effort: Medium] Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
12[Impact: High | Effort: Medium] Convert all non-critical scripts to async/defer to eliminate render-blocking resources
Detailed Category Analysis
Key Findings
1Title tag is 59 characters — within optimal 50–60 range (Google 2025-2026)
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)
5HTML lang attribute set to "en-US"
6Favicon present
713 internal links help establish site architecture
815 external links provide reference signals
9Content length of 465 words is adequate
1028 total links — within recommended range
11URL length (32 chars) is within optimal range
12No redirect chain — direct URL resolution
13Good anchor text diversity: 60% unique anchor texts
14Good keyword alignment between title and H1
15Primary keyword "baltimore trademark attorney" found in H1 — strong on-page signal
16Primary keyword not in URL — acceptable for homepage/root URLs
17og:locale set to "en_US"
18Twitter card uses summary_large_image — maximum visual impact
19Internal link density (28/1k words) — above average but acceptable for navigation-heavy pages
20Optimal keyword density: "baltimore trademark attorney" at 1.9% (3 occurrences)
21Moderate entity presence: Contact Get Started, News About Baltimore Trademarks, Baltimore Brands Search
22Social share buttons detected: ShareThis
23OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Meta description is slightly short (139 chars)
2Multiple H1 tags found (3)
3Missing Twitter tags: twitter:title, twitter:description, twitter:image
413 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5High dofollow external link count (14) — excessive link equity leakage
6Primary keyword missing from first paragraph
7Weak E-E-A-T signals (2 indicators)
8Low readability score (22 Flesch) — content is hard to read
9OG image dimensions too small for social platforms
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters — this range maximizes SERP visibility in 2025-2026
2Consolidate to a single H1 tag — use H2–H6 for subtopics
3Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
5Include your primary keyword naturally in the first paragraph to establish topical relevance early
6Include your primary keyword in the URL slug for improved crawlability and click-through rates
7Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
8Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
9Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
11Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
Key Findings
1Excellent server response time: 43ms
2Lean HTML document: 59KB
3Responsive images with srcset detected
4Most images have explicit width/height attributes (prevents layout shift)
51 async and 0 deferred scripts
6Cache-Control header with max-age is set
7Lean CSS payload (~107KB)
8JavaScript payload (~203KB) is acceptable
9HTTP/3 (QUIC) detected — fastest connection protocol
10CDN detected: Cloudflare — reduces latency for global users
11Brotli compression enabled — best-in-class compression
122 third-party script(s) — manageable count
13Estimated LCP: ~983ms — within Google's "good" threshold (<2.5s)
14Estimated CLS: 0.1 — within Google's "good" threshold (<0.1)
15Estimated INP: ~84ms — within Google's "good" threshold (<200ms)
16Good analytics setup: GA4 + event tracking
Issues Found
13 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No font-display property found
47 inline <style> blocks
53 render-blocking CSS file(s)
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
3Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
4Preload critical resources (fonts, hero images) with <link rel="preload">
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
7Consider inlining critical CSS and deferring non-essential stylesheets
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
6Mobile-responsive hamburger menu detected
7Lightweight page (~539KB) — fast on mobile networks
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)
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
7Add :active / touch-action CSS for tactile feedback on mobile interactions
Key Findings
1HTTPS enabled — encrypted connection
2Server via CDN proxy (cloudflare) — header added by infrastructure, not application
3No cookie security issues detected
4Rate limiting recommended for form endpoints
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
713 external links missing rel="noopener noreferrer" — security risk
8No privacy policy detected
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
9Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
10Add a privacy policy link — required by GDPR, CCPA, and builds user trust
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 2 images have alt attributes
5All 2 forms have proper labels
6Rich ARIA implementation: 16 elements with ARIA attributes
7No major HTML nesting or validity issues detected
Issues Found
14 button(s) missing accessible labels
2No focus styles detected
Recommendations to Reach 100%
1Add text content or aria-label to all buttons
2Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Key Findings
11 schema block(s): WebPage, BreadcrumbList, WebSite, Organization
2Strong semantic markup: header, nav, main, section, footer
3Complete social metadata (OG + Twitter Card)
4Breadcrumb navigation present — aids AI in understanding site hierarchy
59 call-to-action elements detected
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7robots.txt file found
8High RAG-friendliness (77/100): 0 headings with IDs, 7 section anchors
9Content provenance signals detected (citations with sources, attributed claims)
10Content freshness signals present (dateModified/datePublished/time elements)
11Good HTML-to-text ratio (43%) — AI crawlers can extract content efficiently
Issues Found
1No FAQ or Q&A content patterns found
2No sitemap reference found
3No social media links found
4robots.txt has no Sitemap directive
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 an FAQ section with FAQPage schema to increase chances of AI engine citations
4Create and reference an XML sitemap for AI crawler discoverability
5Add links to your social media profiles to strengthen brand entity signals
6Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
7Create an llms.txt file to guide AI models on how to access and interpret your content (emerging standard for AI SEO)
Key Findings
14 emphasized entities
2Good semantic-to-div ratio: 10 semantic elements
3Structured content: 4 lists, 0 tables — easily parsed by AI
414 external citations — strong reference density for AI model training
5Author attribution present but missing expertise signals
6Strong CRO: 5 clear call-to-action elements detected
7Above-the-fold CTA detected — captures immediate visitor attention
8Good form usability score: 100/100
9Clear value proposition detected in heading elements
Issues Found
1Content may be too thin for AI optimization (465 words)
2No structured Q&A content
3Weak E-E-A-T schema signals
4Paragraphs are too long for optimal AI consumption
5Insufficient trust signals for conversion optimization
6No social proof elements
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
2Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
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 author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
9Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
14 lists detected
23 original data elements (charts, figures, data tables)
36 unique insight patterns detected (original research/analysis signals)
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
5paragraphs may be too long for featured snippets
6No hreflang tags — generative engines cannot determine language/region targeting
7Content appears stale (over 1 year since last update)
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
6Include unique statistics, expert quotes, and original insights that generative AI would want to cite
7Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
8Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
9Update content regularly — generative engines prioritize fresh, recently-updated content. Add dateModified signals.
Key Findings
1Breadcrumb navigation with schema aids answer context
24 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
4Paragraphs too long for answer engine extraction
5Few concise answer paragraphs for snippet extraction
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
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
9Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Key Findings
1NAP information detected: phone: 16073179185
2Phone number(s) visible: 16073179185, 0444444444
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
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
72 sameAs link(s) for entity matching
8Average schema property completeness: 86% — well-implemented
9Rich results potential: Breadcrumbs
10SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
1BreadcrumbList has very few properties (1)
2BreadcrumbList missing common identifiers (name/headline/url)
Recommendations to Reach 100%
1Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
2Add missing high-impact schemas: Person
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
Key Findings
1Relative units (rem/em/clamp) detected — supports text resizing
2Good semantic element usage (10 semantic elements)
3Page language declared — aids assistive technology
4All ARIA roles are valid
5Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4No error suggestion mechanisms detected in forms
5No focus styles detected
6No form error identification detected
7Multiple 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
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
5Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
6Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
7Ensure 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)
8Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
Limited-Time Offer
Audit-informed Optimizations for Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.