Speed Insights
Grade D
62% performance
https://gfmholdings.us
From Gfmholdings.us
LCP
716ms
Largest paint
TBT
3830ms
Blocking time
CLS
0.001
Layout shift
71
out of 100
93
out of 100
102/110 rule points
83
out of 100
60/72 rule points
47
out of 100
33/70 rule points
62
out of 100
68/110 rule points
Category point breakdown
Biggest score-losing checks
Fix rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 5 violation rule(s), including 5 serious or critical rule(s). Top rules: aria-required-parent (3), aria-tab-name (2), color-contrast (1), link-name (2), nested-interactive (6).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
ARIA tab nodes must have an accessible name
Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Fix Prompt
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Clarify the hero promise
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 1 H1 heading(s), 43 H1 characters, 0 supporting-copy characters, and 1 actionable CTA(s).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Use one clear H1 and ordered headings
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 19 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Fix heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 2, 2, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5, 2, 2, 2, 2, 2, 2.
Priority
Priority 13: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 1 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 1 review and 1 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 19 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 6 of 18 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 2, 2, 3, 3, 3, 2, 2, 2, 5, 5, 5, 5, 2, 2, 2, 2, 2, 2. Failed: earned 0 of 11 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
Basic contrast
Why this needs attention
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Low contrast makes a launch page feel less polished and can exclude users with low vision.
Recommended correction
Evidence
2 of 34 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
Digital Services for Connecticut Businesses
Web • WordPress • SEO • Design
Fix Prompt
Rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 5 violation rule(s), including 5 serious or critical rule(s). Top rules: aria-required-parent (3), aria-tab-name (2), color-contrast (1), link-name (2), nested-interactive (6). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
ARIA tab nodes must have an accessible name
Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Fix Prompt
Hero clarity signals
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 1 H1 heading(s), 43 H1 characters, 0 supporting-copy characters, and 1 actionable CTA(s). Failed: earned 9 of 13 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Trust signals
Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 strong, specific trust or proof signal(s). Generic words such as “security” do not count by themselves. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Spacing consistency
Why this needs attention
The page exposes few consistent spacing signals in class or inline styles.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Detected 0 spacing uses across 0 distinct spacing token(s). Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Visual hierarchy
Why this needs attention
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
Detected 3 of 4 hierarchy signals from one H1, supporting headings, an actionable CTA, and emphasized text. Failed: earned 7 of 9 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 2995ms. Load complete: 2997ms. First contentful paint: 716ms. Resources: 84. Scripts: 33. Images: 7. Third-party origins: 8. Transfer: not available. Potential render-blocking resources: 56. Exceeded thresholds: DOMContentLoaded 2995ms (threshold 2500ms); Script requests 33 scripts (threshold 20 scripts). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
Load contributors
Asset timings are observed request durations. They are not added together because browsers can load requests in parallel.
DOMContentLoaded
495ms over the rendered audit threshold.
Script requests
13 scripts over the rendered audit threshold.
swiper.min.js
elements-handlers.min.js
Fix Prompt
Rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 458px. WCAG 2.2 AA target-size failures: 0. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Connecticut Digital Services
Connecticut Digital Services
Overflowing element
Overflowing element
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 70/100. Detected 1 JSON-LD block(s), 0 parse error(s), 11 graph node(s), and types BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 85/100 for “Digital Services for Connecticut Businesses”. Title/H1 token overlap is 50%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 70/100 from 372 main-content words, 0 concise answer block(s), 3 question heading(s), 2 definition(s), 5 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected home page role.
Published or updated date
Freshness metadata is contextual for the detected home page role.
Supporting-source links
Supporting sources are contextual for the detected home page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 34 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OAI-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
GPTBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
ClaudeBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Claude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Claude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
GooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Google-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
BingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
PerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
ApplebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Applebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
MistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
MistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
meta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
meta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Amzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Amzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
CCBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
The image refreshes from FreeScan after a completed rescan. Clicking it always opens the newest public report saved for this exact scanned URL.
Scan evidence is included as untrusted data. The implementation brief instructs agents to verify findings before editing and to avoid destructive or speculative changes.
