Speed Insights
Grade C
79% performance
https://www.snuh.org/main.do
From www.snuh.org/main.do
LCP
5.4s
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
57
out of 100
79
out of 100
119/150 rule points
60
out of 100
46/76 rule points
42
out of 100
40/94 rule points
66
out of 100
57/86 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
Remove insecure page resources
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 55 insecure asset or link reference(s).
Priority
Priority 4: 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 7 violation rule(s); 6 non-contrast rule(s) are scored here, including 5 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: aria-required-children (2), aria-required-parent (7), color-contrast (2), label-title-only (1), listitem (7).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
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 1 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
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 85/100, answer-ready text 40/100, semantic structured data 62/100. Detected role: tool (medium confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 1 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: 2 review and 2 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 1 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: 2 review and 2 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 85/100, answer-ready text 40/100, semantic structured data 62/100. Detected role: tool (medium confidence). Failed: earned 25 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 7 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
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
Detected 3 JSON-LD block(s). Primary types: Article, FAQPage, WebSite. No primary type matches the page role. The named entity is supported by visible page content. Failed: earned 6 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Schema quality and validity
Why this needs attention
The JSON-LD may parse, but its required facts, page-role relevance, visible-content agreement, or graph connections are incomplete.
Invalid structured data can be ignored by search and answer systems, even when visible page content is strong.
Recommended correction
Evidence
3 of 3 JSON-LD block(s) parsed. Semantic quality is 62/100: completeness 75/100, graph connectivity 10/100, primary types Article, FAQPage, WebSite, currently useful search-feature types Article, WebSite, and limited-eligibility types FAQPage. Nested types do not count as separate schema coverage. SearchAction is retired as a Google search feature and earns no coverage credit. Failed: earned 6 of 8 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 10: fix during launch polish.
Fix Prompt
Mixed content indicators
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 55 insecure asset or link reference(s). Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
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
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 1 image(s) with empty alt text that appear informative, out of 28. 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
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 1 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
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
77 of 268 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 37 of 151 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
병원소식 더보기
본문으로 바로가기
2026-09-11
2026-09-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 7 violation rule(s); 6 non-contrast rule(s) are scored here, including 5 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: aria-required-children (2), aria-required-parent (7), color-contrast (2), label-title-only (1), listitem (7). 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.
Affected elements
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parent role not present: tablist
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 16px/700 weight versus a 16px/400 median body style (1× size). Captured 19 supporting heading(s) and 36 action(s). The main heading has a clear rendered emphasis over body copy. 77 of 268 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: 4403ms. Load complete: 0ms. First contentful paint: 4448ms. Largest contentful paint: 5404ms. Total blocking time: 0ms. Cumulative layout shift: 0. Resources: 34. Scripts: 11. Images: 11. Third-party origins: 6. Transfer: 9120KB. Potential render-blocking resources: 10. Metrics outside the good range: DOMContentLoaded 4403ms (good at or below 2500ms); First contentful paint 4448ms (good at or below 2200ms); Largest contentful paint 5404ms (good at or below 2500ms; poor range); Transfer size 9120KB (good at or below 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.
DOMContentLoaded
1903ms over the rendered audit threshold.
First contentful paint
2248ms over the rendered audit threshold.
Largest contentful paint
2904ms over the rendered audit threshold.
Transfer size
6920KB over the rendered audit threshold.
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
Desktop horizontal overflow: 0px. Mobile horizontal overflow at 390px: 0px. WCAG 2.2 AA target-size failures: 6. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Slide1
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Slide2
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Slide3
Target has insufficient size (12px by 12px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20px instead of at least 24px.
Stop
Target has insufficient size (16px by 16px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 18.6px instead of at least 24px.
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 scanned URL was not found in the fetched sitemap.
Structured data
Semantic schema score 62/100. Detected 3 JSON-LD block(s), 0 parse error(s), 20 graph node(s), and primary types Article, FAQPage, WebSite. Completeness: 75/100. Graph connectivity: 10/100. No primary schema type matched the detected page role. The schema entity is supported by visible page content. Limited search eligibility: FAQPage. Retired search feature: SearchAction; no coverage credit is awarded.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 85/100 for “서울대학교병원”. Title/H1 token overlap is 100%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability scored 40/100 from 254 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 11 list(s), and 1 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 109 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 by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 6
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 6
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 6
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% 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 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 6
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 6
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 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 6
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 6
Synthetic probe: reachable · HTTP 200 · 88% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 6
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.
