Speed Insights
Grade A
94% performance
https://calorie.alsn.kr
From calorie.alsn.kr
LCP
392ms
Largest paint
TBT
237ms
Blocking time
CLS
0.001
Layout shift
79
out of 100
87
out of 100
131/150 rule points
100
out of 100
72/72 rule points
76
out of 100
50/66 rule points
52
out of 100
57/110 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
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit.
Priority
Priority 4: 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 55/100, answer-ready text 20/100, semantic structured data 96/100. Detected role: home (high confidence).
Priority
Priority 6: 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 3 violation rule(s); 2 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: aria-hidden-focus (2), avoid-inline-spacing (18), color-contrast (9).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
ARIA hidden element must not be focusable or contain focusable elements
Fix all of the following: Focusable content should have tabindex="-1" or be removed from the DOM
ARIA hidden element must not be focusable or contain focusable elements
Fix all of the following: Focusable content should have tabindex="-1" or be removed from the DOM
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Fix Prompt
Review introductory clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 1 H1 heading(s), 8 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 0 actionable CTA(s). The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Improve 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: 437ms. Load complete: 784ms. First contentful paint: 392ms. Resources: 44. Scripts: 14. Images: 0. Third-party origins: 9. Transfer: 3074KB. Potential render-blocking resources: 5. Exceeded thresholds: Transfer size 3074KB (threshold 2200KB); Third-party origins 9 origins (threshold 8 origins).
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.
Total blocking time
37ms over the rendered audit threshold.
Transfer size
874KB over the rendered audit threshold.
Third-party origins
1 origins over the rendered audit threshold.
37v__ja0peant.css
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 3 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 3 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
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 55/100, answer-ready text 20/100, semantic structured data 96/100. Detected role: home (high confidence). Failed: earned 21 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
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
22 of 67 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.29. Mobile 390px viewport: 10 of 32 failed; worst ratio 2.29: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
9월 11일 (금)
검색
사진
커뮤니티
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); 2 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: aria-hidden-focus (2), avoid-inline-spacing (18), color-contrast (9). 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
ARIA hidden element must not be focusable or contain focusable elements
Fix all of the following: Focusable content should have tabindex="-1" or be removed from the DOM
ARIA hidden element must not be focusable or contain focusable elements
Fix all of the following: Focusable content should have tabindex="-1" or be removed from the DOM
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit. 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
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 1 H1 heading(s), 8 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 0 actionable CTA(s). The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence). Failed: earned 7 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
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 80 visible word(s). The contextual range is 120-1200 words for the detected home 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
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
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 24px/700 weight versus a 14px/400 median body style (1.71× size). Captured 1 supporting heading(s) and 0 action(s). The main heading has a clear rendered emphasis over body copy. 22 of 67 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: 437ms. Load complete: 784ms. First contentful paint: 392ms. Resources: 44. Scripts: 14. Images: 0. Third-party origins: 9. Transfer: 3074KB. Potential render-blocking resources: 5. Exceeded thresholds: Transfer size 3074KB (threshold 2200KB); Third-party origins 9 origins (threshold 8 origins). 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.
Total blocking time
37ms over the rendered audit threshold.
Transfer size
874KB over the rendered audit threshold.
Third-party origins
1 origins over the rendered audit threshold.
37v__ja0peant.css
Fix Prompt
Runtime console health
Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 0 site-authored console error(s) and 1 uncaught page error(s) during render. Samples: Minified React error #418; visit https://react.dev/errors/418?args[]=text&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 15: 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
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 96/100. Detected 1 JSON-LD block(s), 0 parse error(s), 3 graph node(s), and primary types SoftwareApplication, WebSite. Completeness: 100/100. Graph connectivity: 70/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 55/100 for “좋은 아침이에요”. Title/H1 token overlap is 0%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability scored 20/100 from 43 main-content words, 1 concise answer block(s), 1 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 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 24 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://calorie.alsn.kr/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
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 ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
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 searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
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.
