Speed Insights
Grade A
98% performance
https://www.stackledge.com
LCP
640ms
Largest paint
TBT
11ms
Blocking time
CLS
0.009
Layout shift
77
out of 100
96
out of 100
145/150 rule points
75
out of 100
57/76 rule points
58
out of 100
55/94 rule points
86
out of 100
95/110 rule points
Category point breakdown
- Material high-impact failures span 2 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
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 14 image(s) with empty alt text that appear informative, out of 42. 3 empty-alt image(s) looked decorative and were not counted as failures.
Priority
Priority 11: 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 2 violation rule(s); 2 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-in-text-block (3), heading-order (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Links must be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Links must be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Links must be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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 78/100, answer-ready text 90/100, semantic structured data 96/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Fix 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
Visible heading levels found: 1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 4, 4, 4 (rendered page).
Priority
Priority 13: fix during launch polish.
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: 2 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: 2 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 78/100, answer-ready text 90/100, semantic structured data 96/100. Detected role: home (high confidence). Failed: earned 35 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: 1/1. HttpOnly: 1/1. SameSite: 0/1. SameSite=None without Secure: 0. Failed: earned 3 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
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 14 image(s) with empty alt text that appear informative, out of 42. 3 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
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
Visible heading levels found: 1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 4, 4, 4 (rendered page). 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
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
25 of 191 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.48. Mobile 390px viewport: 11 of 99 failed; worst ratio 2.48: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
Reviewed by hand, not scraped
What this is
As seen on
What this is
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 2 violation rule(s); 2 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-in-text-block (3), heading-order (1). Failed: earned 12 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 be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Links must be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Links must be distinguishable without relying on color
Fix any of the following: The link has insufficient color contrast of 2.61:1 with the surrounding text. (Minimum contrast is 3:1, link text: #4f46e5, surrounding text: #1b1f2a) The link has no styling (such as underline) to distinguish it from the surrounding text
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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: 5 unique above-fold action(s), 4 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), 4 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. More than three distinct actions compete in a captured first viewport. 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 60px/600 weight versus a 15px/400 median body style (4× size). Captured 9 supporting heading(s) and 14 action(s). The main heading has a clear rendered emphasis over body copy. 25 of 191 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: 1116ms. Load complete: 1987ms. First contentful paint: 640ms. Largest contentful paint: 640ms. Total blocking time: 11ms. Cumulative layout shift: 0.009. Resources: 47. Scripts: 3. Images: 37. Third-party origins: 16. Transfer: 856KB. Potential render-blocking resources: 2. Metrics outside the good range: Third-party origins 16 origins (good at or below 8 origins). Failed: earned 8 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.
Third-party origins
8 origins over the rendered audit threshold.
css2
style.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-09-24.
Structured data
Semantic schema score 96/100. Detected 1 JSON-LD block(s), 0 parse error(s), 4 graph node(s), and primary types CollectionPage, 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. 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 78/100 for “The tools that power your stack”. Title/H1 token overlap is 25%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 90/100 from 869 main-content words, 7 concise answer block(s), 2 question heading(s), 13 definition(s), 2 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 103 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://www.stackledge.com/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 oai-searchbot allow: / · line 50
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 36
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
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, max-image-preview:large
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by claudebot allow: / · line 78
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by google-extended allow: / · line 120
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 106
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
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, max-image-preview:large
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 20
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 20
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 20
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Controls: robots meta: index, follow, max-image-preview:large
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by ccbot allow: / · line 134
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow, max-image-preview:large
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.
