Competing actions on the same page split the attention you had

6 days ago
3 min read

Updated: 4 days ago

Introduction

Pages accumulate requests. A form, a phone number, a newsletter sign-up, a download, a chat window, a link to a guide, a social follow button. Each was added by somebody with a reasonable objective, and collectively they present a visitor with a menu of unrelated decisions at the moment they were ready to take one.

The effect is not that each action gets a share of the traffic. It is that the total falls, because choosing between several unrelated options is more effortful than accepting a single obvious one, and a proportion of people resolve that effort by leaving. The remedy is subtraction, which is unpopular because every element has an internal advocate.

1. Competing actions on the same page reduce the total, not just the share

The mechanism worth understanding.

Adding a second request does not split the conversions between two options. It reduces the combined figure, because the decision itself is the cost. This is why pages get worse as they get more complete.

2. Decide what each page is for

The prerequisite.

One primary action per page, written down. A page that cannot name its objective in a sentence will accumulate requests indefinitely, because there is no basis for refusing any of them. The written objective is what lets you decline the next well-intentioned addition.

3. Distinguish the primary action from the escape routes

The useful distinction.

A phone number beside a form is not a competing action; it is the same action by another route. A newsletter sign-up beside a form is a different objective entirely, and it competes. The test is whether both routes end in the same outcome for the business.

4. Rank the secondary options visually

The compromise where you cannot remove.

If something must stay, it should look secondary: smaller, lower, less prominent, plain text rather than a button. Visual equality is what makes two options feel like a genuine choice.

5. Remove the requests that serve you rather than them

The audit criterion.

Social follows, newsletter sign-ups and downloads frequently exist because somebody has a metric, not because the visitor wanted them. On a page whose purpose is enquiries, they are a cost. Ask what each element was added for and whether that reason still applies.

6. Watch for automatic interruptions

The category that competes hardest.

Chat windows that open themselves, overlays, cookie dialogues that reappear. These interrupt at the moment of intent and are the most damaging form of competition on the page.

7. Put different objectives on different pages

The structural answer.

If you genuinely need newsletter sign-ups and enquiries, they can have their own pages. Combining them compromises both, and separation costs nothing.

8. Repeat the same action rather than adding others

The safe form of repetition.

The same request appearing three times down a long page is helpful. Three different requests is a menu. Repetition of one action is not competition.

9. Remove one thing and watch

The method.

Take the least defensible element off the page and compare enquiries over a quarter. Removal is the change most likely to help and the one businesses are least willing to try.

Be careful about removing genuinely useful routes. Some visitors need a phone number, some need an email address, and some need a way to ask a question without committing. Serving one intention through several channels is not the same as pursuing several intentions.

Conclusion

Give each page one objective and remove what competes with it.

Understand that additional requests lower the total rather than dividing it, write down what each page is for, distinguish alternative routes to the same action from genuinely different objectives, make anything secondary look secondary, remove requests that exist for your metrics rather than the visitor's needs, eliminate self-opening interruptions, separate different objectives onto different pages, repeat one action rather than adding others, and test by removing rather than adding.