Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://minikode.my.id
From minikode.my.id
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
53
out of 100
66
out of 100
68/103 rule points
61
out of 100
46/76 rule points
50
out of 100
47/94 rule points
35
out of 100
38/110 rule points
Category point breakdown
Biggest score-losing checks
Remove exposed sensitive files
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Fix Prompt
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 93%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/10.
Priority
Priority 2: fix before sharing the page publicly.
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: strict-transport-security. Missing: content-security-policy, 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
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 3 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (4), link-name (3), heading-order (1).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Crawler access
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 93%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 10/10. Failed: earned 13 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
Meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 178 characters. 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 H1 heading(s) and 0 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
Schema presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). 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
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 0 internal link(s). 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 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: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 4 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
Sensitive file probes
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response. Failed: earned 0 of 16 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 1: 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: none. 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 landmark element(s) or roles. 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
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
8 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.07. 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.
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 3 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (4), link-name (3), heading-order (1). 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 primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Detected 0 CTA candidate(s). Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
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 0 H1 heading(s) and 178 meta-description characters. Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Text density
Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 5 visible word(s). General page range: 80-1800 words. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
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 trust-signal keyword occurrence(s). 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 class/style signal(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 0 hierarchy signal(s) from headings, CTA, and emphasized text. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
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: 0px. Small tap targets: 14. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
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
The exact URL appears in the fetched sitemap with lastmod 2026-05-17.
Structured data
Detected 0 JSON-LD block(s), 0 parse error(s), and types none.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 2 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 5 visible words and 0 audience, use-case, pricing, or integration signals.
Authorship and accountability
Detected author or accountable entity: Minikode.
Published or updated date
No datePublished or dateModified value was detected in structured data.
Supporting-source links
No external supporting links were detected; this is contextual rather than a universal requirement.
Rendered content availability
Rendered audit completed with 181 visible text element(s).
Synthetic search-agent reachability
6 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://minikode.my.id/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: blocked by gptbot disallow: / · line 55
Probe: not tested for this control
Controls: robots meta: index, follow
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude model trainingClaudeBotModel training
Robots: blocked by claudebot disallow: / · line 46
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by googlebot allow: / · line 63
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: blocked by google-extended disallow: / · line 52
Probe: not tested for this control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by bingbot allow: / · line 66
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
Controls: robots meta: index, follow
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Probe: not tested for this control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: blocked · HTTP 403
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: blocked by meta-externalagent disallow: / · line 58
Probe: not tested for this control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotModel training
Robots: blocked by amazonbot disallow: / · line 34
Probe: not tested for this control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 31
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotModel training
Robots: blocked by ccbot disallow: / · line 43
Probe: not tested for this control
Controls: robots meta: index, follow
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.
