Testing
How to Pick Your First Website Test After an Audit
Start with a problem on a page people already visit that affects something you care about, like a form or call button. Write one sentence saying what you'll change and what you expect. Pick the simplest test your traffic can support, and decide before you start how you'll judge it. On sites with little traffic, a careful before-and-after comparison often works better than an A/B test.
- The best first tests sit on busy pages and touch an action you care about.
- Write down your guess, and why, before changing anything.
- Pick big-payoff, low-effort ideas first.
- Small sites can learn a lot from before-and-after comparisons and recordings of real visits.
On this page
Audits are great at producing lists. Fifty findings, all true, none obviously first. A test turns that list into learning: you change one thing on purpose, watch what happens and keep what works.
Not Every Finding Is a Test
Some findings are just fixes. A broken link doesn't need a test. Neither does a missing page description or a form that stopped sending emails. Fix those and move on.
A finding is worth testing when you're not sure what to do, like "would a shorter form get more quote requests?" or "would visitors call more if the phone number were higher up?"
Pick the Right Spot
Good first tests usually have three things in common:
- Busy page. Plenty of people already see the page you're changing.
- Action that matters. It affects a form, call, booking or sale, not just clicks on a footer link.
- Quick to make. You can make the change in an afternoon, not a few months.
Write Down What You Expect
Before you change anything, write one sentence: what you'll change, what you expect to happen and why. Testers call this a hypothesis. It stops you from deciding afterward that whatever happened was the plan.
Vague
"Let's try a new button and see what happens."
Clear
"If we shorten the quote form from nine fields to five, more mobile visitors will finish it, because recordings show people quitting at the address fields."
The "because" matters most. It's what you actually learn, whether the test wins or not.
Choose a Test That Fits Your Traffic
| Approach | How it works | Good for |
|---|---|---|
| A/B test | Half of visitors see version A, half see version B, at the same time | Busy pages with lots of leads or sales |
| Before and after | Change the page, then compare matching time periods before and after | Smaller sites, simple changes |
| Watch and ask | Watch recordings of real visits or ask a few customers | Very low traffic, early ideas |
An A/B test needs enough leads or sales to tell a real difference from luck. If your page gets a handful of leads a month, a careful before-and-after comparison is usually more practical. We cover how to do that fairly in Did That Fix Actually Work?
Decide How You'll Judge It
Before you start, write down:
- The one number that decides it, like completed quote forms per week.
- How long it runs. Use full weeks so weekdays and weekends both count.
- What would make you stop early, like a broken form.
On the start date, add an annotation (a dated note on your charts) in GA4, so you can see later exactly when the change went live.
Where Moonlit Tools Fits
In Moonlit Tools, a recommended test becomes a task with a hypothesis, the planned change, a success measure and a saved baseline, then check-ins at 30, 60 and 90 days and a recorded decision. Moonlit Tools plans and measures the test. It doesn't split traffic. See a testing plan in the demo.
Frequently Asked Questions
What if my test "loses"?
You still learned something. Write down what happened and why you think so. A clear loss is more useful than a vague win.
Can I test more than one thing at once?
You can, but it's harder to know which change made the difference. For a first test, change one thing.
What tools do I need?
For a before-and-after test, Google Analytics (GA4) and a calendar. To see why people do what they do, Microsoft Clarity's recordings and heatmaps (maps of where people click and scroll) are free and very handy.
Sources
- Events and key events, Google Analytics Help
- About annotations, Google Analytics Help
- Microsoft Clarity, Microsoft
See What Google and AI Tools Can Read
Moonlit Tools reads your site the way search engines and AI assistants do, then tells you what to fix first and shows you why. Scan your own website free. No card needed.
Scan Your Site Free Or apply for 90 days of Launch free