This website audit report analyzes http://IRS.gov across 12 critical dimensions with actionable recommendations.
http://IRS.gov
50Needs Workout of 100
Website Audit Report
Internal Revenue Service | An official website of the United States government
September 7, 2026 at 1:48 PM EDT 696ms response HTTPS Secure301 Redirect
Executive Summary
http://IRS.gov scores 50/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 1710 words, 15 images, and 0 schema blocks. Data confidence: 90%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
696ms
Response Time
1,710
Word Count
15
Images
273
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 too long (78 chars — may be truncated in SERPs)
2[SEO] No H1 heading found
3[SEO] Missing OG tags: og:title, og:description, og:url, og:type
4[SEO] High link count (273) — above recommended range
5[SEO] 28 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6[SEO] High dofollow external link count (30) — excessive link equity leakage
7[SEO] Primary keyword missing from first paragraph
8[SEO] Low readability score (15 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 (140.9/1k words) — may appear spammy
Top Recommendations
1[Impact: High | Effort: Low] Shorten your title to under 60 characters to prevent truncation in search results
2[Impact: High | Effort: Low] Add exactly one H1 tag with your primary keyword to establish page topic
3[Impact: High | Effort: Low] Add missing Open Graph tags: og:title, og:description, og:url, og:type
4[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
5[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
6[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
7[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
8[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
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: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
11[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
Detailed Category Analysis
Key Findings
1Meta description is 151 characters — within optimal 140–160 range (2025-2026)
2Clean heading hierarchy with no skipped levels
3Canonical URL is set and matches the page URL
4Complete Twitter Card tags present
5HTML lang attribute set to "en"
6Favicon present
7241 internal links help establish site architecture
830 external links provide reference signals
9Content length of 1710 words is adequate
10URL length (20 chars) is within optimal range
11No redirect chain — direct URL resolution
12Healthy internal link ratio: 88% of links are internal
13Good anchor text diversity: 61% unique anchor texts
14Primary keyword not in URL — acceptable for homepage/root URLs
15Moderate E-E-A-T signals (4 indicators)
16Low passive voice ratio (10%) — clear, active writing style
17Table of Contents detected — improves dwell time and jump-link navigation
18Zero-click optimized: 4 TL;DR/summary block(s) + 2 definition-style lead paragraph(s)
19Moderate entity presence: United States, Social Security, Individual Business Tax Pro Access
20Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
21Social share buttons detected: ShareThis, AddToAny
Issues Found
1Title tag is too long (78 chars — may be truncated in SERPs)
2No H1 heading found
3Missing OG tags: og:title, og:description, og:url, og:type
4High link count (273) — above recommended range
528 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6High dofollow external link count (30) — excessive link equity leakage
7Primary keyword missing from first paragraph
8Low readability score (15 Flesch) — content is hard to read
9Missing og:locale tag — social platforms may guess language/region
10Very high internal link density (140.9/1k words) — may appear spammy
11Primary keyword "internal revenue service" not found in body content
12Low OG sharing completeness (17%) — social previews will be poor
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Add exactly one H1 tag with your primary keyword to establish page topic
3Add missing Open Graph tags: og:title, og:description, og:url, og:type
4Aim for ≤150–200 total links per page including nav, footer, and content links
5Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
6Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
7Include your primary keyword naturally in the first paragraph to establish topical relevance early
8Include your primary keyword in the URL slug for improved crawlability and click-through rates
9Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
11Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
12Add <meta property="article:published_time"> for content freshness signals in social shares
13Add <meta property="article:modified_time"> to signal content freshness
14Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
15Reduce internal link density — excessive linking dilutes individual link value
16Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
17Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
18SEO (E-E-A-T): no author linkage or sameAs identity markup detected. Add a verifiable author byline with rel="author" and sameAs links to strengthen Experience/Expertise signals.
19SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Acceptable response time: 696ms
2HTML size is 133KB — acceptable
31/15 images use lazy loading
40 async and 1 deferred scripts
5Cache-Control header with max-age is set
6Lean CSS payload (~90KB)
7JavaScript payload (~304KB) is acceptable
8Brotli compression enabled — best-in-class compression
91 third-party script(s) — manageable count
10Estimated LCP: ~1756ms — within Google's "good" threshold (<2.5s)
11Estimated INP: ~86ms — within Google's "good" threshold (<200ms)
12Comprehensive analytics: GA4 (detected) + GTM (GTM-KV978ZL) with event tracking
Issues Found
15 render-blocking scripts slow down initial paint
2No WebP or AVIF image formats found
3No responsive image srcset found
4Only 0/15 images have width/height attributes
5No font-display property found
6273 links increase DOM size and parsing time
7HTTP/1.1 detected — no multiplexing
8No CDN detected
9No resource hints found
102 render-blocking CSS file(s)
11Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Convert all non-critical scripts to async/defer to eliminate render-blocking resources
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
9Reduce links per page to improve DOM parsing performance and reduce memory usage
10Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
11Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
12Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
13Consider inlining critical CSS and deferring non-essential stylesheets
14Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
15Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
16Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
17Performance: only 0/15 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, shrink-to-fit=no
2HTML5 doctype declared
3Character encoding declared
41 images with lazy loading benefit mobile data users
5Mobile-responsive hamburger menu detected
63 internationalization signals detected (hreflang, lang, dir, locale meta)
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
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
6Server header not exposing technology details
7Privacy policy link detected
8Rate limiting recommended for form endpoints
9No stack traces or sensitive error details exposed in responses
10No raw email addresses exposed in page source
11No obvious secret/API-key patterns exposed in page source
126 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
428 external links missing rel="noopener noreferrer" — security risk
5HSTS header present but missing preload directive
6Cookie security issues: missing Secure flag; missing HttpOnly flag; missing SameSite attribute
7No cookie consent banner detected
8No Subresource Integrity (SRI) on external scripts
9Server technology disclosed via response headers/markup: x-generator: Drupal 10 (https://www.drupal.org)
10security.txt file is missing — no standardized channel for reporting vulnerabilities
11robots.txt discloses sensitive-looking path(s): /web.config, /admin/, /user/login/ — Disallow entries can act as a map for attackers
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
8Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
9Implement a cookie consent banner for GDPR/ePrivacy compliance
10Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
11Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
12Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
13Add 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]
14Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
15A07 Authentication Failures: cookies do not use the __Host-/__Secure- prefix. Prefix session cookies with __Host- (with Secure, Path=/, no Domain) and add the Partitioned (CHIPS) attribute for cross-site isolation.
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
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 15 images have alt attributes
5All 2 forms have proper labels
6All 47 buttons have accessible labels
7Rich ARIA implementation: 89 elements with ARIA attributes
8Language-specific content sections marked with lang attribute (WCAG 3.1.2)
Issues Found
1No focus styles detected
24 minor HTML validity issue(s)
315 images missing explicit dimensions — causes layout shifts for screen reader users
455 focusable element(s) inside aria-hidden containers
54 duplicate ID(s) — breaks ARIA references and label associations
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
4Remove focusable elements (links, buttons, inputs) from aria-hidden regions — they trap keyboard users in invisible content
5Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
6Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
1Hreflang tags: en, es, zh-hans, zh-hant, ko, ru, vi, ht
2Strong semantic markup: header, section, nav, aside, main, article, footer
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5Social presence signals: facebook, twitter, instagram, linkedin, youtube
614 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): 41 headings with IDs, 62 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
12Content freshness signals present (dateModified/datePublished/time elements)
Issues Found
1No structured data (Schema.org) found
2No breadcrumb navigation
3No sitemap reference found
4No 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 breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
3Create and reference an XML sitemap for AI crawler discoverability
4Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
5Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
6Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
7AI Readiness (multimodal): only 47% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Comprehensive content (1710 words) — strong for AI model training
2Rich Q&A content (126 FAQ/accordion elements)
35 emphasized entities
4Structured content: 37 lists, 0 tables — easily parsed by AI
5Good paragraph length for readability and AI parsing
625 external citations — strong reference density for AI model training
7Strong CRO: 3 clear call-to-action elements detected
8Good form usability score: 90/100
9Trust signals present: HTTPS Security, Privacy Policy
10Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 294 divs vs 15 semantic elements
2Weak E-E-A-T schema signals
3No author or expertise signals
4No CTA above the fold
5No social proof elements
Recommendations to Reach 100%
1Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
2Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
3Add Speakable schema markup to help voice assistants identify the most important content
4Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
5Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
6Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
7Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
8AIO: no schema "name" property to anchor your primary entity. Declare a consistent Organization/Person/Product name in JSON-LD matching your title and H1.
Key Findings
137 lists provide scannable, AI-friendly content
2How-to instructional patterns detected — valued by AI answer engines
3Comprehensive content depth (1710 words) supports AI citation
4Hreflang includes self-referencing tag
517 original data elements (charts, figures, data tables)
6Content is fresh (updated within 30 days) — strong recency signal
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
4Hreflang set is missing x-default fallback
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
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 <link rel="alternate" hreflang="x-default" href="primary-url"> as a fallback for unmatched languages/regions
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
8GEO: only 1/69 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
9GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
1Short paragraphs are well-suited for answer extraction
237 lists provide scannable answers for People Also Ask
335 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
4Content length and paragraph structure are voice-search optimized
Issues Found
1FAQ content exists but lacks FAQPage schema
2How-to content exists but lacks HowTo schema
3Content not optimized for featured snippets
4No Speakable schema for voice search
5No breadcrumb navigation
6No 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
2Add HowTo schema to your instructional content for rich result eligibility
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: 4884958
2Phone number(s) visible: 4884958, 4644204
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
7Local SEO: local business signals present but no explicit city/region in the title, H1 or opening paragraph. Add "City, State" to your title/H1 and intro to reinforce local relevance.
8Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
Issues Found
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite, FAQPage, HowTo
Recommendations to Reach 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
2Priority schema types to add: Organization, WebSite, FAQPage, HowTo — these have the highest SEO impact for your page type
3Schema.org (maximize): long-form article content detected but no Article/BlogPosting schema. Add Article with headline, author, datePublished, dateModified, image and publisher for maximal eligibility.
4Schema.org (maximize): commerce signals detected but no Product schema. Add Product with offers (price, priceCurrency, availability), aggregateRating and review for product rich results.
5Schema.org (maximize): local-business signals (address, hours, phone) detected but no LocalBusiness schema. Add LocalBusiness with address, geo, openingHoursSpecification and telephone for local rich results.
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Page language declared — aids assistive technology
4All ARIA roles are valid
5Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
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 — 294 divs vs 15 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)
7Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
8WCAG 2.2 (1.4.13 Content on Hover/Focus): 93 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.