Why has my conversion rate stopped improving even though every test looked reasonable?

Usually because the tests were aimed at things the page already did well enough. A page converts only as far as the question it answers worst allows, so a sharper headline or a shorter form barely moves the rate when the real gap is somewhere else, such as a visitor who cannot tell whether the product is meant for them. A run of flat, reasonable tests is useful information, because it tells you where the limit probably is not.

What should I test next when nothing I change moves conversion?

Sort what you have already shipped before adding anything new. Tag each past change with the visitor question it tried to answer, from whether the page is easy to take in through to whether the visitor can see themselves in it. The questions with no fixes against them are the likelier limit. Test the element that is meant to answer one of those, and write down in advance why you think it is the one the page is short of.

How do I know which part of the page is holding conversion back?

Look for the question the page answers worst, then look for evidence of it on the page itself. Analytics shows which step people leave from and recordings show how they move before leaving, but neither records which question went unanswered. Read the page as a first-time visitor would, write down what they need to believe before acting, and check whether anything on the page supports each belief. An audit does the same thing more systematically and ranks the candidates with a confidence level on each.

Is a conversion rate plateau a traffic problem or a page problem?

It can be either, and it is worth ruling out traffic first because that check is quicker. If the mix of sources or audience shifted around the time the rate flattened, a page written for the old visitors may be answering the wrong questions for the new ones. If the traffic mix has held steady and the rate still will not move, the limit is more likely on the page. Some plateaus are both, which is one reason a single fix rarely clears them.

Published October 1, 2026 · 10 min read

Conversion Rate Plateau: Find What Your Page Is Short Of

Conversion

Cracked, dry earth with a few green shoots pushing up through the fissures.

A farmer spreads more nitrogen on a field every spring and gets the same thin crop every autumn. The soil is short of something else, and until that arrives the extra nitrogen has nothing to work with. Carl Sprengel, a German agronomist studying what plants take from the soil, worked this out in 1828, and Justus von Liebig made the idea famous in his writing from 1840 onwards, which is why it is often called the Sprengel-Liebig law of the minimum today. Growth is set by whichever nutrient is scarcest, however generous the supply of everything else.

A conversion rate plateau is the point where a page's conversion rate stops responding to the changes you make. Tests come back flat, and the number sits in the same narrow band for a quarter or more while traffic keeps arriving.

Most advice for that situation amounts to trying harder. I think the farmer's problem is the better guide.

Conversion rate stopped improving: what the plateau is telling you

The usual reading of a plateau is that you have not optimised enough. The page is fine in outline, the thinking goes, and the rate will creep up again if you widen the test programme and try more elements: a different headline, a shorter form, a new hero image, another round on the button.

The law of the minimum says something less comfortable. If the page is short of one thing, every fix aimed at anything else was always going to barely move it, however well it was executed. That makes a flat test a piece of evidence. It tells you, with some confidence, where the limit is not. Most teams throw that evidence away and start the next test from the backlog, a list ordered by how easy each idea is to ship, with no column for which shortage the page actually has.

On a page, the nutrients are the questions a visitor needs answered before they act. Form length and button colour are nitrogen: easy to change and easy to measure, and after a year of work on a page they are usually in good supply. If the field is short of potassium, say a visitor who cannot tell whether handing over a work email is safe, a shorter form is more nitrogen on a field that never needed it.

Practitioners describe the result in almost exactly those terms. One person on r/analytics, writing on 4 June 2026 about an online store, put it this way: "kept assuming it was a checkout problem. simplified forms, added shop pay, bigger buttons. barely moved." A composite line we modelled from plateau research for a Head of Growth at a product-led SaaS company (a paraphrase of many people, so treat it as a sketch rather than a quote) lands in the same place: "We've optimized the obvious. Form length, button colors, page speed. Conversion hit a ceiling." Barely moved is exactly what the law predicts when every fix lands on a factor the page already had enough of.

What to test next: sort what you have already shipped

Before choosing what to test next, look backwards. List the last five to ten changes you shipped on the plateaued page, including the tests that lost. Then tag each one with the question it was trying to answer for the visitor. There are seven, and a visitor needs a yes to every one before they act:

Can I take this in without effort?
Is the next step obvious?
Does this feel safe?
Is the value clear before you ask me for something?
Are my worries answered?
Do the steps connect?
Is this for someone like me?

These are the human side of how we look at a page, and the dimensions breakdown goes through each one. A fix can touch more than one question. Tag it with the one it was mainly for.

Here is a claim I could be wrong about. On most plateaued pages, I expect the list to cluster on the first two questions, because those are the ones every best-practice checklist covers. Trim the form, sharpen the headline, make the button stand out, speed the page up. Checklists favour them because they are visible and simple to split-test. The later questions, the ones about safety and fit in particular, get far fewer tickets, partly because the fix is usually a sentence of copy or a piece of proof someone has to go and find, which rarely looks like work on a sprint board. They are also the elements a redesign quietly removes without anyone noticing.

The questions with no tags against them are the likelier limit. That gives you a place to look and nothing more yet. An unanswered question is what conversion friction looks like from the visitor's side: the point on the page where they hesitate because something they needed to know is missing.

Find the limiting factor on a page, and where the law gets it wrong

The strict version of the law has not survived in agronomy, and it would be dishonest to borrow it without saying so. In 1909 Eilhard Mitscherlich described yields responding to a nutrient along a curve of diminishing returns, so a plant still gains a little from something that is not its scarcest input. Later work on co-limitation found crops short of two nutrients at once, where adding either one alone does less than adding both.

That weakens the spine of this piece, and the weakness matters in practice. A page can be limited by two questions together, say safety and fit, and fixing one of them may move the rate only partly. Barely moved is the prediction for a fix aimed elsewhere, which leaves room for a small lift, and a small lift from a fix does not prove you found the limit, since it may sit inside the page's normal week-to-week wobble.

There is a second problem. You cannot always read the limiting factor off the page at all. Traffic mix and intent sit outside it. A page written for founders will plateau if paid search starts sending it procurement leads, and no change to the page will explain that. Session recordings do not settle it either, because they show where visitors stop and not which question went unanswered (the longer argument is in why session recordings don't show why users drop off).

When we audit a page, this sorting is the step we try to do in the open. The audit ranks candidate limiting factors and puts a confidence level on each, and the scoring is written out in the methodology. A top-ranked fix we rate LOW is one we are not sure about, and we would rather print that than round it up.

The clearest example we have is our own homepage at nudgent.com. Audit b9d328ee ran on 18 September 2026, on engine version 2-fable51. We had spent the fortnight before it on hero copy and CTA wording. The audit put its top-ranked friction on comfort, a question none of that work had touched: the field in the hero asks a visitor to paste a page address, and nothing beneath it says what happens to that data. Its third- and fourth-ranked findings were about trust, with no named user quotes on the page and a band of four statistics carrying terse labels and no sources. We had been adding nitrogen, if the audit read the page right. It is one audit of one page, and we have not yet measured whether closing the comfort gap moves our own rate, so it shows the method at work and proves nothing about the outcome.

What you can check on your own page this week

Take the tagged list and pick the question none of your shipped fixes touched. Find the one element on the page that is supposed to answer it, perhaps a line under the form or a customer name near the price. Read it the way a first-time visitor would, arriving from wherever most of your traffic comes from and carrying none of the context your team has. If you cannot find an element that answers the question at all, you have your first candidate.

Before the next test goes live, write one sentence in the ticket saying which question this test answers and why you believe that is the question the page is short of. If the honest answer is that it was next on the list, the plateau is setting your roadmap.

Your analytics will keep reporting the rate, and your testing tool will keep reporting which variant won. Neither of them records which question the page answers worst, so this is the one to sit with before the next sprint: which factor is limiting your page right now, and what evidence says it is that one rather than the last thing you fixed?

Frequently asked questions

01Why has my conversion rate stopped improving even though every test looked reasonable?
Usually because the tests were aimed at things the page already did well enough. A page converts only as far as the question it answers worst allows, so a sharper headline or a shorter form barely moves the rate when the real gap is somewhere else, such as a visitor who cannot tell whether the product is meant for them. A run of flat, reasonable tests is useful information, because it tells you where the limit probably is not.
02What should I test next when nothing I change moves conversion?
Sort what you have already shipped before adding anything new. Tag each past change with the visitor question it tried to answer, from whether the page is easy to take in through to whether the visitor can see themselves in it. The questions with no fixes against them are the likelier limit. Test the element that is meant to answer one of those, and write down in advance why you think it is the one the page is short of.
03How do I know which part of the page is holding conversion back?
Look for the question the page answers worst, then look for evidence of it on the page itself. Analytics shows which step people leave from and recordings show how they move before leaving, but neither records which question went unanswered. Read the page as a first-time visitor would, write down what they need to believe before acting, and check whether anything on the page supports each belief. An audit does the same thing more systematically and ranks the candidates with a confidence level on each.
04Is a conversion rate plateau a traffic problem or a page problem?
It can be either, and it is worth ruling out traffic first because that check is quicker. If the mix of sources or audience shifted around the time the rate flattened, a page written for the old visitors may be answering the wrong questions for the new ones. If the traffic mix has held steady and the rate still will not move, the limit is more likely on the page. Some plateaus are both, which is one reason a single fix rarely clears them.