| name | cro-friction-reduction |
| description | CRO lens — what steps, fields, or hesitation points stand between intent and completion? Surveyed by the Analyst. |
| license | Apache-2.0 |
| metadata | {"version":"1.1.0"} |
Friction Reduction
Lens question: What is between the visitor's intent and the completed action,
and can a step or a doubt be removed rather than added?
Signal of the gap (DOM/RUM):
- DOM: long forms, redundant fields, actions hidden behind hovers/accordions,
required scrolling to reach the action (
a.button below the fold in the block's
decorated DOM), modal interruptions.
- RUM: drop-off between impression and engagement; high bounce on a page whose
action is below the fold; time-on-block high but conversion low (hesitation).
Variant kind it implies: CSS-only when the fix is surfacing/reordering —
hoist the action above the fold or reveal a hidden control with flex/grid order
and visibility rules scoped to the block. CSS can only reorder what the block
already rendered; JS (a branch in the block's decorate path on
body.variant-<name>) when the fix changes behavior or structure (defer a field,
inline a step). Prefer the CSS framing first.
Related Skills
- building-blocks: the decorate contract and block-scoped DOM a reordering or behavioral variant works within.