Speed Insights
Grade C
78% performance
https://adualliance.com
LCP
1.4s
Largest paint
TBT
638ms
Blocking time
CLS
0.000
Layout shift
65
out of 100
64
out of 100
96/150 rule points
75
out of 100
54/72 rule points
71
out of 100
57/80 rule points
70
out of 100
71/101 rule points
Category point breakdown
- 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
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
Shorten the meta description
Why this needs attention
The meta description is 199 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 199 characters, above the 170-character maximum.
Priority
Priority 3: 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 75/100, semantic structured data 40/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Publish a valid sitemap
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
Timed out while fetching sitemap_xml.
Priority
Priority 7: fix during launch polish.
Fix Prompt
Write a clear 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 78 characters.
Priority
Priority 8: 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 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 0 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.
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 75/100, semantic structured data 40/100. Detected role: home (high confidence). Failed: earned 28 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 78 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 199 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 199 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
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
Timed out while fetching sitemap_xml. 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: GeneralContractor. 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 40/100: completeness 100/100, graph connectivity 0/100, primary types GeneralContractor, currently useful search-feature types none. 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
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
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, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 2, 4, 4, 4, 3, 4, 4, 4, 4, 2, 3, 3, 2, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 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
1 of 122 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.66. 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
•
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 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: color-contrast (13), heading-order (2), region (3). 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
← Drag slider to reveal full transformation →
Permit Time
Est. Rent
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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), 14 body sample(s) below 14px, 0 cramped line-height sample(s), and 1 overlong line sample(s). The mobile composition pass did not complete. 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 96px/900 weight versus a 14px/400 median body style (6.86× size). Captured 31 supporting heading(s) and 16 action(s). The main heading has a clear rendered emphasis over body copy. 1 of 122 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: 1160ms. Load complete: 1957ms. First contentful paint: 1080ms. Largest contentful paint: 1380ms. Total blocking time: 638ms. Cumulative layout shift: 0. Resources: 49. Scripts: 14. Images: 1. Third-party origins: 9. Transfer: 12340KB. Potential render-blocking resources: 2. Metrics outside the good range: Total blocking time 638ms (good at or below 200ms; poor range); Transfer size 12340KB (good at or below 2200KB); Third-party origins 9 origins (good at or below 8 origins). Failed: earned 2 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
438ms over the rendered audit threshold.
Transfer size
10140KB over the rendered audit threshold.
Third-party origins
1 origins over the rendered audit threshold.
3086a2b1c0949d07.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
Sitemap coverage could not be verified.
Structured data
Semantic schema score 40/100. Detected 1 JSON-LD block(s), 0 parse error(s), 4 graph node(s), and primary types GeneralContractor. 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 85/100 for “ADU Builders Orange County”. Title/H1 token overlap is 100%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 75/100 from 1186 main-content words, 14 concise answer block(s), 1 question heading(s), 3 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 336 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://adualliance.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 71
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 68
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 claudebot allow: / · line 74
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by googlebot allow: / · line 80
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by google-extended disallow: / · line 52
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by bingbot allow: / · line 83
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 77
Synthetic probe: reachable · HTTP 200 · 98% 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 31
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by meta-externalagent disallow: / · line 58
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 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by amazonbot disallow: / · line 34
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by ccbot disallow: / · line 43
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.
