This website audit report analyzes http://DigitalMarketingCo.org/blog/imputed-tax-quantitative-easing-itqe-zero-tax-america across 12 critical dimensions with actionable recommendations.
http://DigitalMarketingCo.org/blog/imputed-tax-quantitative-easing-itqe-zero-tax-america
82Goodout of 100
Website Audit Report
ITQE: How America Can Eliminate All Income Taxes | Zero Tax
September 16, 2026 at 8:12 AM EDT 457ms response HTTPS Secure301 Redirect
Executive Summary
http://DigitalMarketingCo.org/blog/imputed-tax-quantitative-easing-itqe-zero-tax-america scores 82/100 (B-). Strong areas include Security, AI Readiness, Accessibility. The site has 6133 words, 68 images, and 3 schema blocks. Data confidence: 100%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
457ms
Response Time
6,133
Word Count
68
Images
221
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan20 scans recorded· Tap or hover a point for score & time↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Cloudflare Email Protection detected (14 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
2[SEO] 11 suspicious internal link pattern(s) detected: /glossary/seo-search-engine-optimization, /glossary/performance-optimization, /glossary/mobile-optimization
3[SEO] Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h4 (skips h3)
4[SEO] High link count (221) — above recommended range
5[SEO] URL is longer than recommended (89 chars)
6[SEO] High dofollow external link count (42) — excessive link equity leakage
7[SEO] Low readability score (12 Flesch) — content is hard to read
8[Performance] No responsive image srcset found
9[Performance] 6 inline <style> blocks
10[Performance] Large JS bundle (~2009KB) even for framework app
Top Recommendations
1[Impact: Medium | Effort: Low] Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2[Impact: Medium | Effort: Medium] Audit internal links for broken paths. Common issues: service slug changes, glossary terms without deep-dive pages, missing locale prefixes [Impact: High | Effort: Medium]
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
5[Impact: Medium | Effort: Medium] Keep URLs under 75 characters for optimal SEO and shareability
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: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
8[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
9[Impact: Medium | Effort: Medium] SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
10[Impact: Medium | Effort: Medium] Use srcset and sizes attributes on images to serve appropriately sized images per device
11[Impact: Medium | Effort: Medium] Extract inline styles into external CSS files for better caching and maintainability
12[Impact: Medium | Effort: Medium] Review bundle size — use dynamic imports and code splitting to reduce initial JS payload
Detailed Category Analysis
Key Findings
1Title tag is 59 characters — within optimal 50–60 range (Google 2025-2026)
2Meta description is 148 characters — within optimal 140–160 range (2025-2026)
3Single H1 tag present: "Imputed Tax Quantitative Easing (ITQE): How America Can Elim…"
4Canonical URL is set and matches the page URL
5Complete Open Graph tags (title, description, image, url, type)
6Complete Twitter Card tags present
7HTML lang attribute set to "en"
8Favicon present
9157 internal links help establish site architecture
1049 external links provide reference signals
11All external links have proper rel attributes (nofollow/noopener)
12No redirect chain — direct URL resolution
13Healthy internal link ratio: 71% of links are internal
14Good anchor text diversity: 76% unique anchor texts
15Good keyword alignment between title and H1
16Primary keyword "itqe" found in H1 — strong on-page signal
17Primary keyword appears in first paragraph — excellent content signal
18Primary keyword present in URL — good URL optimization
19Strong E-E-A-T signals detected (7 indicators)
20og:locale set to "en_US"
21OG image uses WebP format — optimal for quality/size balance
22OG image dimensions ≥1200×630px — optimal for all platforms
23article:published_time present — content freshness signal for social platforms
24article:modified_time present — update recency signal
25Twitter card uses summary_large_image — maximum visual impact
26Internal link density (25.6/1k words) — above average but acceptable for navigation-heavy pages
27Optimal keyword density: "itqe" at 1.4% (88 occurrences)
28Low passive voice ratio (8%) — clear, active writing style
29Table of Contents detected — improves dwell time and jump-link navigation
30Strong entity salience: Federal Reserve, Federal Reserve Act, Imputed Tax Quantitative Easing (score: 92)
31Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
32Social share buttons detected: ShareThis
33OG sharing completeness: 100% — all tags present for optimal social previews
343 hreflang annotation(s) present for international targeting
35Character encoding declared as UTF-8
Issues Found
1Cloudflare Email Protection detected (14 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
211 suspicious internal link pattern(s) detected: /glossary/seo-search-engine-optimization, /glossary/performance-optimization, /glossary/mobile-optimization
3Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h4 (skips h3)
4High link count (221) — above recommended range
5URL is longer than recommended (89 chars)
6High dofollow external link count (42) — excessive link equity leakage
7Low readability score (12 Flesch) — content is hard to read
Recommendations to Reach 100%
1Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2Audit internal links for broken paths. Common issues: service slug changes, glossary terms without deep-dive pages, missing locale prefixes [Impact: High | Effort: Medium]
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4Aim for ≤150–200 total links per page including nav, footer, and content links
5Keep URLs under 75 characters for optimal SEO and shareability
6Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
7Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
8Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
9SEO: 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: 457ms
2HTML is 775KB — typical for SSR framework with rich content
32 framework-managed script(s) — optimized by build pipeline
465/68 images use lazy loading
5Modern image formats (WebP/AVIF) detected
6Most images have explicit width/height attributes (prevents layout shift)
7Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com
8Preloaded resources: image, image, script, image
9font-display property detected — reduces invisible text during font loading
1030 async and 2 deferred scripts
11Cache-Control header with max-age is set
1232 inline scripts (framework hydration/data — standard for SSR apps)
13Lean CSS payload (~99KB)
14HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level
15CDN detected: Cloudflare — reduces latency for global users
16Gzip compression enabled
178 resource hints (preconnect/prefetch/preload) optimize loading
185 framework hydration script(s) — standard for SSR apps
19Estimated LCP: ~1217ms — within Google's "good" threshold (<2.5s)
20Estimated CLS: 0.09 — within Google's "good" threshold (<0.1)
21Estimated INP: ~230ms — acceptable for framework-hydrated app
22Variable fonts detected — reduces total font file downloads
23Good analytics setup: GA4 + event tracking
24Lab-proxy estimates — Speed Index ~7547ms, TTI ~7317ms, TBT ~2000ms (estimated from resource composition, not third-party field data)
Issues Found
1No responsive image srcset found
26 inline <style> blocks
3Large JS bundle (~2009KB) even for framework app
4221 links increase DOM size and parsing time
5Excessive DOM size (2716 elements) — increases memory use and slows rendering
6No efficient cache policy (Cache-Control max-age) on the main document
73 image(s) lack explicit width/height — a common cause of layout shift (CLS)
Recommendations to Reach 100%
1Use srcset and sizes attributes on images to serve appropriately sized images per device
2Extract inline styles into external CSS files for better caching and maintainability
3Review bundle size — use dynamic imports and code splitting to reduce initial JS payload
4Reduce links per page to improve DOM parsing performance and reduce memory usage
5Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
6Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
7Reduce DOM node count to under ~1,500 by simplifying markup and paginating long lists (Lighthouse best practice) [Impact: Medium | Effort: Medium]
8Set a Cache-Control header with an appropriate max-age (and immutable for versioned assets) to enable browser caching [Impact: Medium | Effort: Low]
9Add width and height attributes (or CSS aspect-ratio) to every image to reserve space and prevent layout shift [Impact: Medium | Effort: Low]
10Performance: only 20/68 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, viewport-fit=cover
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
7Service worker detected — offline capability possible
865 images with lazy loading benefit mobile data users
9Mobile-responsive hamburger menu detected
10PWA install-ready: manifest + service worker + HTTPS all present
11Web app manifest includes 19 icon sizes — good coverage
12CSS safe-area-inset handling detected — notch/dynamic-island compatible
13Touch feedback CSS detected (active states or touch-action)
143 internationalization signals detected (hreflang, lang, dir, locale meta)
153 image(s) without explicit width/height — most impactful for layout stability (CLS) on mobile (see Performance for remediation)
Issues Found
1No responsive image srcset — mobile users may download oversized images
256 potentially undersized touch targets detected
3Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
4Estimated page weight ~6643KB — heavy for mobile data plans
Recommendations to Reach 100%
1Implement srcset to serve smaller images on mobile devices, saving bandwidth
2Ensure all interactive elements are at least 48x48px (44x44px minimum) with adequate spacing for mobile tap accuracy
3Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
4Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4Content Security Policy header present
5X-Content-Type-Options: nosniff is set
6X-Frame-Options header prevents clickjacking
7Referrer-Policy set to: strict-origin-when-cross-origin
8Permissions-Policy header restricts browser features
9Cross-Origin-Opener-Policy set
10Cross-Origin-Resource-Policy set
11Cross-Origin-Embedder-Policy set
12Server via CDN proxy (cloudflare) — header added by infrastructure, not application
13All external links have security-safe rel attributes
14HSTS with preload and adequate max-age — eligible for browser preload list
15No cookie security issues detected
16Privacy policy link detected
17Cookie consent mechanism detected
18CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts
19CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks
20Permissions-Policy restricts 9 browser features (camera, microphone, geolocation, interest-cohort)
21Rate limiting recommended for form endpoints
22No server software/technology fingerprints exposed in headers or markup
23security.txt present and valid (/.well-known/security.txt) — provides a channel for vulnerability disclosure
24No stack traces or sensitive error details exposed in responses
25No obvious secret/API-key patterns exposed in page source
26Client-side library inventory (SBOM): WordPress
2734 script resource(s) catalogued for software-composition review
28No common sensitive paths (.git, .env, server-status, …) were publicly accessible
29Cross-origin isolation enabled (COOP + COEP) — hardened against Spectre-style side-channel and cross-origin leaks
30A09: a client-side error/monitoring integration (e.g. Sentry/Datadog) is present — supports security logging & alerting.
Issues Found
11 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
Recommendations to Reach 100%
1Strengthen CSP: consider nonce-based policies when feasible
2When feasible, migrate to nonce-based CSP for inline scripts/styles
3Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
4If 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
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 68 images have alt attributes
5All 1 forms have proper labels
6All 34 buttons have accessible labels
7Rich ARIA implementation: 75 elements with ARIA attributes
8Focus styles detected for keyboard navigation
95 minor HTML validity issue(s) — common in modern framework component patterns
101 table(s) have captions/labels
Issues Found
1Heading hierarchy has gaps — confusing for screen readers
2Potential contrast issues: white text on very light background detected, white text on very light background detected
Recommendations to Reach 100%
1Ensure all text meets WCAG AA contrast ratio of at least 4.5:1
2Review HTML structure for any non-framework-related nesting issues
Key Findings
1Rich structured data: 3 schema blocks (Organization, ProfessionalService, LocalBusiness, WebSite, WebPage)
2Hreflang tags: en, es, x-default
3Strong semantic markup: header, nav, main, section, article, figure, details, summary, footer, address
4Complete social metadata (OG + Twitter Card)
5Breadcrumb navigation present — aids AI in understanding site hierarchy
6FAQ/Q&A content patterns detected — highly valuable for AI citation
7Sitemap reference detected
820 strong entity mentions (bold/emphasized text)
9Social presence signals: facebook, youtube, instagram, tiktok, twitter, linkedin
1042 call-to-action elements detected
11No AI crawlers blocked via meta tags — content accessible to AI search engines
12robots.txt file found
13AI crawlers explicitly allowed in robots.txt: GPTBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Bytespider, Applebot-Extended, Cohere-ai, Amazonbot
14robots.txt references 4 sitemap(s) — aids AI crawler discoverability
15llms.txt detected (score: 83/100, quality: comprehensive)
16llms-full.txt companion file detected (8KB)
17llms.txt has proper title and description block
18llms.txt has 7 well-organized sections
19llms.txt references 16 URLs for AI navigation
20llms.txt includes service/product catalog
21llms.txt uses proper Markdown formatting for machine readability
22llms.txt links to detailed documentation (llms-full.txt)
23llms.txt referenced in HTML for discoverability
24llms.txt uses canonical domain in URLs
25High RAG-friendliness (100/100): 19 headings with IDs, 4 section anchors
26Additional AI crawlers allowed: PerplexityBot, Bytespider, Amazonbot, Applebot-Extended, Cohere-ai
27Content provenance signals detected (citations with sources, attributed claims)
28Content freshness signals present (dateModified/datePublished/time elements)
29Good HTML-to-text ratio (53%) — AI crawlers can extract content efficiently
Key Findings
1Comprehensive content (6133 words) — strong for AI model training
2Rich Q&A content (4 FAQ/accordion elements)
3Strong entity emphasis: 20 key terms highlighted
4Structured content: 16 lists, 1 tables — easily parsed by AI
5E-E-A-T schema signals present (2 types)
6Speakable schema detected — content optimized for voice assistants
745 external citations — strong reference density for AI model training
850 statistics/data points — excellent for AI knowledge extraction
9Author attribution present but missing expertise signals
102 call-to-action element(s) detected
11Good form usability score: 100/100
12Trust signals present: Trust Badges, HTTPS Security, Privacy Policy
13Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 401 divs vs 31 semantic elements
2Paragraphs are too long for optimal AI consumption
3No CTA above the fold
4No social proof elements
Recommendations to Reach 100%
1Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
2Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
3Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
4Add author bio, credentials, and links to establish expertise signals for AI E-E-A-T evaluation
5Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
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: primary entity name is inconsistent across title, H1 and schema "name". Align the brand/entity term across all three so AI systems resolve a single, unambiguous entity.
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
21 comparison/data table(s) — highly extractable by AI
316 lists provide scannable, AI-friendly content
44 ordered lists provide step-by-step structure
5How-to instructional patterns detected — valued by AI answer engines
6Comprehensive content depth (6133 words) supports AI citation
720 emphasized terms suggest unique, quotable insights
83 schema blocks help AI engines understand content context
9comprehensive content length — good for authority signals
10Hreflang includes self-referencing tag
11x-default hreflang fallback present
1250 data points/statistics — content has original research signals
13Content updated within 90 days
Issues Found
1paragraphs may be too long for featured snippets
Recommendations to Reach 100%
1Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
2Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
3GEO: only 4/97 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
Key Findings
1FAQPage schema markup present — eligible for rich FAQ results
2HowTo schema markup present — eligible for how-to rich results
3Question-answer heading patterns support featured snippet capture
4Speakable schema supports voice search optimization
5Breadcrumb navigation with schema aids answer context
616 lists provide scannable answers for People Also Ask
788 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1Paragraphs too long for answer engine extraction
2Paragraphs too long for voice assistant extraction
Recommendations to Reach 100%
1Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
2Consider adding video content with VideoObject schema for multimedia search results
3Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Key Findings
1NAP information detected: phone: 4799999999, email: [email protected]
2Phone number(s) visible: 4799999999, 2399999999
3Email address found: [email protected]
4LocalBusiness schema: LocalBusiness
5Address microdata markup detected
6Geo meta tags present for location targeting
7Business hours/opening hours detected
8Service area defined in schema
Issues Found
1No Google Maps embed
2No review/rating schema
Recommendations to Reach 100%
1Add an embedded Google Map to your contact or about page for local search signals
2Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
3Local 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.
4Local SEO (NAP): the visible phone number does not match schema telephone. Keep Name/Address/Phone identical across visible content, schema and directories for local ranking consistency.
Key Findings
13 JSON-LD block(s) with types: Organization, ProfessionalService, LocalBusiness, WebSite, WebPage, BlogPosting, NewsArticle, BreadcrumbList, FAQPage, HowTo
2Some microdata attributes detected alongside JSON-LD — common for address/local business markup in modern frameworks
3Comprehensive schema implementation
4Strong top-tier schema coverage: LocalBusiness, Organization, FAQPage, BreadcrumbList, WebSite, BlogPosting, NewsArticle
5BreadcrumbList schema → breadcrumb rich results
6FAQPage schema → expandable FAQ rich results
7Article/BlogPosting schema → article rich results + Google Discover
8Service schema describes your offerings
9HowTo schema → step-by-step rich results
10No schema validity issues detected
11Rich schema diversity: 7 distinct types with properties
12Entity linking via sameAs: 8 external profiles linked — strengthens Knowledge Graph
13Average schema property completeness: 89% — well-implemented
14Rich results eligible: FAQ, HowTo, Breadcrumbs, Article
15Schema nesting depth: 2 levels — rich entity relationships
16SearchAction schema present — eligible for sitelinks search box in Google
17Schema.org: a connected @graph with 10 entity types is present — strong structured-data maturity.
Recommendations to Reach 100%
1When feasible, consolidate all structured data into JSON-LD format
2Add missing high-impact schemas: Person
3Schema.org (maximize): commerce signals detected but no Product schema. Add Product with offers (price, priceCurrency, availability), aggregateRating and review for product rich results.
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Form error/validation feedback detected
5Relative units (rem/em/clamp) detected — supports text resizing
6Focus styles detected for keyboard navigation visibility
7Page language declared — aids assistive technology
8All ARIA roles are valid
9Moderate cognitive load — acceptable for interactive modern web apps with rich UI patterns
10Form error identification mechanisms present (WCAG 3.3.1)
11Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
12Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
13Reduced motion enforced: animations disabled when prefers-reduced-motion is set
Issues Found
1Low semantic-to-div ratio — 401 divs vs 31 semantic elements
22 potential color contrast issue(s)
Recommendations to Reach 100%
1Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
2Audit color contrast ratios — ensure at least 4.5:1 for normal text and 3:1 for large text (WCAG 1.4.3)
3WCAG 2.2 (1.4.13 Content on Hover/Focus): 72 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.