Speed Insights
Grade A
98% performance
https://www.wvp.at/utf/index.php
From www.wvp.at
LCP
1.5s
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
51
out of 100
21
out of 100
31/142 rule points
72
out of 100
55/76 rule points
54
out of 100
51/94 rule points
75
out of 100
57/68 rule points
Category point breakdown
- Material high-impact failures span 3 categories.
Biggest score-losing checks
For your AI agent
Share this audit’s URL with ChatGPT, Claude, or your coding agent to turn findings into fixes. Your agent can open the saved evidence below when it needs more detail; these files never start a new scan.
Agent-readable files
Add common public security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Strengthen answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 35/100, answer-ready text 15/100, semantic structured data 0/100. Detected role: tool (medium confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Label public form fields
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 2 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
Fix Prompt
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 4 violation rule(s); 3 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 0 result(s) require review. Top rules: label (2), color-contrast (11), html-has-lang (1), page-has-heading-one (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
Elements must meet minimum color contrast ratio thresholds
Austria
Fix Prompt
Expand the meta description
Why this needs attention
The meta description is 3 characters, so it is too short to provide a useful search-result summary.
A very short description may not give searchers enough context to understand the page before clicking.
Recommended correction
Evidence
Meta description is 3 characters, below the 50-character minimum.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 1 review and 2 not applicable.
No failed checks in this category.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 1 review and 2 not applicable.
No failed checks in this category.
Failed checks
These checks need attention.
Answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 35/100, answer-ready text 15/100, semantic structured data 0/100. Detected role: tool (medium confidence). Failed: earned 8 of 40 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 9 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: fix during launch polish.
Fix Prompt
Meta description
Why this needs attention
The meta description is 3 characters, so it is too short to provide a useful search-result summary.
A very short description may not give searchers enough context to understand the page before clicking.
Recommended correction
Evidence
Meta description is 3 characters, below the 50-character minimum. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
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 0 visible H1 heading(s) and 1 visible heading(s) in the rendered page. Heading-level order is assessed separately under Accessibility. 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
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
robots.txt reachability
Why this needs attention
The standard crawler instruction file was not reachable.
A reachable robots.txt helps crawlers understand what they can index before launch traffic arrives.
Recommended correction
Evidence
HTTP 404 returned for robots_txt. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: fix during launch polish.
Fix Prompt
Sitemap validity
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
HTTP 404 returned for sitemap_xml. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
Fix Prompt
Relevant schema coverage
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
No JSON-LD schema blocks were detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 0 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Internal link basics
Why this needs attention
The page has too few detectable links to other public pages on the same site.
Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Recommended correction
Evidence
Detected 1 visible internal link target(s) in the rendered page. Failed: earned 0 of 6 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Common security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none. 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.
Fix Prompt
Visible cookie flags
Why this needs attention
The safe public scan could not inspect private or browser-set cookies, so cookie flag coverage was not verified.
Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Recommended correction
Evidence
Observed 2 cookie(s) without storing names or values. Secure: 0/2. HttpOnly: 0/2. SameSite: 0/2. SameSite=None without Secure: 0. Failed: earned 1 of 4 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Form labels
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 2 eligible user-facing form control(s). Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
Fix Prompt
HTML language
Why this needs attention
The html lang attribute is missing.
Screen readers use the language attribute to pronounce content correctly.
Recommended correction
Evidence
No html lang attribute was detected. The page text appears to be en, but detected language cannot replace an explicit declaration for assistive technology. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 19: lower-risk cleanup after urgent launch blockers.
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
21 of 30 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.84. Mobile 390px viewport: 11 of 17 failed; worst ratio 2.84: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
Austria
Bosnia and Herzegovina
Bulgaria
Croatia
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 4 violation rule(s); 3 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 0 result(s) require review. Top rules: label (2), color-contrast (11), html-has-lang (1), page-has-heading-one (1). 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.
Affected elements
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
Elements must meet minimum color contrast ratio thresholds
Austria
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
No canonical URL was detected.
Sitemap coverage and freshness
Sitemap coverage could not be verified.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and primary types none. Completeness: 0/100. Graph connectivity: 0/100. No primary schema type matched the detected page role. The primary schema entity was not clearly supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 35/100 for “WVP Group”. Title/H1 token overlap is 0%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 15/100 from 12 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 3 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected tool page role.
Published or updated date
Freshness metadata is contextual for the detected tool page role.
Supporting-source links
Supporting sources are contextual for the detected tool page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 13 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.
OpenAIChatGPT searchOAI-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: all
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: all
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. 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.
