This website audit report analyzes http://EarthRiverGeothermal.com across 12 critical dimensions with actionable recommendations.
http://EarthRiverGeothermal.com
60Needs Workout of 100
Website Audit Report
My Home - Earth River Geothermal Heating & Cooling
July 8, 2026 · 16:02 (America/New_York) 145ms response HTTPS Secure301 Redirect
Executive Summary
http://EarthRiverGeothermal.com scores 60/100 (D-). Priority improvements needed in Performance, Security, GEO. The site has 2535 words, 4 images, and 1 schema blocks. Data confidence: 95%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
145ms
Response Time
2,535
Word Count
4
Images
122
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan5 scans recorded· Tap or hover a point for score & time↑ 1 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is short (112 chars)
2[SEO] Heading hierarchy gaps: h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
3[SEO] Missing Twitter tags: twitter:image
4[SEO] 10 dofollow external links — slightly above optimal range
5[SEO] Primary keyword "home" not found in H1
6[SEO] Low readability score (33 Flesch) — content is hard to read
7[SEO] OG image dimensions too small for social platforms
8[SEO] Low keyword density (0.4%) for "home"
9[Performance] Very large HTML: 1512KB
10[Performance] 56 render-blocking scripts slow down initial paint
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
4[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
5[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
6[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
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] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
9[Impact: Medium | Effort: Medium] Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
10[Impact: Medium | Effort: Medium] Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
11[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
12[Impact: Medium | Effort: Low] Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
Detailed Category Analysis
Key Findings
1Title tag is 50 characters — within optimal 50–60 range (Google 2025-2026)
2Single H1 tag present: "Earth River Geothermal Heating & Cooling"
3Canonical URL is set and matches the page URL
4Complete Open Graph tags (title, description, image, url, type)
5HTML lang attribute set to "en-US"
6Favicon present
7112 internal links help establish site architecture
810 external links provide reference signals
9Content length of 2535 words is adequate
10122 total links — within recommended range
11URL length (33 chars) is within optimal range
12No redirect chain — direct URL resolution
13Healthy internal link ratio: 92% of links are internal
14Good anchor text diversity: 91% unique anchor texts
15Good keyword alignment between title and H1
16Primary keyword appears in first paragraph — excellent content signal
17Primary keyword not in URL — acceptable for homepage/root URLs
18Strong E-E-A-T signals detected (5 indicators)
19og:locale set to "en_US"
20article:published_time present — content freshness signal for social platforms
21article:modified_time present — update recency signal
22Twitter card uses summary_large_image — maximum visual impact
23Internal link density (44.2/1k words) — above average but acceptable for navigation-heavy pages
24Low passive voice ratio (10%) — clear, active writing style
25Table of Contents detected — improves dwell time and jump-link navigation
26Strong entity salience: Earth River Geothermal, Geothermal Heating, Mark Schultz (score: 100)
27Social share buttons detected: ShareThis, Facebook Share, Twitter/X Share, Email Share
28OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Meta description is short (112 chars)
2Heading hierarchy gaps: h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
3Missing Twitter tags: twitter:image
410 dofollow external links — slightly above optimal range
5Primary keyword "home" not found in H1
6Low readability score (33 Flesch) — content is hard to read
7OG image dimensions too small for social platforms
8Low keyword density (0.4%) for "home"
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
4Include your primary keyword in the H1 heading for strongest on-page SEO signal
5Include your primary keyword in the URL slug for improved crawlability and click-through rates
6Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
7Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
8Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
9Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
10Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
11Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
Key Findings
1Excellent server response time: 145ms
2Responsive images with srcset detected
3Most images have explicit width/height attributes (prevents layout shift)
4Preconnect hints for: //hb.wpmucdn.com, http://fonts.googleapis.com, //fonts.gstatic.com
5Preloaded resources: font, font, font, font
6font-display property detected — reduces invisible text during font loading
74 async and 0 deferred scripts
8Cache-Control header with max-age is set
930 inline scripts (framework hydration/data — standard for SSR apps)
10HTTP/3 (QUIC) detected — fastest connection protocol
11CDN detected: Cloudflare — reduces latency for global users
12Brotli compression enabled — best-in-class compression
133 third-party script(s) — manageable count
149 resource hints (preconnect/prefetch/preload) optimize loading
154 font(s) preloaded for faster text rendering
16Estimated CLS: 0.1 — within Google's "good" threshold (<0.1)
17Estimated INP: ~210ms — acceptable for framework-hydrated app
18Variable fonts detected — reduces total font file downloads
19Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
1Very large HTML: 1512KB
256 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
413 inline <style> blocks
5Large CSS payload (~1851KB across 15 files) — slows rendering
6Large JS bundle (~3012KB) even for framework app
775 font files loaded — excessive font weight
815 render-blocking CSS files — delays first paint
9Estimated CSS bundle ~2001KB — above optimal
10Large JS bundle (~3612KB) even for framework app
11Poor estimated LCP: ~7345ms — exceeds 4s threshold
Recommendations to Reach 100%
1Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
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
4Extract inline styles into external CSS files for better caching and maintainability
5Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
6Review bundle size — use dynamic imports and code splitting to reduce initial JS payload
7Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
8Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
9Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
10Review bundle size — use dynamic imports and code splitting to reduce initial payload
11Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
12Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
13Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1, maximum-scale=1
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
8Responsive images via srcset serve appropriate sizes per device
9Mobile-responsive hamburger menu detected
10PWA install-ready: manifest + service worker + HTTPS all present
11Orientation handling declared in manifest or meta
12Touch feedback CSS detected (active states or touch-action)
13RTL text direction support detected
Issues Found
1Viewport disables user zoom (maximum-scale=1 or user-scalable=no)
2Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
3Only 3 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
4Estimated page weight ~7325KB — heavy for mobile data plans
Recommendations to Reach 100%
1Remove maximum-scale=1 and user-scalable=no from viewport meta — users must be able to zoom for accessibility (WCAG 1.4.4)
2Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
3Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
4Add env(safe-area-inset-*) CSS for proper display on notched/island devices
5Reduce 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
3Server via CDN proxy (cloudflare) — header added by infrastructure, not application
4No cookie security issues detected
5Rate limiting recommended for form endpoints
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
73 external link(s) without noopener/noreferrer
8No privacy policy detected
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11Outdated libraries detected: jQuery 1.12.4 (latest 3.7+)
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Add rel="noopener noreferrer" to external links for security
10Add a privacy policy link — required by GDPR, CCPA, and builds user trust
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Update outdated JavaScript libraries to latest versions — older versions have known security vulnerabilities (CVEs)
14Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 4 images have alt attributes
5All 2 forms have proper labels
6All iframes have title attributes
7Rich ARIA implementation: 38 elements with ARIA attributes
8Focus styles detected for keyboard navigation
9No major HTML nesting or validity issues detected
Issues Found
12 button(s) missing accessible labels
2Heading hierarchy has gaps — confusing for screen readers
31 video(s) missing captions/subtitles
41 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add text content or aria-label to all buttons
2Add <track kind="captions"> or <track kind="subtitles"> to all video elements (WCAG 1.2.2)
3Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Key Findings
11 schema block(s): WebPage, ImageObject, BreadcrumbList, WebSite, Organization
2Strong semantic markup: header, nav, main, section, footer, aside
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5Sitemap reference detected
620 strong entity mentions (bold/emphasized text)
7Social presence signals: facebook, twitter, instagram, youtube
88 call-to-action elements detected
9No AI crawlers blocked via meta tags — content accessible to AI search engines
10robots.txt file found
11High RAG-friendliness (100/100): 3 headings with IDs, 16 section anchors
12Content provenance signals detected (citations with sources, attributed claims)
13Content freshness signals present (dateModified/datePublished/time elements)
Issues Found
1No breadcrumb navigation
2robots.txt has no Sitemap directive
3No llms.txt file found — AI models cannot find structured guidance for your site
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
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
5Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
6Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
7Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
Key Findings
1Comprehensive content (2535 words) — strong for AI model training
21 FAQ/Q&A elements detected
3Strong entity emphasis: 20 key terms highlighted
4Structured content: 10 lists, 0 tables — easily parsed by AI
53 external citation(s)
615 statistics/data points — excellent for AI knowledge extraction
718 blockquotes/quotes enhance authority signals
8Author expertise signals detected (bio, credentials, Person schema)
91 call-to-action element(s) detected
10Above-the-fold CTA detected — captures immediate visitor attention
11Good form usability score: 100/100
12Trust signals present: Reviews/Testimonials, HTTPS Security
13Social proof elements detected — builds credibility and conversion confidence
14Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 179 divs vs 9 semantic elements
2Weak E-E-A-T schema signals
3Paragraphs are too long for optimal AI consumption
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
6Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
210 lists provide scannable, AI-friendly content
3Comprehensive content depth (2535 words) supports AI citation
420 emphasized terms suggest unique, quotable insights
515 data points/statistics — content has original research signals
662 unique insight patterns detected (original research/analysis signals)
718 quotation elements enhance credibility for GEO
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
5Content appears stale (over 1 year since last update)
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
4Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
5Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
6Update content regularly — generative engines prioritize fresh, recently-updated content. Add dateModified signals.
Key Findings
1Question-answer heading patterns support featured snippet capture
210 lists provide scannable answers for People Also Ask
3Video content detected — supports multimedia answer results
427 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
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
5No direct answer patterns ("X is defined as...", "X refers to...")
6Paragraphs 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
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
7Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
Issues Found
1No Name/Address/Phone (NAP) information detected
2No phone number detected on the page
3No LocalBusiness structured data
4No Google Maps embed
5No address microdata
6No geo meta tags
7No review/rating schema
Recommendations to Reach 100%
1Display your business name, address, and phone number prominently — NAP consistency is a top local ranking factor
2Add a clickable phone number (tel: link) for mobile users and local SEO signals
3Consider displaying a business email for direct contact signals
4Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
5Add an embedded Google Map to your contact or about page for local search signals
6Add PostalAddress schema or itemprop="address" microdata to your address elements
7Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
8Add 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: WebPage, ImageObject, BreadcrumbList, WebSite, Organization
2All structured data uses JSON-LD format — Google's recommended format
3Comprehensive schema implementation
4Strong top-tier schema coverage: Organization, BreadcrumbList, WebSite
5BreadcrumbList schema → breadcrumb rich results
6Rich schema diversity: 5 distinct types with properties
7Entity linking via sameAs: 5 external profiles linked — strengthens Knowledge Graph
8Rich results potential: Breadcrumbs
9SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
14 high-impact schema types missing
2BreadcrumbList has very few properties (1)
3BreadcrumbList missing common identifiers (name/headline/url)
4Schema property completeness averaging 69%
Recommendations to Reach 100%
1Priority schemas to add: FAQPage, Article, Person, Review
2Add FAQPage schema to FAQ content — enables expandable rich results
3Consider adding HowTo schema for instructional content
4Add more properties to schema types — aim for at least 5 meaningful properties per type
5Fill in missing recommended properties for each schema type
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)
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
9prefers-reduced-motion detected but enforcement unclear
Issues Found
1No error suggestion mechanisms detected in forms
21 autoplay media element(s) detected
3Low semantic-to-div ratio — 179 divs vs 9 semantic elements
43 heading level skip(s) — confuses screen reader navigation
5No form error identification detected
6Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
Recommendations to Reach 100%
1Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
2Remove autoplay from media elements or provide controls — autoplay can be disorienting and violates WCAG 1.4.2
3Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
4Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
5Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
6Ensure sticky headers/footers do not fully obscure the keyboard focus indicator. Use scroll-padding-top or ensure focus remains visible under overlapping elements (WCAG 2.4.11 AA)
7Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
8Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
Limited-Time Offer
Audit-informed Optimizations for 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.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.