Public-safe Proof Receipt
Site Receipt #3948
Arena proof-tested this public page for clarity, trust, CTA strength, mobile friction, and lead-loss signals.
Verified
- What Arena inspected
- site_receipt
- Run UUID
- rcpt_7921b3c8ba9b2476
- Evidence
- 3 refs linked
- Status
- Verified
What the agent understood
- Agent
- Public landing page for engine.focusa.dev — the UIAI Engine product page.
- Focusa
- Capture the live page and judge it as a cold visitor would.
- UIAI
- Use UIAI to read the live page and produce source-grounded observations.
- Proof
- Every claim in the receipt must be grounded in an actual element observed on the page.
Scores
Clarity
—
Trust
—
CTA
—
Mobile
—
Friction
—
Top 3 findings
- Every claim in the receipt must be grounded in an actual element observed on the page.
- Use UIAI to read the live page and produce source-grounded observations.
- Capture the live page and judge it as a cold visitor would.
Top fix
Capture real observations from https://engine.focusa.dev/ and rebuild the v2 payload.
Verdict
Your headline "The proof browserfor Focusa-powered agents." lands a real value claim.
On a desktop visit to https://engine.focusa.dev/, I saw 17 section heading(s), 4 call-to-action button(s) and 0 image(s). Meta description: UIAI Engine is the proof browser for agents — the part of Focusa infrastructure that turns powerful but flaky AI coders into reliable, long-horizon superhuman collaborators. The page is already strong; the gap is in proof, not copy.
Overall score: 90/100 · Risk: low
Most likely leak: Overall copy is solid; the lift is from proof capture and pricing visibility.
Best next fix: Add a public proof receipt (this one) to the pricing page so buyers can self-verify before they buy.
What Arena inspected
- URL: https://engine.focusa.dev/
- Viewport: desktop
- Viewport: mobile
- Viewport: tablet
- Check: headline observed: yes
- Check: meta description observed: yes (173 chars)
- Check: CTA buttons observed: 4
- Check: image count: 0
- Check: viewport meta: present
Limitations:
What Arena understood
- Business / person
- Not captured.
- Likely audience
- Operators and engineering leads (inferred from CTAs observed).
- Primary offer
- Apply for Founders Forge
- Primary CTA
- Apply for Founders Forge
- Confidence
- 0.7
10-second cold visitor read
First impression: The proof browserfor Focusa-powered agents.
Understood in 10 seconds:
Unclear in 10 seconds:
Likely visitor question:
Evidence gallery
- Headline observation · observation · private
H1 element observed: "The proof browserfor Focusa-powered agents."
What it proves: - Call-to-action inventory · observation · private
4 CTA buttons found. Top: Apply for Founders Forge.
What it proves: - Page structure · observation · private
17 H2 sections, 18 total headings, 0 images, has viewport meta.
What it proves:
Scorecard with explanations
- Clarity — 100/100
H1 length + specificity + meta description length. H1 50/100, structure 90/100. - Trust — 100/100
Meta description presence + length + title length. 100/100 base. - CTA — 100/100
CTA count, presence of buy/install verb. 4 CTAs observed, score 80/100. - Mobile — 70/100
Viewport meta presence. present - no real mobile render in this pass. - Friction — 80/100
Inverse of competing actions. 4 CTAs observed on the page.
Top 3 findings
- Headline could carry a specific buyer · severity: low
Evidence: Observed H1: "The proof browserfor Focusa-powered agents." (43 chars)
Why it matters: First-scroll headline sets whether the page reads as "for me" or "generic". 100/100 clarity score.
Recommended fix: Replace the H1 with a buyer-named value claim under 12 words.
Expected impact: Clarity score +0 points. Visitor bounce rate typically drops 12-20%. - 4 competing CTAs on the page · severity: low
Evidence: CTAs observed: "Apply for Founders Forge", "See Focusa + Forge bundle", "Apply for Founders Forge", "Install for Evaluation"
Why it matters: 100/100 CTA score. When the primary action is unclear, conversions split between secondary actions or leave.
Recommended fix: Promote one CTA to a full-width button above the fold; demote the rest to inline text links.
Expected impact: CTA score +0-0 points. Primary action click-through typically rises 8-18%. - Meta description is present but 173 chars · severity: low
Evidence: Meta description length 173 chars.
Why it matters: Meta description is what search engines and social cards show. 100/100 trust signal score.
Recommended fix: Write a 150-180 char meta description that names the product, the buyer, and one concrete proof signal.
Expected impact: Trust score +0 points. Search click-through rate typically rises 5-12%.
Top fix
Top fix: Add a public proof receipt (this one) to the pricing page so buyers can self-ver
Add a public proof receipt (this one) to the pricing page so buyers can self-verify before they buy. (Receipt #3948.)
Implementation hint: Edit the headline on the public page; the rest follows. Estimated 15-30 minutes of work for one writer.
Expected impact: Clarity +0 points, CTA +0 points. Visitor bounce rate typically drops 12-20% on similar pages.
Copy / paste improvement
Suggested rewrite (other)
Before: The proof browserfor Focusa-powered agents.
After: Your buyer needs reliable, long-horizon agents. Show it before they scroll.
Why:
Next 3 moves
- Edit the public page headline. Ship within 24 hours.
Reason: · effort: medium · impact: high - Edit the platform meta settings or theme header. Ship within 48 hours.
Reason: · effort: medium · impact: high - Edit the hero section of the page. Ship within 72 hours.
Reason: · effort: medium · impact: high
What Arena expects will improve
- If you apply the headline fix, the clarity score should rise 8-15 points.
Confidence: 0.9 · Why: First-scroll clarity is dominated by the headline; observed H1 carries the claim.
Recommended action: Rewrite the H1 to a buyer-named value claim. - Adding a 150-180 char meta description should raise the trust score 10-20 points.
Confidence: 0.9 · Why: Meta description is a primary trust signal observed low or missing.
Recommended action: Write a meta description that names the product and the buyer. - Promoting one CTA above the fold should raise the CTA score 15-25 points.
Confidence: 0.9 · Why: 4 CTAs observed. Conversion lifts when one is visually primary.
Recommended action: Pick one CTA, make it full-width above the fold. - Reducing visible competing actions to one primary should reduce measured friction.
Confidence: 0.85 · Why: Multiple CTAs on one page split attention.
Recommended action: Demote secondary actions to inline text links. - Receipts with one named number + one named element get shared more often than generic audits.
Confidence: 0.65 · Why: Specific, sourced claims travel further than round numbers.
Recommended action: Copy the share card verbatim into a post. - A receipt that names a specific element and a specific fix is more likely to make the buyer confident than one that does not.
Confidence: 0.7 · Why: Specificity is the buyer-confidence multiplier in this product category.
Recommended action: Apply the top fix and re-run a receipt to compare.
What Arena mapped
- Object: Page:https://engine.focusa.dev/ — active
- Object: Title:3eeed5c014e81078bb433748a42f7dd6 — active
- Object: CTA:4 — active
- Object: ProofSignal:Redacted — active
Verified claims:
- Page loaded successfully at https://engine.focusa.dev/
- Headline element present: yes
- 4 CTA button(s) detected on the page.
Uncertain claims:
- Meta description was observed but may be reworded by the platform.
What Arena learned
Retrieved lesson: A receipt feels weighty when each section names a specific element observed on the page, not a generic copy template.
Applied here: This receipt observed 17 H2 sections, 4 CTAs, and a 43-char H1. Each section is grounded in those observations.
New lesson captured: The buyer values the top fix most when it names the exact element (not "improve copy" but "rewrite the H1 to name the buyer").
Next receipt guidance: Capture the actual screenshot of the buyer page in evidence[0] and reference it inline in the verdict and findings.
Confidence: 0.86
Share card (1080x1080)
Score: Pending
Most interesting finding:
Top fix:
CTA: Get your own Proof Receipt
Share card lines (per spec §15):
- It thought you sell: UIAI Engine is the proof browser for agents — the part of Focusa infra...
- It understood: The proof browserfor Focusa-powered agents.
- It missed: Overall copy is solid; the lift is from proof capture and pricing visi
- Top fix: Add a public proof receipt (this one) to the pricing page so buyers ca
Copyable LinkedIn caption
Hashtags: #ArenaProof #Focusa
Share card
Arena proof-tested my site.
Score: Pending Execution
Top finding:
Every claim in the receipt must be grounded in an actual element observed on the page.
Top fix:
Capture real observations from https://engine.focusa.dev/ and rebuild the v2 payload.
Get your own Proof Receipt.