Testing, honestly
A/B testing in plain English, and when it does not work
An A/B test splits visitors between two versions of the same page at the same time. Half see the current page, half see the change, and the version that produces more calls and forms wins. Running both at once is the whole point. Comparing this month with last month mixes your change up with the weather, the season, a holiday week, and whatever your competitors did.
Why a small site often cannot run one
A test needs enough conversions to tell a real difference from luck. Take a page with 400 visitors a month converting at 3 percent. That is about 12 leads a month, or 6 for each version. A gap of one or two leads between them is noise, and it could flip next month. To prove even a large improvement, a page like that would need to run the test for about a year, and a modest one would take several years. By then too much else has changed for the answer to mean anything.
Plenty of local service pages sit in that range. For them, a promise of clean A/B tests on button colors is a promise the math cannot keep.
What we do when traffic is low
We fix what the evidence already shows, one change at a time, and compare calls and forms over matching periods before and after. We watch the trend over several weeks, check it against call tracking so a seasonal rush is not mistaken for a win, and undo anything that makes the numbers worse. Bigger changes need far less traffic to prove: a rewritten page against the old one is a large enough difference to show up far sooner than a new button color.
When we do run a test
Pages with steady traffic get real A/B tests, and landing pages for ads are often the best candidates because the volume is predictable. A test runs until it has enough data, even when one version looks ahead early, because early leads are the least reliable part of any test. The winning version goes live, and we keep tracking it month over month.