H
hostinger.com
CRO Recommendations — August 2026
9 Medium Page

Ambiguous pricing CTA

The 'Choose' button on pricing does not specify which plan it corresponds to, causing ambiguity in the funnel step.

CURRENT —
Full-page screenshot of the current page
scroll ↕ — this is the live page
⚠ Ambiguous pricing CTAThe 'Choose' button on pricing does not specify which plan it corresponds to, causing ambiguity in the funnel step.
Fix
Evidence

Observed on the live site

✓ Flagged independently by 1 of 7 analysts
Business case

If this change wins

0 – 0
orders per 1,000 visitors
Low
Effort — 0.5-2 days
Not A/B testable
At typical traffic
Detecting this needs about 1,941,808 visitors per variant. Ship it as a sequenced change and log the date instead.
Prioritisation

PXL score: 4 / 10

Assessed from the live page

QuestionAnswerPoints
Is the change above the fold?No0
Is the change noticeable in under 5 seconds?Yes2
Does it add or remove an element?Yes1
Does it run on a high-traffic page?Yes1
Verified by direct technical measurement?No0

Criteria that need your data

4 of these could not be answered from the live page. Session recordings, survey or support themes, and analytics access would raise the confidence of this ranking — they do not indicate a weaker finding.

QuestionAnswerPoints
Discovered via user testing?No0
Discovered via qualitative feedback (survey, support)?No0
Supported by heatmaps or session recordings?No0
Found via digital analytics or real-user field data?No0
Implementation

Hand this to your developer

Surface
Page — page
Problem
The 'Choose' button on pricing does not specify which plan it corresponds to, causing ambiguity in the funnel step.
Current state
cta: Choose (multiple); notes: Pricing section shows multiple price points but 'Choose' buttons lack plan labels.
Change
cta: Choose [Plan Name]; notes: Label each 'Choose' button with the specific plan name and term.
Acceptance criteria
GIVEN a first-time visitor on the affected page
WHEN the change is live
THEN Label each 'Choose' button with the specific plan name and term, with no regression at 375px and 1280px widths.
Tracking
event: cro_ambiguous_pricing_cta on interaction with the changed element; verify it fires in BOTH variants before opening traffic.
Success metric
conversion rate on the affected step
QA checklist
Chrome / Safari / Firefox · 375px + 1280px · keyboard reachable · screen-reader name present · no CLS introduced
Effort
Low — 0.5-2 days
Test plan
1,941,808 visitors per variant (95% significance, 80% power); not testable at current traffic.
Rollback
Feature-flag the change; revert the flag if the primary metric drops for 3 consecutive days.
← ‘website’ searchers land on both a tutorial and a sales pageCompeting CTAs on builder page →