This website audit report analyzes https://www.ncis.navy.mil/ across 12 critical dimensions with actionable recommendations.
https://www.ncis.navy.mil/
44Poorout of 100
Website Audit Report
Home
July 22, 2026 486ms response HTTPS Secure
Executive Summary
https://www.ncis.navy.mil/ scores 44/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 1250 words, 75 images, and 1 schema blocks. Data confidence: 95%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
486ms
Response Time
1,250
Word Count
75
Images
161
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (4 chars)
2[SEO] Meta description is short (65 chars)
3[SEO] Heading hierarchy gaps: h1 → h5 (skips h2)
4[SEO] Missing canonical URL
5[SEO] No Open Graph tags found
6[SEO] No Twitter Card tags found
7[SEO] 43 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8[SEO] Title and H1 share no keywords — misaligned topic signals
9[SEO] High dofollow external link count (54) — excessive link equity leakage
10[SEO] Primary keyword "home" not found in H1
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
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] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
8[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
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 in the H1 heading for strongest on-page SEO signal
11[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
12[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
Detailed Category Analysis
Key Findings
1Single H1 tag present: "Mission of NCIS"
2HTML lang attribute set to "en-US"
3Favicon present
4101 internal links help establish site architecture
554 external links provide reference signals
6Content length of 1250 words is adequate
7161 total links — within recommended range
8URL length (26 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 63% of links are internal
11Good anchor text diversity: 91% unique anchor texts
12Primary keyword not in URL — acceptable for homepage/root URLs
13Low passive voice ratio (5%) — clear, active writing style
14Table of Contents detected — improves dwell time and jump-link navigation
15Moderate entity presence: United States, Director Omar Lopez, Homeland Security Task Force
16Social share buttons detected: Twitter/X Share
Issues Found
1Title tag is very short (4 chars)
2Meta description is short (65 chars)
3Heading hierarchy gaps: h1 → h5 (skips h2)
4Missing canonical URL
5No Open Graph tags found
6No Twitter Card tags found
743 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8Title and H1 share no keywords — misaligned topic signals
9High dofollow external link count (54) — excessive link equity leakage
10Primary keyword "home" not found in H1
11Primary keyword missing from first paragraph
12Weak E-E-A-T signals (2 indicators)
13Low readability score (22 Flesch) — content is hard to read
14Very high internal link density (80.8/1k words) — may appear spammy
15Low keyword density (0.2%) for "home"
16Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Expand your meta description to 140–160 characters for better SERP visibility
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
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
7Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
8Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
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 in the H1 heading for strongest on-page SEO signal
11Include your primary keyword naturally in the first paragraph to establish topical relevance early
12Include your primary keyword in the URL slug for improved crawlability and click-through rates
13Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
14Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
15Link to a Contact page — essential trust signal for E-E-A-T and local SEO
16Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
17Reduce internal link density — excessive linking dilutes individual link value
18Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
19Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
20Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
Key Findings
1Excellent server response time: 486ms
2HTML size is 143KB — acceptable
3Gzip compression enabled
4Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
135 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/75 images have width/height attributes
6No font-display property found
7No effective Cache-Control header
86 inline <style> blocks
913 inline scripts
10Large CSS payload (~752KB across 25 files) — slows rendering
11Heavy JavaScript payload (~1774KB across 35 files)
12HTTP/1.1 detected — no multiplexing
13No CDN detected
14No resource hints found
1525 render-blocking CSS files — delays first paint
16Estimated CSS bundle ~1002KB — above optimal
17Estimated JS bundle ~2124KB — heavy payload
18Potential long-task scripts: Heavy third-party: Universal-Federated-Analytics-8.7.js?age, Heavy third-party: DVIDSVideoAnalytics.min.js?cdv=4558, Heavy third-party: analyticsParamsForDVIDSAnalyticsAPI.js
19Poor estimated LCP: ~6386ms — exceeds 4s threshold
20Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
21Estimated INP: ~220ms — needs improvement (goal: <200ms)
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
10Extract inline styles into external CSS files for better caching and maintainability
11Move inline scripts to external files with defer attributes
12Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
13Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
14Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
15Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
16Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
17Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
18Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
19Reduce JS bundle with code splitting, tree shaking, and dynamic imports. Target <500KB initial JS
20Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
21Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
22Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
23Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
24Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
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)
7Estimated page weight ~7019KB — heavy for mobile data plans
Recommendations to Reach 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
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
10Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
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
Issues Found
1Missing Content-Security-Policy header
2Missing Referrer-Policy header
3Missing Permissions-Policy header
443 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
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]
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 75 images have alt attributes
5All 1 forms have proper labels
6All 8 buttons have accessible labels
7Rich ARIA implementation: 65 elements with ARIA attributes
Issues Found
1Heading hierarchy has gaps — confusing for screen readers
2No focus styles detected
36 HTML validity issues detected — affects assistive technology parsing
475 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
2Fix HTML nesting errors and deprecated elements. Validate at validator.w3.org for WCAG compliance
3Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
Key Findings
11 schema block(s): Organization
2Some semantic elements: header, nav, footer
3FAQ/Q&A content patterns detected — highly valuable for AI citation
47 strong entity mentions (bold/emphasized text)
5Social presence signals: linkedin, instagram, facebook, twitter, youtube
67 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 1 sitemap(s) — aids AI crawler discoverability
10High RAG-friendliness (100/100): 0 headings with IDs, 59 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No sitemap reference found
4No llms.txt file found — AI models cannot find structured guidance for your site
5No 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 /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Moderate content depth (1250 words)
21 FAQ/Q&A elements detected
37 emphasized entities
4Structured content: 14 lists, 0 tables — easily parsed by AI
517 external citations — strong reference density for AI model training
61 call-to-action element(s) detected
7Above-the-fold CTA detected — captures immediate visitor attention
8Trust signals present: Trust Badges, HTTPS Security
9Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 377 divs vs 3 semantic elements
2Weak E-E-A-T schema signals
3Paragraphs are too long for optimal AI consumption
4No author or expertise signals
5No social proof elements
Recommendations to Reach 100%
1Expand FAQ section with more questions to increase AI training coverage
2Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
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 expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
7Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
8Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
9Add 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
214 lists provide scannable, AI-friendly content
3Comprehensive content depth (1250 words) supports AI citation
Issues Found
1No data tables for AI comparison extraction
2Insufficient structured data for generative engine context
3paragraphs may be too long for featured snippets
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
4Include unique statistics, expert quotes, and original insights that generative AI would want to cite
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
7Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
8Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1Question-answer heading patterns support featured snippet capture
214 lists provide scannable answers for People Also Ask
3Video content detected — supports multimedia answer results
Issues Found
1FAQ content exists but lacks FAQPage schema
2No Speakable schema for voice search
3Paragraphs too long for answer engine extraction
4No breadcrumb navigation
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%
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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Key Findings
1NAP information detected: phone: 6389016277
2Phone number(s) visible: 6389016277, 2089877
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
11 media element(s) without autoplay
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
72 ARIA live regions for dynamic content announcements
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 — 377 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)
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.