Speed Insights
Grade A
99% performance
https://cryptocasinos.ph
LCP
544ms
Largest paint
TBT
16ms
Blocking time
CLS
0.001
Layout shift
78
out of 100
100
out of 100
111/111 rule points
63
out of 100
48/76 rule points
72
out of 100
68/94 rule points
76
out of 100
84/110 rule points
Category point breakdown
Biggest score-losing checks
Remove exposed sensitive files
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: 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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
$5 Free Bet
Play Now
Play Now
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Fix any of the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
Fix Prompt
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
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: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Fix 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
Horizontal overflow: 0px. Small tap targets: 43.
Priority
Priority 13: fix during launch polish.
Affected elements
Home
Crypto Casinos
Bitcoin (BTC) Casinos
Ethereum (ETH) Casinos
Fix Prompt
Improve detectable color 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
9 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.79.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
$5 Free Bet
Free Spins
Free Spins
Play Now
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
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: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 6 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
Sensitive file probes
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response. Failed: earned 0 of 16 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 1: fix before sharing the page publicly.
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
9 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.79. 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
$5 Free Bet
Free Spins
Free Spins
Play Now
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), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1). 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
$5 Free Bet
Play Now
Play Now
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Fix any of the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
Fix Prompt
Text density
Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 2489 visible word(s). General page range: 80-1800 words. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Spacing consistency
Why this needs attention
The page exposes few consistent spacing signals in class or inline styles.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Detected 2 spacing class/style signal(s). Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
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
Horizontal overflow: 0px. Small tap targets: 43. 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
Home
Crypto Casinos
Bitcoin (BTC) Casinos
Ethereum (ETH) Casinos
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 70/100. Detected 1 JSON-LD block(s), 0 parse error(s), 15 graph node(s), and types Answer, BreadcrumbList, FAQPage, ImageObject, ListItem, Organization, Question, WebPage, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 100/100 for “Crypto Casinos in the Philippines”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 100/100 from 1393 main-content words, 11 concise answer block(s), 8 question heading(s), 17 definition(s), 56 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 429 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://cryptocasinos.ph/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: 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. Purple 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.
