What to Test
Prioritizing experiments.
What to Test is a free Digital Marketing Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Digital Marketing Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Why Prioritize What You Test
You can test almost anything, but testing time and traffic are limited. Smart marketers choose tests by potential impact, not curiosity.
A good test targets a page or step that touches many users and sits close to revenue. Testing a button color on a low-traffic page wastes weeks for little learning.
Find High-Leverage Pages
Start where the money flows. Map your funnel and look for the steps with the biggest drop-off and the highest traffic.
A checkout page with 40% abandonment and 10,000 monthly visitors is a far better target than a thank-you page nobody complains about.
Funnel drop-off audit
Landing -> 100%
Product page -> 62% (-38%)
Add to cart -> 28% (-34%) <-- biggest leak
Checkout -> 19%
Purchase -> 11%Test Big Levers First
The biggest wins usually come from value proposition, headline, offer, and page layout, not tiny tweaks.
Changing your headline or pricing framing can shift conversion by double digits. Changing a font rarely does. Save micro-tests for after you have exhausted the big levers.
Categories of Testable Elements
Group ideas so you cover the full experience, not just the obvious bits.
Common categories: messaging (headline, copy), offer (price, bundle, guarantee), layout (above-the-fold order), social proof (reviews, logos), and friction (form fields, steps).
Test idea map
Messaging | new headline emphasizing outcome
Offer | annual vs monthly default
Layout | move pricing above features
Proof | add 3 customer logos
Friction | cut form from 7 to 3 fieldsReduce Friction
Every extra field, click, or distraction costs conversions. Friction tests are reliable winners because they remove work for the user.
Cutting a signup form from seven fields to three, or removing a forced account creation, often produces clear, repeatable lifts.
Score Ideas With ICE
Use a simple framework to rank a backlog of test ideas. ICE scores each idea on Impact, Confidence, and Ease, from 1 to 10.
Average the three. The highest scores go first. This keeps the team from arguing about opinions and focuses on expected value.
ICE scoring (1-10 each)
Idea: Shorten checkout form
Impact = 8
Confidence = 7
Ease = 9
Score = (8+7+9)/3 = 8.0 -> run firstAnchor Tests to Real Problems
The best test ideas come from data and user research, not brainstorms. Watch session recordings, read support tickets, and study analytics.
If users keep abandoning at the shipping step, that is your signal. Test ideas grounded in evidence convert more often than guesses.
One Change, One Variable
To know what caused a result, change one meaningful thing at a time in an A/B test. If you alter the headline and the layout and the price together, a win tells you nothing about why.
When you must test many changes at once, use multivariate testing, but only with enough traffic.
Avoid Local Maxima
Endless tiny tweaks can trap you at a local maximum. Sometimes you need a bold, radical redesign to discover a much higher peak.
Balance your roadmap: mostly safe incremental tests, plus occasional big swings that could unlock a step-change in performance.
Test roadmap balance
70% incremental (copy, layout, CTA)
20% structural (page flow, offer)
10% radical (full redesign concept)Match Tests to Traffic
Low-traffic pages cannot detect small effects in reasonable time. On thin traffic, only test changes expected to produce large lifts.
Reserve subtle optimizations for your highest-traffic pages where you can collect enough data to see a small difference clearly.
Build a Prioritized Backlog
Keep a living list of test ideas with their ICE scores, the problem they address, and the metric they should move.
This backlog turns optimization into a steady pipeline instead of random one-off experiments, and it makes your reasoning visible to stakeholders.
Backlog row
Idea | Add money-back guarantee badge
Problem | High price objection in surveys
Metric | Checkout completion rate
ICE | 7.3
Status | QueuedQuick Check
Which test should you prioritize first?
Recap: What to Test
Prioritize tests by impact, traffic, and proximity to revenue. Start with big levers like value proposition, offer, and friction before micro-tweaks.
Ground ideas in real data, score them with ICE, change one variable at a time, and maintain a prioritized backlog so optimization stays a disciplined pipeline.
Frequently asked questions
Is the “What to Test” lesson free?
Yes — the full text of “What to Test” is free to read here on the web, and the Digital Marketing Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Digital Marketing Academy course, upgrade to CoddyKit PRO.
What will I learn in “What to Test”?
Prioritizing experiments. You practise Digital Marketing Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Digital Marketing Academy?
No prior experience is required. Digital Marketing Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “What to Test” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Digital Marketing Academy lesson?
Yes. Every Digital Marketing Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.