Speed Insights
Grade A
97% performance
https://djf.pages.dev
LCP
608ms
Largest paint
TBT
0ms
Blocking time
CLS
0.09
Layout shift
49
out of 100
41
out of 100
62/150 rule points
82
out of 100
59/72 rule points
34
out of 100
19/56 rule points
51
out of 100
52/101 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
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 20/100, answer-ready text 0/100, semantic structured data 45/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit.
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Review introductory clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 0 H1 heading(s), 0 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 0 actionable CTA(s). The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Shorten the meta description
Why this needs attention
The meta description is 239 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 239 characters, above the 170-character maximum.
Priority
Priority 3: fix before sharing the page publicly.
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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 4 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 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: 0 review and 4 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: 0 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 20/100, answer-ready text 0/100, semantic structured data 45/100. Detected role: home (high confidence). Failed: earned 8 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 76 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 239 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 239 characters, above the 170-character maximum. 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
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 0 H1 heading(s) and 0 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Sitemap validity
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: 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 1 JSON-LD block(s). Primary types: CivilEngineer, LocalBusiness, ProfessionalService. No primary type matches the page role. The named entity was not clearly supported by visible page content. Failed: earned 3 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
1 of 1 JSON-LD block(s) parsed. Semantic quality is 45/100: completeness 100/100, graph connectivity 0/100, primary types CivilEngineer, LocalBusiness, ProfessionalService, currently useful search-feature types LocalBusiness. Nested types do not count as separate schema coverage. Failed: earned 5 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
Internal link basics
Why this needs attention
The page has too few detectable links to other public pages on the same site.
Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Recommended correction
Evidence
Detected 0 internal link(s). Failed: earned 0 of 6 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none. Failed: earned 5 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
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
Heading levels found: none. 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 main landmark(s) and 0 total 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
8 of 105 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 3 of 45 failed; worst ratio 3.77: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
Projetos
DJF
DJF Projetos e Construção LTDA MECREA 5069622765 · CNPJ 48.374.153/0001-25
© 2026 DJF Projetos e Construção LTDA ME. Todos os direitos reservados.
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 3 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: select-name (1), color-contrast (2), region (42). Failed: earned 10 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
Select element must have an accessible name
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation"
DJF Projetos e Construção LTDA ME CREA 5069622765 · CNPJ 48.374.153/0001-25
2026
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
Fix Prompt
Visible primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Hero clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 0 H1 heading(s), 0 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 0 actionable CTA(s). The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence). Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Text density
Why this needs attention
The page may not provide enough useful context for its detected role, or its rendered structure needs review.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 13 visible word(s). The contextual range is 120-1200 words for the detected home page role. Failed: earned 1 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
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
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 32px/600 weight versus a 19px/400 median body style (1.68× size). Captured 0 supporting heading(s) and 0 action(s). The main heading has a clear rendered emphasis over body copy. 8 of 105 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
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 45/100. Detected 1 JSON-LD block(s), 0 parse error(s), 25 graph node(s), and primary types CivilEngineer, LocalBusiness, ProfessionalService. Completeness: 100/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 20/100 for “DJF Projetos e Construção”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 0/100 from 0 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 0 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 52 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
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
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
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
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: index, follow
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
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
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
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: index, follow
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
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: index, follow
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
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.
