This website audit report analyzes https://www.ncis.navy.mil/resources/ncis-tips/ across 12 critical dimensions with actionable recommendations.
https://www.ncis.navy.mil/resources/ncis-tips/
40Poorout of 100
Website Audit Report
Naval Criminal Investigative Service > Resources > NCIS Tips
September 7, 2026 at 1:54 PM EDT 430ms response HTTPS Secure
Executive Summary
https://www.ncis.navy.mil/resources/ncis-tips/ scores 40/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 588 words, 8 images, and 1 schema blocks. Data confidence: 85%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
430ms
Response Time
588
Word Count
8
Images
111
Links
Website Preview
Visit SiteLoading preview…
Score History
Current scan2 scans recorded· Tap or hover a point for score & time↓ 4 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is short (65 chars)
2[SEO] No H1 heading found
3[SEO] Very few headings for content length
4[SEO] Missing canonical URL
5[SEO] No Open Graph tags found
6[SEO] No Twitter Card tags found
7[SEO] Deprecated HTML tags found: <font> (1)
8[SEO] 15 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
9[SEO] High dofollow external link count (26) — excessive link equity leakage
10[SEO] Primary keyword missing from first paragraph
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: High | Effort: Low] Add exactly one H1 tag with your primary keyword to establish page topic
3[Impact: Medium | Effort: Medium] Add more subheadings (H2, H3) to break up content and improve scannability
4[Impact: High | Effort: Low] Add a <link rel="canonical"> tag pointing to the preferred version of this page
5[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
7[Impact: Medium | Effort: Medium] Replace deprecated HTML tags with modern semantic equivalents
8[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
9[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
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 60 characters — within optimal 50–60 range (Google 2025-2026)
2HTML lang attribute set to "en-US"
3Favicon present
475 internal links help establish site architecture
526 external links provide reference signals
6Content length of 588 words is adequate
7111 total links — within recommended range
8URL length (46 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 68% of links are internal
11Good anchor text diversity: 96% unique anchor texts
12Primary keyword not in URL — acceptable for homepage/root URLs
13Optimal keyword density: "naval criminal investigative" at 1.5% (3 occurrences)
14Low passive voice ratio (13%) — clear, active writing style
15Moderate entity presence: United States, Marine Corps, Press Enter
Issues Found
1Meta description is short (65 chars)
2No H1 heading found
3Very few headings for content length
4Missing canonical URL
5No Open Graph tags found
6No Twitter Card tags found
7Deprecated HTML tags found: <font> (1)
815 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
9High dofollow external link count (26) — excessive link equity leakage
10Primary keyword missing from first paragraph
11Weak E-E-A-T signals (2 indicators)
12Low readability score (23 Flesch) — content is hard to read
13Very high internal link density (127.6/1k words) — may appear spammy
14No social sharing buttons/widgets detected
15Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Add exactly one H1 tag with your primary keyword to establish page topic
3Add more subheadings (H2, H3) to break up content and improve scannability
4Add a <link rel="canonical"> tag pointing to the preferred version of this page
5Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6Add Twitter Card meta tags for better social media previews
7Replace deprecated HTML tags with modern semantic equivalents
8Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
9Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
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
16Reduce internal link density — excessive linking dilutes individual link value
17Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
18Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
19Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
20SEO: 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: 430ms
2Lean HTML document: 52KB
3Gzip compression enabled
4Estimated INP: ~162ms — within Google's "good" threshold (<200ms)
Issues Found
117 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 0/8 images have width/height attributes
6No font-display property found
7No effective Cache-Control header
8Moderate CSS payload (~302KB)
9Moderate JavaScript payload (~852KB)
10HTTP/1.1 detected — no multiplexing
11No CDN detected
12No resource hints found
1310 render-blocking CSS files — delays first paint
14Estimated CSS bundle ~402KB — above optimal
15Potential long-task scripts: Heavy third-party: Universal-Federated-Analytics-8.7.js?age
16Estimated LCP: ~3330ms — needs improvement (goal: <2.5s)
17Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
18No analytics tracking detected — flying blind on user behavior
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">
8Add font-display: swap to web font declarations to show fallback text while fonts load
9Set Cache-Control headers with appropriate max-age to leverage browser caching
10Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
11Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
12Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
13Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
14Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
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
17Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
18Optimize Largest Contentful Paint: preload hero image, reduce render-blocking resources, use CDN for static assets
19Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
20Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
21Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
22Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
23Performance: only 0/8 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
Key Findings
1Viewport meta tag present: width=device-width,initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Mobile-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
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%
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
6Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
7Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
8Add env(safe-area-inset-*) CSS for proper display on notched/island devices
9Add :active / touch-action CSS for tactile feedback on mobile interactions
10Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
11Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4X-Frame-Options header prevents clickjacking
5Server header not exposing technology details
6No cookie security issues detected
7Privacy policy link detected
8Rate limiting recommended for form endpoints
9No server software/technology fingerprints exposed in headers or markup
10No stack traces or sensitive error details exposed in responses
11No obvious secret/API-key patterns exposed in page source
1217 script resource(s) catalogued for software-composition review
13No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Content-Security-Policy header
2Missing Referrer-Policy header
3Missing Permissions-Policy header
415 external links missing rel="noopener noreferrer" — security risk
5HSTS header present but missing preload directive
6No cookie consent banner detected
7security.txt file is missing — no standardized channel for reporting vulnerabilities
81 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
9Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
101 state-changing POST form(s) show no visible anti-CSRF token (heuristic — SameSite cookies may still protect them)
1110 javascript: URL(s) found — a legacy XSS/injection vector
12Access-Control-Allow-Origin: * — the API is readable by any website
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
3Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
4Add Cross-Origin-Opener-Policy: same-origin-allow-popups
5Add Cross-Origin-Resource-Policy: cross-origin
6Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
7Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
8Implement a cookie consent banner for GDPR/ePrivacy compliance
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]
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]
12Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
13Include a per-request anti-CSRF token (or rely on SameSite=Strict/Lax cookies plus origin checks) on all state-changing forms [Impact: Medium | Effort: Medium]
14Replace javascript: URLs with proper event handlers and href targets [Impact: Low | Effort: Low]
15Restrict Access-Control-Allow-Origin to an explicit allowlist of trusted origins rather than a wildcard [Impact: Medium | Effort: Low]
16A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 8 images have alt attributes
5All 1 forms have proper labels
6All 2 buttons have accessible labels
7Rich ARIA implementation: 13 elements with ARIA attributes
Issues Found
1No focus styles detected
2Deprecated HTML tags impact accessibility
33 minor HTML validity issue(s)
48 images missing explicit dimensions — causes layout shifts for screen reader users
Recommendations to Reach 100%
1Add :focus-visible styles to all interactive elements for keyboard navigation visibility
2Review and fix HTML structure issues for better accessibility and cross-browser compatibility
3Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
4Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
11 schema block(s): Organization
2Some semantic elements: header, nav, footer
3FAQ/Q&A content patterns detected — highly valuable for AI citation
48 strong entity mentions (bold/emphasized text)
5Social presence signals: linkedin, instagram, facebook, twitter, youtube
63 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8High RAG-friendliness (100/100): 0 headings with IDs, 13 section anchors
9Content provenance signals detected (citations with sources, attributed claims)
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No sitemap reference found
4No robots.txt file found
5No llms.txt file found — AI models cannot find structured guidance for your site
6No content freshness signals (dateModified, datePublished, <time> elements)
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
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
5Create and reference an XML sitemap for AI crawler discoverability
6Create a robots.txt file at your domain root — essential for crawler governance and AI SEO strategy
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
10Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
11 FAQ/Q&A elements detected
28 emphasized entities
3Structured content: 17 lists, 0 tables — easily parsed by AI
416 external citations — strong reference density for AI model training
51 call-to-action element(s) detected
6Above-the-fold CTA detected — captures immediate visitor attention
7Trust signals present: Trust Badges, HTTPS Security
Issues Found
1Content may be too thin for AI optimization (588 words)
2Low semantic markup ratio — 75 divs vs 3 semantic elements
3Weak E-E-A-T schema signals
4No author or expertise signals
5No social proof elements
6No clear value proposition in headings
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
2Expand FAQ section with more questions to increase AI training coverage
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 more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
10Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
11Your H1 or hero section should clearly state your unique value proposition — what you offer, for whom, and why it matters
Key Findings
117 lists provide scannable, AI-friendly content
28 emphasized terms suggest unique, quotable insights
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Insufficient structured data for generative engine context
4No hreflang tags — generative engines cannot determine language/region targeting
5No statistics or data points in substantial content
Recommendations to Reach 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
6Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
7Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
8Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
10GEO: 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
117 lists provide scannable answers for People Also Ask
Issues Found
1FAQ content exists but lacks FAQPage schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Add FAQPage schema markup to your FAQ section for rich snippet eligibility in search results
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Consider adding video content with VideoObject schema for multimedia search results
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8AEO: 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: 6391918290
2Phone number(s) visible: 6391918290, 2637202
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: Organization
2All structured data uses JSON-LD format — Google's recommended format
3Some top-tier schemas: Organization
4No schema validity issues detected
Issues Found
1Only basic schema implementation
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 57%
4No rich results eligibility detected
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add more top-tier schema types — consider: LocalBusiness, Product, Article
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: WebSite, FAQPage
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more schema types — diverse structured data improves AI and search engine understanding
9Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
10Fill in missing recommended properties for each schema type
11Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
12Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
13Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
Key Findings
1Relative units (rem/em/clamp) detected — supports text resizing
2Page language declared — aids assistive technology
3All ARIA roles are valid
4Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
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
5Low semantic-to-div ratio — 75 divs vs 3 semantic elements
6No focus styles detected
7No 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
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)
5Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
6Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
7Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
8Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
9WCAG 2.2 (1.4.13 Content on Hover/Focus): 16 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.