Speed Insights
Grade A
97% performance
https://m.blog.naver.com/reengki_songdo_leah/224297258760
LCP
1.7s
Largest paint
TBT
50ms
Blocking time
CLS
0.01
Layout shift
39
out of 100
44
out of 100
62/142 rule points
78
out of 100
56/72 rule points
63
out of 100
50/80 rule points
68
out of 100
52/77 rule points
Category point breakdown
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
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 OAI-SearchBot, Claude-SearchBot, PerplexityBot for this page path. GPTBot, ClaudeBot, Google-Extended, and 3 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 68%: discovery 28/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 0/10.
Priority
Priority 2: 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 40/100, answer-ready text 0/100, semantic structured data 0/100. Detected role: other (low confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
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 1 of 5 common public security controls. Present: referrer-policy. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none.
Priority
Priority 5: 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
Add meaningful image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 0 image(s) with no alt attribute and 7 image(s) with empty alt text that appear informative, out of 8. 0 empty-alt image(s) looked decorative and were not counted as failures.
Priority
Priority 11: fix during launch polish.
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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 1 review and 2 not applicable.
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 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, 7 medium, 1 low. Coverage: 1 review and 2 not applicable.
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 OAI-SearchBot, Claude-SearchBot, PerplexityBot for this page path. GPTBot, ClaudeBot, Google-Extended, and 3 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 68%: discovery 28/45, index and snippet eligibility 20/25, synthetic reachability 20/20, sitemap freshness 0/10. Failed: earned 10 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
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 40/100, answer-ready text 0/100, semantic structured data 0/100. Detected role: other (low confidence). Failed: earned 6 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
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
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
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 1 of 5 common public security controls. Present: referrer-policy. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none. Failed: earned 2 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
Image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 0 image(s) with no alt attribute and 7 image(s) with empty alt text that appear informative, out of 8. 0 empty-alt image(s) looked decorative and were not counted as failures. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: 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
7 of 28 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 0 of 11 failed. 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
κ΅μ¬ μλ΄

ποΈμ‘λ μ μμμ΄ β μ‘λ μ΄λ±μμ΄ 6μ κ΅μ¬μλ΄ (μ΄λ±λΆ)ποΈ

Reengki Leah
2026. 5. 26. 21:49
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); 3 non-contrast rule(s) are scored here, including 1 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: link-name (6), meta-viewport (1), region (2). Failed: earned 10 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
Links must have discernible text

Fix all of the following: Element is in tab order and does not have accessible text 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
Links must have discernible text

Fix all of the following: Element is in tab order and does not have accessible text 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
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text 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
Zooming and scaling must not be disabled
Fix any of the following: user-scalable=no on <meta> tag disables zooming on mobile devices
Fix Prompt
Text density
Why this needs attention
The page may not provide enough useful context for its detected role, or its rendered structure needs review.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 53 visible word(s). The contextual range is 80-1800 words for the detected other page role. Failed: earned 7 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 0 unique above-fold action(s), 1 body sample(s) below 14px, 1 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 0 unique above-fold action(s), 1 body sample(s) below 14px, 1 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. Failed: earned 2 of 7 points from partial coverage.
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
Rendered typography, geometry, and contrast show that the main heading is not distinct or legible enough, or that the hierarchy needs manual review.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
The rendered H1 is 14px/600 weight versus a 11px/400 median body style (1.27Γ size). Captured 1 supporting heading(s) and 0 action(s). The main heading has a clear rendered emphasis over body copy. 7 of 28 rendered text samples missed contrast targets, so hierarchy is not considered fully legible. Failed: earned 6 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: 1772ms. Load complete: 0ms. First contentful paint: 1552ms. Resources: 31. Scripts: 13. Images: 9. Third-party origins: 6. Transfer: 4531KB. Potential render-blocking resources: 15. Exceeded thresholds: Transfer size 4531KB (threshold 2200KB). 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.
Transfer size
2331KB over the rendered audit threshold.
ssp.web.sdk.js
jquery-1.12.4.min-049104e_https.js
LegoPostView-44287531_https.js
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 40/100 for βλΈλ‘κ·Έβ. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 0/100 from 31 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 0 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected other page role.
Published or updated date
Freshness metadata is contextual for the detected other page role.
Supporting-source links
Supporting sources are contextual for the detected other page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 6 visible text element(s).
Synthetic search-agent reachability
5 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-SearchBotFAIL Β· BLOCKED Β· Toggle crawler details
AI search
Robots: blocked by oai-searchbot disallow: / Β· line 9
Synthetic probe: not tested Β· access is unverified
Controls: robots meta: index,follow
OpenAIOpenAI model trainingGPTBotOPTED OUT Β· Toggle crawler details
Model training
Robots: blocked by gptbot disallow: / Β· line 6
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
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: index,follow
AnthropicClaude model trainingClaudeBotOPTED OUT Β· Toggle crawler details
Model training
Robots: blocked by claudebot disallow: / Β· line 18
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
AnthropicClaude searchClaude-SearchBotFAIL Β· BLOCKED Β· Toggle crawler details
AI search
Robots: blocked by claude-searchbot disallow: / Β· line 21
Synthetic probe: not tested Β· access is unverified
Controls: robots meta: index,follow
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: index,follow
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: index,follow
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT Β· Toggle crawler details
Data-use policy control
Robots: blocked by google-extended disallow: / Β· line 15
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
MicrosoftBing and CopilotBingbotPASS Β· ALLOWED Β· Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable Β· HTTP 200 Β· 100% sampled-content parity
Controls: robots meta: index,follow
PerplexityPerplexity searchPerplexityBotFAIL Β· BLOCKED Β· Toggle crawler details
AI search
Robots: blocked by perplexitybot disallow: / Β· line 12
Synthetic probe: not tested Β· access is unverified
Controls: robots meta: index,follow
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: index,follow
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: index,follow
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT Β· Toggle crawler details
Data-use policy control
Robots: blocked by applebot-extended disallow: / Β· line 27
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
Mistral AIMistral searchMistralAI-IndexPASS Β· ALLOWED Β· Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable Β· HTTP 200 Β· 100% sampled-content parity
Controls: robots meta: index,follow
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: index,follow
MetaMeta AI model and product datameta-externalagentOPTED OUT Β· Toggle crawler details
Model training
Robots: blocked by meta-externalagent disallow: / Β· line 24
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
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: index,follow
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED Β· Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index,follow
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: index,follow
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: index,follow
Common CrawlOpen web datasetsCCBotOPTED OUT Β· Toggle crawler details
Model training
Robots: blocked by ccbot disallow: / Β· line 30
Synthetic probe: not applicable to this policy 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. 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.
