メニュー
CRO lens — is slowness (LCP/CLS/INP) the thing suppressing conversion? Surveyed by the Analyst.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
CRO lens — are real users excluded from converting by contrast, target size, focus, or semantics? Surveyed by the Analyst.
CRO lens — does the wording lead with the visitor's value, specifically and concretely? Surveyed by the Analyst.
CRO lens — is the primary action obvious, singular, and labeled with a value-bearing verb? Surveyed by the Analyst.
CRO lens — what steps, fields, or hesitation points stand between intent and completion? Surveyed by the Analyst.
CRO lens — does the block show that others already chose this, at the moment of decision? Surveyed by the Analyst.
CRO lens — is there an honest reason to act now rather than later? Surveyed by the Analyst.
| name | cro-performance-as-conversion |
| description | CRO lens — is slowness (LCP/CLS/INP) the thing suppressing conversion? Surveyed by the Analyst. |
| license | Apache-2.0 |
| metadata | {"version":"1.1.0"} |
Lens question: Is the block losing conversions to speed — slow LCP, layout shift, sluggish interaction — rather than to clarity or trust?
Signal of the gap (DOM/RUM):
blocks/<block>/<block>.manifest.json); bounce that rises with load time.
If LCP/CLS are already healthy, this lens is the wrong one — do not pick it
just because it's measurable.Variant kind it implies: CSS-only (smaller assets, reserve space to kill CLS) or JS (defer/trim decorate work, push non-critical work to lazy/delayed). Note: this overlaps the platform's own performance budget — EDS targets a PSI score of 100 (aem.live "keeping it 100") — only pick it when speed is genuinely the binding constraint.