This website audit report analyzes https://portal.ehawaii.gov/ across 12 critical dimensions with actionable recommendations.
https://portal.ehawaii.gov/
57Needs Workout of 100
Website Audit Report
The Official Website of the Aloha State | Hawaii.gov
September 7, 2026 at 1:57 PM EDT 44ms response HTTPS Secure
Executive Summary
https://portal.ehawaii.gov/ scores 57/100 (F). Strong areas include Accessibility. Priority improvements needed in Security, AI Readiness, AIO. The site has 416 words, 1 images, and 0 schema blocks. Data confidence: 80%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
44ms
Response Time
416
Word Count
1
Images
86
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description is short (39 chars)
2[SEO] No Twitter Card tags found
3[SEO] 8 external links missing recommended rel attributes
4[SEO] 8 dofollow external links — slightly above optimal range
5[SEO] Primary keyword missing from first paragraph
6[SEO] Missing og:locale tag — social platforms may guess language/region
7[SEO] Very high internal link density (185.1/1k words) — may appear spammy
8[Performance] 1 render-blocking script(s)
9[Performance] No font-display property found
10[Performance] No effective Cache-Control header
Top Recommendations
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
5[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
6[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
7[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
8[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
9[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
10[Impact: High | Effort: Medium] Reduce internal link density — excessive linking dilutes individual link value
11[Impact: Medium | Effort: Low] OG sharing completeness at 83% — add missing tags for better social previews
12[Impact: High | Effort: Medium] SEO (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.
Detailed Category Analysis
Key Findings
1Title tag is 52 characters — within optimal 50–60 range (Google 2025-2026)
2Single H1 tag present: "Aloha, welcome to hawaii.gov The official website of the Alo…"
3Clean heading hierarchy with no skipped levels
4Canonical URL is set and matches the page URL
5Complete Open Graph tags (title, description, image, url, type)
6HTML lang attribute set to "en"
7Favicon present
877 internal links help establish site architecture
98 external links provide reference signals
10Content length of 416 words is adequate
1186 total links — within recommended range
12URL length (27 chars) is within optimal range
13No redirect chain — direct URL resolution
14Healthy internal link ratio: 90% of links are internal
15Good anchor text diversity: 93% unique anchor texts
16Primary keyword "the official website" found in H1 — strong on-page signal
17Primary keyword not in URL — acceptable for homepage/root URLs
18Moderate E-E-A-T signals (3 indicators)
19Optimal keyword density: "the official website" at 0.7% (1 occurrences)
20Moderate entity presence: News Release, Josh Green, Hurricane Lowell
21Social share buttons detected: ShareThis
Issues Found
1Meta description is short (39 chars)
2No Twitter Card tags found
38 external links missing recommended rel attributes
48 dofollow external links — slightly above optimal range
5Primary keyword missing from first paragraph
6Missing og:locale tag — social platforms may guess language/region
7Very high internal link density (185.1/1k words) — may appear spammy
Recommendations to Reach 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Add Twitter Card meta tags for better social media previews
3Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
4Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
5Include your primary keyword naturally in the first paragraph to establish topical relevance early
6Include your primary keyword in the URL slug for improved crawlability and click-through rates
7Link to a Contact page — essential trust signal for E-E-A-T and local SEO
8Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
9Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
10Reduce internal link density — excessive linking dilutes individual link value
11OG sharing completeness at 83% — add missing tags for better social previews
12SEO (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.
13SEO: 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: 44ms
2Lean HTML document: 34KB
3Modern image formats (WebP/AVIF) detected
4Preloaded resources: font, font, font, font, font, font, font
51 async and 0 deferred scripts
6Lean CSS payload (~30KB)
7JavaScript payload (~108KB) is acceptable
8CDN detected: CloudFront — reduces latency for global users
9Gzip compression enabled
101 third-party script(s) — manageable count
117 resource hints (preconnect/prefetch/preload) optimize loading
127 font(s) preloaded for faster text rendering
13Estimated LCP: ~324ms — within Google's "good" threshold (<2.5s)
14Estimated CLS: 0.03 — within Google's "good" threshold (<0.1)
15Estimated INP: ~68ms — within Google's "good" threshold (<200ms)
16Good analytics setup: GA4 + event tracking
Issues Found
11 render-blocking script(s)
2No font-display property found
3No effective Cache-Control header
4HTTP/1.1 detected — no multiplexing
57 font files loaded — excessive font weight
Recommendations to Reach 100%
1Add async or defer attributes to render-blocking scripts
2Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
3Add font-display: swap to web font declarations to show fallback text while fonts load
4Set Cache-Control headers with appropriate max-age to leverage browser caching
5Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
6Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
7Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
8Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
Key Findings
1Viewport meta tag present: width=device-width,initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Mobile-responsive hamburger menu detected
7Lightweight page (~252KB) — fast on mobile networks
Issues Found
1Missing Apple touch icon
2Manifest present but no service worker — PWA install prompt will not fire
Recommendations to Reach 100%
1Add <link rel="apple-touch-icon"> for iOS homescreen icons
2Consider implementing a service worker for offline support and faster repeat visits
3Add a service worker to complete PWA install requirements (manifest + SW + HTTPS)
4Add env(safe-area-inset-*) CSS for proper display on notched/island devices
5Add :active / touch-action CSS for tactile feedback on mobile interactions
6Mobile/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.
7Mobile/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
2No cookie security issues detected
3Privacy policy link detected
4Rate limiting recommended for form endpoints
5No server software/technology fingerprints exposed in headers or markup
6No stack traces or sensitive error details exposed in responses
7No raw email addresses exposed in page source
8No obvious secret/API-key patterns exposed in page source
92 script resource(s) catalogued for software-composition review
10No common sensitive paths (.git, .env, server-status, …) were publicly accessible
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
7Server header exposes technology: AmazonS3
88 external links missing rel="noopener noreferrer" — security risk
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11security.txt file is missing — no standardized channel for reporting vulnerabilities
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
9Remove or obfuscate the Server header to avoid exposing your technology stack
10Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
14Add 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]
15A08 Integrity Failures: dynamic remote script injection detected. Load third-party code with static tags carrying SRI, or gate it behind a strict CSP with Trusted Types to prevent tampered-update execution.
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 1 images have alt attributes
5All 2 forms have proper labels
6All 5 buttons have accessible labels
7Rich ARIA implementation: 74 elements with ARIA attributes
8Language-specific content sections marked with lang attribute (WCAG 3.1.2)
Issues Found
1No focus styles detected
25 minor HTML validity issue(s)
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
3Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
1Strong semantic markup: nav, main, section, footer
2FAQ/Q&A content patterns detected — highly valuable for AI citation
31 call-to-action elements detected
4No AI crawlers blocked via meta tags — content accessible to AI search engines
5High RAG-friendliness (100/100): 0 headings with IDs, 16 section anchors
6Content provenance signals detected (citations with sources, attributed claims)
7Content freshness signals present (dateModified/datePublished/time elements)
8Good HTML-to-text ratio (24%) — AI crawlers can extract content efficiently
Issues Found
1No structured data (Schema.org) found
2Incomplete social metadata
3No breadcrumb navigation
4No sitemap reference found
5No social media links found
6No robots.txt file found
7No 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 hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Use <strong> and <em> tags to highlight key entities, concepts, and terms
6Add links to your social media profiles to strengthen brand entity signals
7Create a robots.txt file at your domain root — essential for crawler governance and AI SEO strategy
8Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
9Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
10Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
Key Findings
1Rich Q&A content (6 FAQ/accordion elements)
2Structured content: 8 lists, 0 tables — easily parsed by AI
38 external citations — strong reference density for AI model training
41 call-to-action element(s) detected
5Good form usability score: 90/100
6Trust signals present: Trust Badges, HTTPS Security, Privacy Policy
7Clear value proposition detected in heading elements
Issues Found
1Content may be too thin for AI optimization (416 words)
2Weak entity markup — few terms emphasized
3Low semantic markup ratio — 162 divs vs 8 semantic elements
4Weak E-E-A-T schema signals
5Paragraphs are too long for optimal AI consumption
6No author or expertise signals
7No CTA above the fold
8No social proof elements
Recommendations to Reach 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
4Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
5Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
6Add Speakable schema markup to help voice assistants identify the most important content
7Include specific statistics, percentages, and data points that AI models can extract and cite in responses
8Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
9Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
10Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
11Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
12Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
13AIO: 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
18 lists provide scannable, AI-friendly content
2How-to instructional patterns detected — valued by AI answer engines
31 definition list(s) — excellent for AI glossary extraction
4Content 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
3Content too thin for AI citation value
4Insufficient structured data for generative engine context
5paragraphs may be too long for featured snippets
6No hreflang tags — generative engines cannot determine language/region targeting
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
3Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
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
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
8GEO: only 0/17 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
18 lists provide scannable answers for People Also Ask
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
5Paragraphs too long for answer engine extraction
6No breadcrumb navigation
7Few concise answer paragraphs for snippet extraction
8No direct answer patterns ("X is defined as...", "X refers to...")
9Paragraphs 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
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
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
7Consider adding video content with VideoObject schema for multimedia search results
8Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
9Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
10Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
11AEO: 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: 6126231
2Phone number(s) visible: 6126231, 4875400
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
Key Findings
1Relative units (rem/em/clamp) detected — supports text resizing
2Page language declared — aids assistive technology
3All ARIA roles are valid
4Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
5Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4No error suggestion mechanisms detected in forms
5Low semantic-to-div ratio — 162 divs vs 8 semantic elements
6No focus styles detected
7No form error identification detected
Recommendations to Reach 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
5Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
6Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
7Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
8Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
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.