Landing Page CRO Analysis
Skill Purpose
Perform a comprehensive Conversion Rate Optimization (CRO) analysis on any landing page. This skill produces a section-by-section teardown with prioritized, actionable fixes that directly impact conversion rates.
When to Use
- User provides a landing page URL and asks for conversion optimization
- User asks for landing page feedback, review, or audit
- User wants to improve signup, lead capture, or purchase rates
- Triggered by
/market landing <url> or /market cro <url>
Dynamic Workflow orchestration
A CRO teardown is multi-angle: the 7 framework sections + copy + form + mobile +
speed + A/B are file-disjoint, independently verifiable analysis units. Run them
as a workflow, not a linear grind.
- Plan. Fetch the page once (browser tool / screenshot if available; raw HTML +
rendered text otherwise). Identify the page type (Step 1 table) — this sets the
benchmark weights every grader uses. Capture the evidence corpus (DOM, copy,
visible elements) so no sub-agent re-fetches blind.
- Fan out (parallel sub-agents, one per natural unit). Dispatch the disjoint
units concurrently against the same captured corpus:
- Hero + value prop + CTA copy (persuasion lens)
- Social proof + objection handling (trust lens)
- Features/benefits + copy scoring (clarity lens)
- Form + mobile + page-speed (friction/UX lens)
- A/B hypotheses + heat-map prediction (experiment lens)
Each returns section score (1-10), cited findings, and prioritized fixes.
- Adversarially verify (>=3 skeptic graders, 2-of-3 consensus). Before accepting
any section verdict, have skeptic lenses try to falsify it: (a) "is this finding
evidence-backed or asserted?" — reject any fix not tied to an observed element;
(b) "is the benchmark/CR claim real or invented?" — reject hallucinated numbers;
(c) "does this fix actually move conversion, or is it cosmetic?". A score survives
only with 2-of-3 agreement; on disagreement, re-grade with the cited evidence.
- Synthesize yourself. YOU merge the verified section verdicts into the weighted
Overall CRO Score, the unified prioritized fix list, and the final report — never
paste a sub-agent's section as the verdict.
- Loop-until-dry (unknown-size discovery). If the page has indeterminate repeated
units (N testimonial blocks, N pricing tiers, N feature rows, a long-scroll with
many sections), keep fanning out per discovered unit until a pass yields no new
convertible finding — then stop. Do not cap the page at 7 sections if it has more.
Scope discipline: analyze ONLY the page(s) given. No competitor crawl unless the user
asks (that is market-competitors). Single-URL asks stay single-URL.
How to Execute
Step 1: Identify the Page Type
Determine which type of landing page you are analyzing. This affects benchmark expectations and scoring weights.
| Page Type |
Primary Goal |
Good CR |
Great CR |
| Lead Capture |
Email/form submission |
5-10% |
15%+ |
| SaaS Signup |
Free trial or freemium signup |
3-7% |
10%+ |
| E-commerce Product |
Add to cart / Purchase |
2-4% |
5%+ |
| Webinar Registration |
Register for event |
20-30% |
40%+ |
| App Download |
Install app |
10-15% |
20%+ |
| Waitlist |
Join waitlist |
15-25% |
35%+ |
| Consultation Booking |
Schedule a call |
5-10% |
15%+ |
| Nonprofit Donation |
Make a donation |
2-5% |
8%+ |
Step 2: Run the 7-Point CRO Framework
Analyze each section in order. Score each section 1-10 and provide specific findings.
Section 1: Hero Section (Weight: 25%)
The first screen a visitor sees. This is where 80% of conversion decisions begin.
Checklist:
Scoring Criteria:
- 9-10: Headline is benefit-driven, specific, and compelling. CTA is clear and contrasting. Visual supports the message. Trust indicators present.
- 7-8: Strong headline and CTA but missing one element (trust badges, supporting visual, or specificity).
- 5-6: Generic headline or weak CTA. Missing multiple above-the-fold elements.
- 3-4: Headline is feature-focused or vague. CTA is below the fold or unclear.
- 1-2: No clear headline or CTA. Visitor cannot understand the offer within 5 seconds.
Section 2: Value Proposition (Weight: 20%)
How clearly the page communicates WHY someone should convert.
Checklist:
Evaluate Using the 4U Framework:
- Useful - Does it solve a real problem the visitor has?
- Urgent - Is there a reason to act now?
- Unique - Is it different from competitors?
- Ultra-specific - Are claims concrete, not vague?
Section 3: Social Proof (Weight: 15%)
Evidence that others trust and benefit from this product/service.
Types of Social Proof (ranked by persuasion power):
- Revenue/results metrics ("$2.4B processed", "500K users")
- Named customer testimonials with photos, titles, and companies
- Recognizable client logos
- Case studies with specific results
- Star ratings and review counts
- Media mentions ("As seen in...")
- Certifications and awards
- User-generated content
- Social media follower counts
Checklist:
Section 4: Features and Benefits (Weight: 15%)
How the page presents what the product/service includes.
Checklist:
Feature-to-Benefit Translation Check:
Bad: "AI-powered analytics dashboard"
Good: "See exactly which campaigns drive revenue -- AI analyzes your data so you don't have to"
Section 5: Objection Handling (Weight: 10%)
How the page addresses reasons a visitor might NOT convert.
Common Objections by Page Type:
| Objection |
How to Address |
| "Too expensive" |
ROI calculator, price comparison, money-back guarantee |
| "Not sure it works" |
Case studies, free trial, demo video |
| "Too complicated" |
Setup wizard, onboarding support, "get started in 5 minutes" |
| "Not sure I need it" |
Problem agitation, cost of inaction |
| "What if I don't like it?" |
Free trial, money-back guarantee, cancel anytime |
| "Is my data safe?" |
Security badges, compliance logos, privacy policy link |
| "I need to ask my team" |
Shareable comparison page, team trial, ROI one-pager |
Checklist:
Section 6: Call-to-Action (Weight: 10%)
The conversion mechanism itself.
CTA Button Checklist:
CTA Copy Scoring:
- Weak: "Submit", "Click Here", "Learn More"
- Medium: "Sign Up", "Get Started", "Download Now"
- Strong: "Start My Free Trial", "Get My Custom Report", "Claim Your Discount"
Section 7: Footer and Secondary Elements (Weight: 5%)
The bottom of the page and supporting elements.
Checklist:
Step 3: Copy Scoring
Score the overall page copy on 5 dimensions (1-10 each):
- Clarity - Can a visitor understand the offer in 5 seconds?
- Urgency - Is there a reason to act NOW vs later?
- Specificity - Are claims concrete with numbers, timeframes, outcomes?
- Proof - Are claims backed by evidence, data, or testimonials?
- Action Orientation - Does the copy drive toward a specific next step?
Calculate the Copy Score: average of all 5 dimensions, multiplied by 10 for a score out of 100.
Step 4: Form Optimization Audit
If the page has a form, evaluate:
| Element |
Best Practice |
| Field count |
Every additional field reduces conversion ~7%. Lead capture: 3-5 fields max. |
| Labels |
Use inline labels or floating labels. Avoid placeholder-only labels. |
| Button text |
Match the value proposition. "Get My Free Guide" > "Submit". |
| Error handling |
Inline validation. Specific error messages. Don't clear the entire form on error. |
| Multi-step |
Break long forms into steps with progress indicator. |
| Required vs optional |
Mark optional fields, not required ones. |
| Auto-fill |
Enable browser auto-fill for standard fields. |
| Field types |
Use appropriate input types (email, tel, url) for mobile keyboards. |
Step 5: Mobile Responsiveness Audit
Mobile accounts for 60%+ of web traffic. Check:
Step 6: Page Speed Impact Assessment
Reference these conversion impact benchmarks:
| Load Time |
Conversion Impact |
| 0-2 seconds |
Baseline (optimal) |
| 2-3 seconds |
-7% conversion rate |
| 3-5 seconds |
-20% conversion rate |
| 5-8 seconds |
-35% conversion rate |
| 8+ seconds |
-50%+ conversion rate |
Check for common speed issues:
- Unoptimized images (use WebP, lazy loading)
- Render-blocking JavaScript
- Missing browser caching
- No CDN
- Excessive third-party scripts
- Unminified CSS/JS
Step 7: Generate A/B Test Recommendations
Format each test as a hypothesis:
Template:
"If we [CHANGE], then [METRIC] will [IMPROVE/INCREASE] because [REASON]."
Example tests to consider:
- Headline variations (benefit-focused vs outcome-focused)
- CTA button color and text
- Social proof placement (above vs below fold)
- Form field count (reduce by 1-2 fields)
- Hero image vs hero video
- Long-form vs short-form page
- Adding urgency elements (countdown, limited spots)
- Price anchoring and presentation
- Testimonial format (text vs video)
- Adding a chatbot or live chat widget
Step 8: Heat Map Interpretation Guidance
Even without actual heat map data, provide guidance on:
- Expected attention zones based on page layout
- F-pattern vs Z-pattern reading based on content density
- Scroll depth predictions based on page length and content breaks
- Click probability zones based on visual hierarchy
- Rage click indicators (elements that look clickable but aren't)
- Dead zones where content may be ignored
Output Format
Generate a file called LANDING-CRO.md in the project root or output directory with:
# Landing Page CRO Analysis
## [Page URL]
### Analysis Date: [date]
---
## Overall CRO Score: [X/100]
## Page Type: [identified type]
## Current Estimated Conversion Rate: [estimate based on findings]
## Target Conversion Rate: [realistic improvement target]
---
## Section-by-Section Analysis
### 1. Hero Section [Score: X/10]
**Findings:**
- [specific observations]
**Fixes (Priority: HIGH/MEDIUM/LOW):**
- [specific, actionable recommendations]
[Repeat for all 7 sections]
---
## Copy Score: [X/100]
| Dimension | Score | Notes |
|---|---|---|
| Clarity | X/10 | [notes] |
| Urgency | X/10 | [notes] |
| Specificity | X/10 | [notes] |
| Proof | X/10 | [notes] |
| Action Orientation | X/10 | [notes] |
---
## Form Audit
[findings and recommendations]
---
## Mobile Audit
[findings and recommendations]
---
## A/B Test Recommendations
1. [Hypothesis format test]
2. [Hypothesis format test]
3. [Hypothesis format test]
---
## Prioritized Fix List
### Quick Wins (implement this week)
1. [fix with expected impact]
### Medium-Term (implement this month)
1. [fix with expected impact]
### Strategic (implement this quarter)
1. [fix with expected impact]
---
## Before/After Wireframe Suggestions
[Text-based wireframe descriptions of current vs recommended layout]
Output contract + VERIFY
Deliverable: LANDING-CRO.md (path above) containing — page type, Overall CRO Score
/100, all 7 section scores, Copy Score /100 table, form/mobile audits, A/B list, and a
prioritized fix list split Quick/Medium/Strategic. Before declaring done, VERIFY:
- Every section has a score AND >=1 cited finding (no empty sections).
- Every fix references a specific observed element on the page (selector, copy
snippet, or screenshot region) — not generic advice.
- The Overall CRO Score equals the weight-applied sum of section scores (re-compute it;
do not eyeball).
- Every benchmark/CR number is either from the Step-1 / Step-6 table in this skill or
explicitly labeled an estimate — zero invented statistics.
If any check fails, fix the report before returning it.
Key Principles
- Always tie recommendations to REVENUE IMPACT. Don't just say "change the button color" -- say "changing the CTA button to a contrasting color typically increases clicks 15-30%, which at your current traffic could mean X more conversions per month."
- Prioritize fixes by effort-to-impact ratio. Quick wins first.
- Be specific. "Improve your headline" is useless. "Change your headline from 'Welcome to Our Platform' to 'Cut Your Reporting Time by 75% -- Automated Analytics for Growth Teams' because it adds specificity, a quantified benefit, and targets a specific audience" is actionable.
- Reference industry benchmarks so the client understands where they stand.
- If you have access to the page via browser tools, take screenshots and reference specific elements.
- If the user has run
/market audit previously, incorporate those findings into the CRO analysis for a more complete picture.
Constraints
MUST DO
- Verify all claims with data or sources
- Cite the observed page element (selector / copy snippet / screenshot region) behind every finding — uncited findings are dropped
- Label any conversion-rate estimate as an estimate; never present an invented statistic as measured fact
- Include actionable recommendations, not just observations
- Consider the target audience and business context
- Provide specific examples, not generic advice
MUST NOT DO
- Make claims without supporting evidence
- Ignore the user's specific business context
- Provide generic one-size-fits-all recommendations
- Skip competitive or market context when relevant
1---2name: market-landing3description: >4 Landing Page CRO (Conversion Rate Optimization) teardown. Section-by-section5 forensic analysis of a landing page with prioritized, revenue-tied fixes:6 hero, value prop, social proof, features/benefits, objection handling, CTA,7 form, mobile, page speed, A/B test recommendations. Use when the user provides8 a landing page URL and asks to improve conversion / signup / lead / purchase9 rates, or asks for a landing page review, audit, teardown, or CRO analysis.10 Triggers (EN): "market-landing", "/market landing <url>", "/market cro <url>",11 "landing page audit", "CRO analysis", "improve conversion rate", "optimize12 signup page", "review my landing page", "why isn't my landing page converting".13 Triggers (FR): "audit landing page", "analyse CRO", "optimiser le taux de14 conversion", "ameliorer ma landing page", "ma page ne convertit pas",15 "audit page d'atterrissage". Do NOT trigger on full-brand or social-content16 asks (use market-brand / market-social) or generic copywriting (market-copy).17metadata:18 source: https://skillmd.com/skills/agentik-os/market-landing19 author: agentik-os20 version: "1.0.0"21 domain: marketing22 triggers: market-landing, marketing23 role: specialist24 scope: analysis25 output-format: report26---2728# Landing Page CRO Analysis2930## Skill Purpose31Perform a comprehensive Conversion Rate Optimization (CRO) analysis on any landing page. This skill produces a section-by-section teardown with prioritized, actionable fixes that directly impact conversion rates.3233## When to Use34- User provides a landing page URL and asks for conversion optimization35- User asks for landing page feedback, review, or audit36- User wants to improve signup, lead capture, or purchase rates37- Triggered by `/market landing <url>` or `/market cro <url>`3839## Dynamic Workflow orchestration4041A CRO teardown is multi-angle: the 7 framework sections + copy + form + mobile +42speed + A/B are *file-disjoint, independently verifiable* analysis units. Run them43as a workflow, not a linear grind.44451. **Plan.** Fetch the page once (browser tool / screenshot if available; raw HTML +46 rendered text otherwise). Identify the page type (Step 1 table) — this sets the47 benchmark weights every grader uses. Capture the evidence corpus (DOM, copy,48 visible elements) so no sub-agent re-fetches blind.492. **Fan out (parallel sub-agents, one per natural unit).** Dispatch the disjoint50 units concurrently against the *same captured corpus*:51 - Hero + value prop + CTA copy (persuasion lens)52 - Social proof + objection handling (trust lens)53 - Features/benefits + copy scoring (clarity lens)54 - Form + mobile + page-speed (friction/UX lens)55 - A/B hypotheses + heat-map prediction (experiment lens)56 Each returns section score (1-10), cited findings, and prioritized fixes.573. **Adversarially verify (>=3 skeptic graders, 2-of-3 consensus).** Before accepting58 any section verdict, have skeptic lenses try to *falsify* it: (a) "is this finding59 evidence-backed or asserted?" — reject any fix not tied to an observed element;60 (b) "is the benchmark/CR claim real or invented?" — reject hallucinated numbers;61 (c) "does this fix actually move conversion, or is it cosmetic?". A score survives62 only with 2-of-3 agreement; on disagreement, re-grade with the cited evidence.634. **Synthesize yourself.** YOU merge the verified section verdicts into the weighted64 Overall CRO Score, the unified prioritized fix list, and the final report — never65 paste a sub-agent's section as the verdict.665. **Loop-until-dry (unknown-size discovery).** If the page has indeterminate repeated67 units (N testimonial blocks, N pricing tiers, N feature rows, a long-scroll with68 many sections), keep fanning out per discovered unit until a pass yields no new69 convertible finding — then stop. Do not cap the page at 7 sections if it has more.7071Scope discipline: analyze ONLY the page(s) given. No competitor crawl unless the user72asks (that is `market-competitors`). Single-URL asks stay single-URL.7374## How to Execute7576### Step 1: Identify the Page Type77Determine which type of landing page you are analyzing. This affects benchmark expectations and scoring weights.7879| Page Type | Primary Goal | Good CR | Great CR |80|---|---|---|---|81| Lead Capture | Email/form submission | 5-10% | 15%+ |82| SaaS Signup | Free trial or freemium signup | 3-7% | 10%+ |83| E-commerce Product | Add to cart / Purchase | 2-4% | 5%+ |84| Webinar Registration | Register for event | 20-30% | 40%+ |85| App Download | Install app | 10-15% | 20%+ |86| Waitlist | Join waitlist | 15-25% | 35%+ |87| Consultation Booking | Schedule a call | 5-10% | 15%+ |88| Nonprofit Donation | Make a donation | 2-5% | 8%+ |8990### Step 2: Run the 7-Point CRO Framework91Analyze each section in order. Score each section 1-10 and provide specific findings.9293#### Section 1: Hero Section (Weight: 25%)94The first screen a visitor sees. This is where 80% of conversion decisions begin.9596**Checklist:**97- [ ] Headline is visible within 2 seconds of page load98- [ ] Headline communicates the primary benefit (not a feature)99- [ ] Headline is under 10 words100- [ ] Subheadline expands on the headline with specificity101- [ ] Primary CTA is above the fold102- [ ] CTA button color contrasts with the background103- [ ] CTA text is action-oriented (not "Submit" or "Click Here")104- [ ] Hero image or video supports the message (not generic stock)105- [ ] Trust badges or social proof visible above the fold106- [ ] Page loads in under 3 seconds107- [ ] No navigation menu competing with the CTA (for dedicated landing pages)108109**Scoring Criteria:**110- 9-10: Headline is benefit-driven, specific, and compelling. CTA is clear and contrasting. Visual supports the message. Trust indicators present.111- 7-8: Strong headline and CTA but missing one element (trust badges, supporting visual, or specificity).112- 5-6: Generic headline or weak CTA. Missing multiple above-the-fold elements.113- 3-4: Headline is feature-focused or vague. CTA is below the fold or unclear.114- 1-2: No clear headline or CTA. Visitor cannot understand the offer within 5 seconds.115116#### Section 2: Value Proposition (Weight: 20%)117How clearly the page communicates WHY someone should convert.118119**Checklist:**120- [ ] Clear statement of what the product/service does121- [ ] Specific outcomes or results promised122- [ ] Differentiation from alternatives (why THIS solution)123- [ ] Target audience is clear (visitor knows if this is for them)124- [ ] Benefits are quantified where possible (save X hours, increase Y%)125- [ ] Value proposition is scannable (not buried in paragraphs)126127**Evaluate Using the 4U Framework:**1281. **Useful** - Does it solve a real problem the visitor has?1292. **Urgent** - Is there a reason to act now?1303. **Unique** - Is it different from competitors?1314. **Ultra-specific** - Are claims concrete, not vague?132133#### Section 3: Social Proof (Weight: 15%)134Evidence that others trust and benefit from this product/service.135136**Types of Social Proof (ranked by persuasion power):**1371. Revenue/results metrics ("$2.4B processed", "500K users")1382. Named customer testimonials with photos, titles, and companies1393. Recognizable client logos1404. Case studies with specific results1415. Star ratings and review counts1426. Media mentions ("As seen in...")1437. Certifications and awards1448. User-generated content1459. Social media follower counts146147**Checklist:**148- [ ] At least 2 types of social proof present149- [ ] Testimonials include real names and photos150- [ ] Testimonials mention specific results or outcomes151- [ ] Social proof is placed near decision points (close to CTAs)152- [ ] Numbers are specific (not rounded - "11,847" beats "10,000+")153- [ ] Logos are recognizable to the target audience154- [ ] Social proof is recent and relevant155156#### Section 4: Features and Benefits (Weight: 15%)157How the page presents what the product/service includes.158159**Checklist:**160- [ ] Features are translated into benefits (what the feature DOES for the user)161- [ ] Content is scannable (icons, bullet points, short paragraphs)162- [ ] Visual hierarchy guides the eye through features163- [ ] Most important features/benefits are listed first164- [ ] Each feature section has a clear mini-headline165- [ ] Screenshots, demos, or visuals accompany feature descriptions166- [ ] Feature list is comprehensive but not overwhelming (3-7 key features)167168**Feature-to-Benefit Translation Check:**169Bad: "AI-powered analytics dashboard"170Good: "See exactly which campaigns drive revenue -- AI analyzes your data so you don't have to"171172#### Section 5: Objection Handling (Weight: 10%)173How the page addresses reasons a visitor might NOT convert.174175**Common Objections by Page Type:**176177| Objection | How to Address |178|---|---|179| "Too expensive" | ROI calculator, price comparison, money-back guarantee |180| "Not sure it works" | Case studies, free trial, demo video |181| "Too complicated" | Setup wizard, onboarding support, "get started in 5 minutes" |182| "Not sure I need it" | Problem agitation, cost of inaction |183| "What if I don't like it?" | Free trial, money-back guarantee, cancel anytime |184| "Is my data safe?" | Security badges, compliance logos, privacy policy link |185| "I need to ask my team" | Shareable comparison page, team trial, ROI one-pager |186187**Checklist:**188- [ ] FAQ section addresses top 3-5 objections189- [ ] Risk reversals present (guarantee, free trial, cancel anytime)190- [ ] Pricing transparency (no hidden fees or surprise costs)191- [ ] Security and privacy indicators where relevant192- [ ] Comparison with alternatives (if applicable)193194#### Section 6: Call-to-Action (Weight: 10%)195The conversion mechanism itself.196197**CTA Button Checklist:**198- [ ] CTA text describes the VALUE, not the action ("Get My Free Report" vs "Submit")199- [ ] CTA button is visually dominant (size, color, whitespace)200- [ ] CTA appears multiple times on long pages201- [ ] Secondary CTA exists for visitors not ready to commit202- [ ] CTA has supporting microcopy (e.g., "No credit card required")203- [ ] Button text uses first person ("Start MY trial" vs "Start YOUR trial")204- [ ] CTA is specific to the offer (not generic)205206**CTA Copy Scoring:**207- Weak: "Submit", "Click Here", "Learn More"208- Medium: "Sign Up", "Get Started", "Download Now"209- Strong: "Start My Free Trial", "Get My Custom Report", "Claim Your Discount"210211#### Section 7: Footer and Secondary Elements (Weight: 5%)212The bottom of the page and supporting elements.213214**Checklist:**215- [ ] Final CTA present at bottom of page216- [ ] Contact information or support options visible217- [ ] Privacy policy and terms of service linked218- [ ] Trust badges repeated near final CTA219- [ ] No competing links that lead away from conversion220- [ ] Copyright and legal information present221- [ ] Social media links (only if they support conversion, not distract)222223### Step 3: Copy Scoring224Score the overall page copy on 5 dimensions (1-10 each):2252261. **Clarity** - Can a visitor understand the offer in 5 seconds?2272. **Urgency** - Is there a reason to act NOW vs later?2283. **Specificity** - Are claims concrete with numbers, timeframes, outcomes?2294. **Proof** - Are claims backed by evidence, data, or testimonials?2305. **Action Orientation** - Does the copy drive toward a specific next step?231232Calculate the Copy Score: average of all 5 dimensions, multiplied by 10 for a score out of 100.233234### Step 4: Form Optimization Audit235If the page has a form, evaluate:236237| Element | Best Practice |238|---|---|239| Field count | Every additional field reduces conversion ~7%. Lead capture: 3-5 fields max. |240| Labels | Use inline labels or floating labels. Avoid placeholder-only labels. |241| Button text | Match the value proposition. "Get My Free Guide" > "Submit". |242| Error handling | Inline validation. Specific error messages. Don't clear the entire form on error. |243| Multi-step | Break long forms into steps with progress indicator. |244| Required vs optional | Mark optional fields, not required ones. |245| Auto-fill | Enable browser auto-fill for standard fields. |246| Field types | Use appropriate input types (email, tel, url) for mobile keyboards. |247248### Step 5: Mobile Responsiveness Audit249Mobile accounts for 60%+ of web traffic. Check:250251- [ ] CTA is thumb-reachable (bottom half of screen)252- [ ] Text is readable without zooming (16px minimum body text)253- [ ] Forms are usable on mobile (large tap targets, appropriate keyboards)254- [ ] Images resize properly and don't break layout255- [ ] No horizontal scrolling required256- [ ] Page loads under 3 seconds on 4G257- [ ] Click-to-call for phone numbers258- [ ] Sticky CTA bar on scroll (if applicable)259260### Step 6: Page Speed Impact Assessment261Reference these conversion impact benchmarks:262263| Load Time | Conversion Impact |264|---|---|265| 0-2 seconds | Baseline (optimal) |266| 2-3 seconds | -7% conversion rate |267| 3-5 seconds | -20% conversion rate |268| 5-8 seconds | -35% conversion rate |269| 8+ seconds | -50%+ conversion rate |270271Check for common speed issues:272- Unoptimized images (use WebP, lazy loading)273- Render-blocking JavaScript274- Missing browser caching275- No CDN276- Excessive third-party scripts277- Unminified CSS/JS278279### Step 7: Generate A/B Test Recommendations280Format each test as a hypothesis:281282**Template:**283"If we [CHANGE], then [METRIC] will [IMPROVE/INCREASE] because [REASON]."284285**Example tests to consider:**2861. Headline variations (benefit-focused vs outcome-focused)2872. CTA button color and text2883. Social proof placement (above vs below fold)2894. Form field count (reduce by 1-2 fields)2905. Hero image vs hero video2916. Long-form vs short-form page2927. Adding urgency elements (countdown, limited spots)2938. Price anchoring and presentation2949. Testimonial format (text vs video)29510. Adding a chatbot or live chat widget296297### Step 8: Heat Map Interpretation Guidance298Even without actual heat map data, provide guidance on:299300- **Expected attention zones** based on page layout301- **F-pattern vs Z-pattern** reading based on content density302- **Scroll depth predictions** based on page length and content breaks303- **Click probability zones** based on visual hierarchy304- **Rage click indicators** (elements that look clickable but aren't)305- **Dead zones** where content may be ignored306307## Output Format308309Generate a file called `LANDING-CRO.md` in the project root or output directory with:310311```markdown312# Landing Page CRO Analysis313## [Page URL]314### Analysis Date: [date]315316---317318## Overall CRO Score: [X/100]319320## Page Type: [identified type]321## Current Estimated Conversion Rate: [estimate based on findings]322## Target Conversion Rate: [realistic improvement target]323324---325326## Section-by-Section Analysis327328### 1. Hero Section [Score: X/10]329**Findings:**330- [specific observations]331332**Fixes (Priority: HIGH/MEDIUM/LOW):**333- [specific, actionable recommendations]334335[Repeat for all 7 sections]336337---338339## Copy Score: [X/100]340| Dimension | Score | Notes |341|---|---|---|342| Clarity | X/10 | [notes] |343| Urgency | X/10 | [notes] |344| Specificity | X/10 | [notes] |345| Proof | X/10 | [notes] |346| Action Orientation | X/10 | [notes] |347348---349350## Form Audit351[findings and recommendations]352353---354355## Mobile Audit356[findings and recommendations]357358---359360## A/B Test Recommendations3611. [Hypothesis format test]3622. [Hypothesis format test]3633. [Hypothesis format test]364365---366367## Prioritized Fix List368369### Quick Wins (implement this week)3701. [fix with expected impact]371372### Medium-Term (implement this month)3731. [fix with expected impact]374375### Strategic (implement this quarter)3761. [fix with expected impact]377378---379380## Before/After Wireframe Suggestions381[Text-based wireframe descriptions of current vs recommended layout]382```383384### Output contract + VERIFY385Deliverable: `LANDING-CRO.md` (path above) containing — page type, Overall CRO Score386/100, all 7 section scores, Copy Score /100 table, form/mobile audits, A/B list, and a387prioritized fix list split Quick/Medium/Strategic. Before declaring done, VERIFY:3881. Every section has a score AND >=1 cited finding (no empty sections).3892. Every fix references a *specific observed element* on the page (selector, copy390 snippet, or screenshot region) — not generic advice.3913. The Overall CRO Score equals the weight-applied sum of section scores (re-compute it;392 do not eyeball).3934. Every benchmark/CR number is either from the Step-1 / Step-6 table in this skill or394 explicitly labeled an estimate — zero invented statistics.395If any check fails, fix the report before returning it.396397## Key Principles398- Always tie recommendations to REVENUE IMPACT. Don't just say "change the button color" -- say "changing the CTA button to a contrasting color typically increases clicks 15-30%, which at your current traffic could mean X more conversions per month."399- Prioritize fixes by effort-to-impact ratio. Quick wins first.400- Be specific. "Improve your headline" is useless. "Change your headline from 'Welcome to Our Platform' to 'Cut Your Reporting Time by 75% -- Automated Analytics for Growth Teams' because it adds specificity, a quantified benefit, and targets a specific audience" is actionable.401- Reference industry benchmarks so the client understands where they stand.402- If you have access to the page via browser tools, take screenshots and reference specific elements.403- If the user has run `/market audit` previously, incorporate those findings into the CRO analysis for a more complete picture.404405## Constraints406407### MUST DO408- Verify all claims with data or sources409- Cite the observed page element (selector / copy snippet / screenshot region) behind every finding — uncited findings are dropped410- Label any conversion-rate estimate as an estimate; never present an invented statistic as measured fact411- Include actionable recommendations, not just observations412- Consider the target audience and business context413- Provide specific examples, not generic advice414415### MUST NOT DO416- Make claims without supporting evidence417- Ignore the user's specific business context418- Provide generic one-size-fits-all recommendations419- Skip competitive or market context when relevant