Partial collection. Some browser measurements or evidence images could not be collected. The report preserves available results; missing evidence is not a confirmed website defect. Affected: axe.
Speed Insights
Grade A
98% performance
https://tourismo.infinityfree.me
From tourismo.infinityfree.me
LCP
2.0s
Largest paint
TBT
0ms
Blocking time
CLS
0.001
Layout shift
35
out of 100
20
out of 100
23/88 rule points
75
out of 100
54/72 rule points
0
out of 100
0/38 rule points
67
out of 100
66/92 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
Add responsive viewport metadata
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Add a useful meta description
Why this needs attention
No meta description was detected in the public page metadata.
Without a description, search and answer previews may select less useful page text automatically.
Recommended correction
Evidence
No meta description was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Publish a valid sitemap
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
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Fix Prompt
Write a clear 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
No title tag was detected.
Priority
Priority 8: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 1 review and 2 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, 6 medium, 0 low. Coverage: 0 review and 4 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 3 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 1 review and 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 4 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, 7 medium, 1 low. Coverage: 3 review and 0 not applicable.
Failed checks
These checks need attention.
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
No title tag was detected. 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
No meta description was detected in the public page metadata.
Without a description, search and answer previews may select less useful page text automatically.
Recommended correction
Evidence
No meta description was detected. 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
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 302 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
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. 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
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
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
Visible heading levels found: 2, 1, 5, 6, 6 (rendered page). 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
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 visible main landmark(s) and 2 visible landmark element(s) or roles. A page should expose one main landmark. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
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
1 of 20 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 3.59. Mobile 390px viewport: 1 of 20 failed; worst ratio 3.59: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
✨ Explore Carranglan
Fix Prompt
Credibility and proof
Why this needs attention
The page does not expose enough verifiable credibility for its detected role.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 commercial proof signal(s) and 0 source or methodology signal(s) for this home page. 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
Responsive viewport basics
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
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: 692ms. Load complete: 1712ms. First contentful paint: 880ms. Largest contentful paint: 2028ms. Total blocking time: 0ms. Cumulative layout shift: 0.001. Resources: 30. Scripts: 7. Images: 8. Third-party origins: 5. Transfer: 22250KB. Potential render-blocking resources: 15. Metrics outside the good range: Transfer size 22250KB (good at or below 2200KB). Failed: earned 8 of 10 points from partial coverage.
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.
Transfer size
20050KB over the rendered audit threshold.
feedback.js
confirm-dialog.js
sweetalert2@11
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
The exact scanned URL was not found in the fetched sitemap.
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 0/100 for “an unnamed subject”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Content extraction captured only 0 main-content words while the browser measured 1318 visible words. Answer readiness needs review after complete content extraction.
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 25 visible text element(s).
Synthetic search-agent reachability
No synthetic search/discovery User-Agent probe completed for this page; this signal does not affect its score.
Optional LLM-readable summary
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OpenAIChatGPT searchOAI-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
OpenAIOpenAI model trainingGPTBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AnthropicClaude model trainingClaudeBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
AnthropicClaude user fetchesClaude-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
GoogleGoogle Search and AI featuresGooglebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
GoogleGemini data use and groundingGoogle-ExtendedPOLICY UNKNOWN · Toggle crawler details
Data-use policy control
Robots: unknown
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
PerplexityPerplexity searchPerplexityBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AppleSiri, Spotlight, and Safari searchApplebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: unknown
Synthetic probe: not tested · access is unverified
AppleApple foundation-model trainingApplebot-ExtendedPOLICY UNKNOWN · Toggle crawler details
Data-use policy control
Robots: unknown
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
Mistral AIMistral user fetchesMistralAI-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
MetaMeta AI model and product datameta-externalagentPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
AmazonAmazon model trainingAmazonbotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: unknown
Synthetic probe: not tested · access is unverified
AmazonAlexa user fetchesAmzn-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: unknown
Synthetic probe: not tested · access is unverified
Common CrawlOpen web datasetsCCBotPOLICY UNKNOWN · Toggle crawler details
Model training
Robots: unknown
Synthetic probe: not applicable to this policy control
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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
