with one click
page-cro
Analyze and optimize individual pages for conversion performance.
Menu
Analyze and optimize individual pages for conversion performance.
Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
Frontend design entry point: direction, design system, visual philosophy. Use whenever building or touching the look of any web UI (components, pages, dashboards, React/Vue/HTML-CSS) or when the user says "make this look better", "fix the spacing/layout", or mentions styling, color, type, or polish.
Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only design skills lack.
Automated visual tuning: a vision or video model rates rendered variants in a loop. Render several labeled variants into one artifact, ask the model to rate them and suggest better values, render the suggestions, ask it to pick the best, repeat until good — the model is the eye, you run the loop.
Human-in-the-loop web studio to tune AI-generated output by eye. Stand up a local interactive studio (sliders, pickers, drag handles) or an inline edit/highlight/comment annotation studio for prose & media, instead of guessing values or shipping a static comparison grid.
macOS screen recorder that captures the main display PLUS system audio via ScreenCaptureKit — no BlackHole/loopback driver, no sudo, just the standard Screen Recording permission. CLI-driven; fills the headless-screen-recording-with-system-sound gap QuickTime and `screencapture -v` can't.
| name | page-cro |
| description | Analyze and optimize individual pages for conversion performance. |
| risk | unknown |
| source | community |
| date_added | 2026-02-27 |
Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.
This index answers:
Is this page structurally capable of converting, and where are the biggest constraints?
It prevents:
This is a diagnostic score, not a success metric.
| Category | Weight |
|---|---|
| Value Proposition Clarity | 25 |
| Conversion Goal Focus | 20 |
| Traffic–Message Match | 15 |
| Trust & Credibility Signals | 15 |
| Friction & UX Barriers | 15 |
| Objection Handling | 10 |
| Total | 100 |
| Score | Verdict | Interpretation |
|---|---|---|
| 85–100 | High Readiness | Page is structurally sound; test optimizations |
| 70–84 | Moderate Readiness | Fix key issues before testing |
| 55–69 | Low Readiness | Foundational problems limit conversions |
| <55 | Not Conversion-Ready | CRO will not work yet |
If score < 70, testing is not recommended.
(Proceed only after scoring)
Analyze in impact order, not arbitrarily.
Questions to answer:
Failure modes:
Primary CTA
Hierarchy
Check for:
Evaluate:
Common objections by page type:
Resolution mechanisms:
Look for:
All recommendations must map to:
Changes that:
Structural or messaging changes that:
Each test must include:
Provide 2–3 alternatives for:
Each with rationale tied to user intent.
(Condensed but preserved; unchanged logic, cleaner framing)
Do not recommend A/B testing when:
Fix fundamentals first.
## When to Use
This skill is applicable to execute the workflow or actions described in the overview.
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.