Speed Insights
Grade A
99% performance
https://agence-sparkevent.fr
LCP
720ms
Largest paint
TBT
0ms
Blocking time
CLS
0.005
Layout shift
33
out of 100
50
out of 100
72/142 rule points
80
out of 100
58/72 rule points
41
out of 100
33/80 rule points
77
out of 100
82/101 rule points
Category point breakdown
- Search discovery is materially blocked.
- 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
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Claude-User: No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Googlebot: No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Bingbot: No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. MistralAI-Index: No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Amzn-SearchBot: No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Amzn-User: No matching robots.txt rule blocks Amzn-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
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 1 of 5 common public security controls. Present: strict-transport-security. Missing: 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 70/100, answer-ready text 60/100, semantic structured data 0/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Expand the meta description
Why this needs attention
The meta description is 30 characters, so it is too short to provide a useful search-result summary.
A very short description may not give searchers enough context to understand the page before clicking.
Recommended correction
Evidence
Meta description is 30 characters, below the 50-character minimum.
Priority
Priority 3: 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 11 image(s) with empty alt text that appear informative, out of 15. 0 empty-alt image(s) looked decorative and were not counted as failures.
Priority
Priority 11: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 1 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 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 1 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 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.
Crawler access
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Claude-User: No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Googlebot: No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Bingbot: No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. MistralAI-Index: No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Amzn-SearchBot: No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. Amzn-User: No matching robots.txt rule blocks Amzn-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: max-image-preview:large. AEO crawler readiness is 25%: discovery 0/45, index and snippet eligibility 20/25, synthetic reachability 0/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 4 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
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 70/100, answer-ready text 60/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 20 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 94 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
Meta description
Why this needs attention
The meta description is 30 characters, so it is too short to provide a useful search-result summary.
A very short description may not give searchers enough context to understand the page before clicking.
Recommended correction
Evidence
Meta description is 30 characters, below the 50-character minimum. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: 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
No JSON-LD schema blocks were detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: 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 1 of 5 common public security controls. Present: strict-transport-security. Missing: 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 4 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
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 11 image(s) with empty alt text that appear informative, out of 15. 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
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: 2, 2, 2, 4, 2, 2, 2, 2, 3, 3, 3, 2, 2, 2, 2, 2, 1, 3, 3 (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
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 visible main landmark(s) and 4 visible landmark element(s) or roles. A page should expose one main landmark. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: 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
32 of 180 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 11 of 87 failed; worst ratio 1.94: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
À propos
Événementiel
Animation & Team building
Donnez vie à vos événements d’entreprise
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 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: heading-order (2), region (21). Failed: earned 14 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
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Heading levels should only increase by one
Fix any of the following: Heading order invalid
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 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: 753ms. Load complete: 2125ms. First contentful paint: 540ms. Largest contentful paint: 720ms. Total blocking time: 0ms. Cumulative layout shift: 0.005. Resources: 44. Scripts: 11. Images: 13. Third-party origins: 5. Transfer: 2463KB. Potential render-blocking resources: 13. Metrics outside the good range: Transfer size 2463KB (good at or below 2200KB). 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.
Transfer size
263KB over the rendered audit threshold.
index.min.js
icon-picker.js
jetpack-carousel.min.js
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
No canonical URL was detected.
Sitemap coverage and freshness
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and primary types none. Completeness: 0/100. Graph connectivity: 0/100. No primary schema type matched the detected page role. The primary schema entity was not clearly supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 70/100 for “Spark Event – Agence événementielle et animations”. Title/H1 token overlap is 100%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 60/100 from 369 main-content words, 1 concise answer block(s), 1 question heading(s), 0 definition(s), 4 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 82 visible text element(s).
Synthetic search-agent reachability
0 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-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: 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: max-image-preview:large
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: max-image-preview:large
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: max-image-preview:large
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: 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: max-image-preview:large
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: max-image-preview:large
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: max-image-preview:large
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: max-image-preview:large
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
AmazonAlexa user fetchesAmzn-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: max-image-preview:large
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy 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. 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.
