Speed Insights
Grade D
66% performance
https://virtual-staging.app
LCP
1.5s
Largest paint
TBT
1010ms
Blocking time
CLS
0.009
Layout shift
82
out of 100
94
out of 100
142/150 rule points
73
out of 100
56/76 rule points
90
out of 100
85/94 rule points
73
out of 100
81/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
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
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 70/100, semantic structured data 90/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 1 violation rule(s); 1 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: empty-table-header (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Table header text should not be empty
Fix any of the following: Element does not have text that is visible to screen readers
Fix Prompt
Add role-appropriate credibility
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.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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: 1405ms. Load complete: 2868ms. First contentful paint: 1452ms. Largest contentful paint: 1452ms. Total blocking time: 1010ms. Cumulative layout shift: 0.009. Resources: 130. Scripts: 20. Images: 8. Third-party origins: 1. Transfer: 3063KB. Potential render-blocking resources: 5. Metrics outside the good range: Total blocking time 1010ms (good at or below 200ms; poor range); Transfer size 3063KB (good at or below 2200KB).
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
810ms over the rendered audit threshold.
Transfer size
863KB over the rendered audit threshold.
1085d1e03fb075c0.css
6ffc8ba568edc891.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 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: 1 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: 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: 1 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 85/100, answer-ready text 70/100, semantic structured data 90/100. Detected role: home (high confidence). Failed: earned 32 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
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
Visible cookie flags
Why this needs attention
The safe public scan could not inspect private or browser-set cookies, so cookie flag coverage was not verified.
Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Recommended correction
Evidence
Observed 1 cookie(s) without storing names or values. Secure: 0/1. HttpOnly: 0/1. SameSite: 1/1. SameSite=None without Secure: 0. Failed: earned 2 of 4 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: 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
11 of 464 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1.97. Mobile 390px viewport: 10 of 345 failed; worst ratio 1.97: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
AI加工を実行すると、写真は処理のため安全なクラウドストレージ（Cloudflare R2）にアップロードされます。
AI加工を実行すると、写真は処理のため安全なクラウドストレージ（Cloudflare R2）にアップロードされます。
日英中 物件紹介文について →
ホームステージング
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 1 violation rule(s); 1 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: empty-table-header (1). Failed: earned 17 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
Table header text should not be empty
Fix any of the following: Element does not have text that is visible to screen readers
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
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: 3 unique above-fold action(s), 5 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 3 unique above-fold action(s), 5 body sample(s) below 14px, 0 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 48px/700 weight versus a 16px/400 median body style (3× size). Captured 18 supporting heading(s) and 19 action(s). The main heading has a clear rendered emphasis over body copy. 11 of 464 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: 1405ms. Load complete: 2868ms. First contentful paint: 1452ms. Largest contentful paint: 1452ms. Total blocking time: 1010ms. Cumulative layout shift: 0.009. Resources: 130. Scripts: 20. Images: 8. Third-party origins: 1. Transfer: 3063KB. Potential render-blocking resources: 5. Metrics outside the good range: Total blocking time 1010ms (good at or below 200ms; poor range); Transfer size 3063KB (good at or below 2200KB). Failed: earned 4 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.
Total blocking time
810ms over the rendered audit threshold.
Transfer size
863KB over the rendered audit threshold.
1085d1e03fb075c0.css
6ffc8ba568edc891.css
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-10-13T00:00:00.000Z.
Structured data
Semantic schema score 90/100. Detected 2 JSON-LD block(s), 0 parse error(s), 19 graph node(s), and primary types FAQPage, Organization, SoftwareApplication, WebSite. Completeness: 81/100. Graph connectivity: 57/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content. Limited search eligibility: FAQPage.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 85/100 for “無料で試せるAIバーチャルステージング｜Virtual Staging”. Title/H1 token overlap is 100%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability scored 70/100 from 1452 main-content words, 13 concise answer block(s), 0 question heading(s), 0 definition(s), 8 list(s), and 1 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 352 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://virtual-staging.app/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 · 64% 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 · 64% 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 · 64% 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 · 64% 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 · 64% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 64% 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 · 64% 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 · 64% 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 · 64% 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 · 64% 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 · 64% 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 · 64% 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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
