This website audit report analyzes http://BaltimorePolice.org across 12 critical dimensions with actionable recommendations.
http://BaltimorePolice.org
56Needs Workout of 100
Website Audit Report
Homepage | Baltimore Police Department
July 20, 2026 185ms response HTTPS Secure301 Redirect
Executive Summary
http://BaltimorePolice.org scores 56/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, Security. The site has 378 words, 12 images, and 0 schema blocks. Data confidence: 85%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
185ms
Response Time
378
Word Count
12
Images
79
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is short (38 chars)
2[SEO] Meta description is short (55 chars)
3[SEO] Missing Twitter tags: twitter:description
4[SEO] 25 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5[SEO] High dofollow external link count (25) — excessive link equity leakage
6[SEO] Primary keyword "homepage" not found in H1
7[SEO] Primary keyword missing from first paragraph
8[SEO] Low readability score (8 Flesch) — content is hard to read
9[SEO] Missing og:locale tag — social platforms may guess language/region
10[SEO] Very high internal link density (142.9/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 for better SERP visibility
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 in the H1 heading for strongest on-page SEO signal
6[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
7[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
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: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
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] Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
12[Impact: High | Effort: Medium] Reduce internal link density — excessive linking dilutes individual link value
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Baltimore Police Department"
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"
6Favicon present
754 internal links help establish site architecture
825 external links provide reference signals
9Content length of 378 words is adequate
1079 total links — within recommended range
11URL length (32 chars) is within optimal range
12No redirect chain — direct URL resolution
13Healthy internal link ratio: 68% of links are internal
14Good anchor text diversity: 63% unique anchor texts
15Good keyword alignment between title and H1
16Primary keyword not in URL — acceptable for homepage/root URLs
17Moderate E-E-A-T signals (4 indicators)
18Low passive voice ratio (7%) — clear, active writing style
19Zero-click optimized: 9 TL;DR/summary block(s) + 1 definition-style lead paragraph(s)
20Moderate entity presence: Related Tip Get, Police Report Review Policies, Send Feedback Report
21Social share buttons detected: ShareThis
Issues Found
1Title tag is short (38 chars)
2Meta description is short (55 chars)
3Missing Twitter tags: twitter:description
425 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5High dofollow external link count (25) — excessive link equity leakage
6Primary keyword "homepage" not found in H1
7Primary keyword missing from first paragraph
8Low readability score (8 Flesch) — content is hard to read
9Missing og:locale tag — social platforms may guess language/region
10Very high internal link density (142.9/1k words) — may appear spammy
11Primary keyword "homepage" not found in body content
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 for better SERP visibility
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 in the H1 heading for strongest on-page SEO signal
6Include your primary keyword naturally in the first paragraph to establish topical relevance early
7Include your primary keyword in the URL slug for improved crawlability and click-through rates
8Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
9Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
10Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
11Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
12Reduce internal link density — excessive linking dilutes individual link value
13Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
14OG sharing completeness at 83% — add missing tags for better social previews
Key Findings
1Excellent server response time: 185ms
2Lean HTML document: 43KB
37/12 images use lazy loading
42 async and 3 deferred scripts
5Cache-Control header with max-age is set
6Lean CSS payload (~150KB)
7Brotli compression enabled — best-in-class compression
85 third-party script(s) — manageable count
9Estimated LCP: ~1685ms — within Google's "good" threshold (<2.5s)
10Estimated INP: ~116ms — within Google's "good" threshold (<200ms)
11Comprehensive analytics: GA4 (G-N4F03K56YN) + GTM (GTM-WFLL756) with event tracking
Issues Found
17 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No responsive image srcset found
4No font-display property found
5Moderate JavaScript payload (~554KB)
6HTTP/1.1 detected — no multiplexing
7No CDN detected
8No resource hints found
95 render-blocking CSS files — delays first paint
10Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
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
3Use srcset and sizes attributes on images to serve appropriately sized images per device
4Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
5Preload critical resources (fonts, hero images) with <link rel="preload">
6Add font-display: swap to web font declarations to show fallback text while fonts load
7Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
8Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
9Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
10Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
11Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
12Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0
2HTML5 doctype declared
3Character encoding declared
47 images with lazy loading benefit mobile data users
5Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4No responsive image srcset — mobile users may download oversized images
5Only 1 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
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Implement srcset to serve smaller images on mobile devices, saving bandwidth
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
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Referrer-Policy set to: same-origin
7Server header not exposing technology details
8No cookie security issues detected
9Privacy policy link detected
10Rate limiting recommended for form endpoints
11No server software/technology fingerprints exposed in headers or markup
12No stack traces or sensitive error details exposed in responses
13No raw email addresses exposed in page source
Issues Found
1Missing Content-Security-Policy header
2Missing Permissions-Policy header
325 external links missing rel="noopener noreferrer" — security risk
4HSTS header present but missing preload directive
5No cookie consent banner detected
6No Subresource Integrity (SRI) on external scripts
7security.txt file is missing — no standardized channel for reporting vulnerabilities
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
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 all external links with target="_blank" to prevent tabnabbing attacks
6Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
7Implement a cookie consent banner for GDPR/ePrivacy compliance
8Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
9Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
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]
Key Findings
1Language declared: en
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 12 images have alt attributes
5All 1 forms have proper labels
6All 4 buttons have accessible labels
7Rich ARIA implementation: 18 elements with ARIA attributes
Issues Found
1No focus styles detected
27 HTML validity issues detected — affects assistive technology parsing
Recommendations to Reach 100%
1Add :focus-visible styles to all interactive elements for keyboard navigation visibility
2Fix HTML nesting errors and deprecated elements. Validate at validator.w3.org for WCAG compliance
Key Findings
1Strong semantic markup: header, nav, main, article, footer
2Complete social metadata (OG + Twitter Card)
3FAQ/Q&A content patterns detected — highly valuable for AI citation
4Social presence signals: facebook, twitter, instagram, youtube, linkedin
55 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 (100/100): 4 headings with IDs, 9 section anchors
9Content provenance signals detected (citations with sources, attributed claims)
10Content freshness signals present (dateModified/datePublished/time elements)
Issues Found
1No structured data (Schema.org) found
2No breadcrumb navigation
3No sitemap reference found
4robots.txt has no Sitemap directive
5No llms.txt file found — AI models cannot find structured guidance for your site
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
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
7Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
8Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
9Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
Key Findings
1Structured content: 6 lists, 0 tables — easily parsed by AI
2Good paragraph length for readability and AI parsing
320 external citations — strong reference density for AI model training
4Strong CRO: 3 clear call-to-action elements detected
5Above-the-fold CTA detected — captures immediate visitor attention
6Good form usability score: 90/100
7Trust signals present: HTTPS Security, Privacy Policy
8Clear value proposition detected in heading elements
Issues Found
1Content may be too thin for AI optimization (378 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 189 divs vs 12 semantic elements
5Weak E-E-A-T schema signals
6No author or expertise signals
7No 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
3Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
4Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
5Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
6Add Speakable schema markup to help voice assistants identify the most important content
7Include specific statistics, percentages, and data points that AI models can extract and cite in responses
8Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
9Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
26 lists provide scannable, AI-friendly content
339 original data elements (charts, figures, data tables)
4Content is fresh (updated within 30 days) — strong recency signal
59 unique insight patterns detected (original research/analysis signals)
Issues Found
1No data tables for AI comparison extraction
2Content too thin for AI citation value
3Insufficient structured data for generative engine context
4No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Include how-to or step-by-step instructional content for generative AI answer inclusion
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
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
Key Findings
1Question-answer heading patterns support featured snippet capture
2Short paragraphs are well-suited for answer extraction
36 lists provide scannable answers for People Also Ask
4Content length and paragraph structure are voice-search optimized
Issues Found
1No FAQ content or schema
2No Speakable schema for voice search
3No breadcrumb navigation
4No 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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
5Consider adding video content with VideoObject schema for multimedia search results
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Key Findings
1NAP information detected: phone: 10462217
2Phone number(s) visible: 10462217, 2271891
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
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
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)
6Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
4Low semantic-to-div ratio — 189 divs vs 12 semantic elements
5No focus styles detected
6No form error identification 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
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
4Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
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)
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.