In short
- People leave at one of three points: before the page paints, on the first screen, or at the form. Each has different causes and different fixes.
- The five usual causes are speed, a mismatch with what they searched for, no clear next step, a trust gap, and a phone layout that fights them.
- Analytics can show where they leave. It cannot show why. Look at the page the way they did, on their device.
- Fix in order: speed, then the first screen, then trust, then the form. Skipping ahead wastes the work.
- If the traffic is the wrong traffic, the site is not the problem. Check the source before you touch the page.
Every exit is a vote
Someone searches "emergency electrician near me" at 9:40 on a Sunday night. She taps your listing. The screen is white for four seconds. She taps back. Your analytics will record a visit, a bounce and a duration of a few seconds. Your phone will record nothing.
That is the whole problem, compressed. Traffic that does not convert is not a mystery and it is not bad luck. It is a set of small decisions made by strangers, each one a vote against something specific on the page or, often, against the page not being there yet. The votes are recorded. Most owners never read them, and the ones who do usually read the wrong number.
The good news is that the causes are few and they show up in a predictable order. This guide is about finding where your visitors leave, why, and what to fix first. It is not about how many leads you should be getting; the website leads guide does that math. This is about the leak.
Diagnose by where they leave
Before asking why, ask where. A visitor can leave at a handful of points, and each has its own set of causes.
| Where they leave | What you see in analytics | The usual cause |
|---|---|---|
| Before the page paints | Very short sessions, high bounce on mobile, a gap between ad clicks and page views | Speed. The page took longer than the visitor's patience, which on a phone is about three seconds. |
| On the first screen | Sessions of five to fifteen seconds, no scroll, no click | Mismatch. The page did not say the thing they searched for, or did not say it first, or looked untrustworthy at a glance. |
| After scrolling, without acting | Longer sessions, scroll depth, no call or form | No clear next step, or a trust gap a scroll did not close. They wanted to act and could not see how, or were not sure enough. |
| At the form | Form starts recorded, few form submits | The form. Too long, asks too much, breaks on a phone, or the button does not say what happens next. |
| On the phone specifically | Mobile converts far below desktop | The mobile layout. Buttons too small, number not tappable, text too small, layout shifting while it loads. |
If you do not have form-start events or a device split, [tracking setup](/services/conversion-tracking-setup) adds them in an afternoon.
The five causes, in the order they happen
Speed. The first and largest cause, because it happens before anything else has a chance. A page that takes four seconds on a phone loses a large share of its visitors before the headline paints, and those visitors never see the copy you spent weeks on. The speed guide gives the targets, and how fast a website should load explains what each second costs.
Mismatch. She searched for emergency service and landed on a home page that says "Welcome, family owned since 1994." The page may be fine. It is the wrong page for the search, or the right page saying the wrong thing first. Every landing page has to repeat, in its first line, the thing the visitor came for.
No clear next step. The page answers the question and then stops. There is a phone number somewhere. There is a Contact link in the menu. There is no button that says "Call now" or "Get a quote" where her thumb is. Visitors do not go looking for ways to give you money. The conversion guide is about this and only this.
Trust gaps. She is ready to call and something stops her. No reviews. Stock photos. No license number. No address. A copyright line from years ago. Any one of these can be enough at 9:40 on a Sunday. The trust guide lists the fixes.
Mobile. All four of the above, made worse by a layout that was designed on a desktop. Most visitors to a local business site are on a phone, and a page that "works" on a phone in the sense that it renders can still lose them at every step. The mobile guide shows what a page designed for a thumb looks like.
Visitors do not leave for complicated reasons. They leave because the page was slow, said the wrong thing, or gave them nothing to press.
How to read the analytics without fooling yourself
Analytics tools report dozens of numbers and most of them are noise. Here is the short path, using the standard Google Analytics setup most sites have.
- Start with the landing pages report, not the overview. Where do people arrive? The home page is usually one of several, and each landing page leaks in its own way.
- For each landing page, look at engagement rate and average time. A page with a 20 percent engagement rate and eight-second sessions is losing people on the first screen. One with 60 percent and no conversions is losing them later.
- Split by device. If mobile engagement is half of desktop, the problem is the phone layout or the phone speed.
- Split by source. Ad traffic that bounces while organic traffic converts means the ad promised something the page does not deliver. Organic traffic that bounces means the page does not match the searches that bring it.
- Check the form funnel. Form starts versus submits. Fewer than half finishing means the form is the leak.
- Then look at the page the way they did. Open the landing page on your phone, over cellular, and count the seconds. Read only the first screen. Ask what you would press. Analytics tells you where; only looking tells you why.
The fixes, in order
Order matters because each fix only shows results if the one before it is done. A shorter form does nothing for visitors who left before the page loaded.
- 1
Make it fast on a phone.
Compress the images, drop the scripts that do nothing, fix the layout shift. Aim for a headline that paints in under two seconds on cellular. This is the fix with the largest effect and it is usually a few days of a developer's time; site speed work is priced by the job.
- 2
Fix the first screen of each landing page.
The first line names what the visitor searched for. The phone number is visible. There is one button. Nothing moves, rotates or pops up. If the page is about drain cleaning, the words appear before the fold.
- 3
Close the trust gaps.
Two reviews with names near the top. A real photo. License, insurance, years, area served. The credibility checklist is the list; most items take an afternoon.
- 4
Shorten the path to acting.
A tappable phone number in the header. A button that says what happens when it is pressed. A form with three or four fields. If the form breaks on a phone, fix it before doing anything else on this list.
- 5
Match the page to the source.
If ads send people to the home page, build a landing page for the ad. If organic traffic lands on a page that does not answer its search, rewrite the first paragraph. The service page guide explains the structure.
- 6
Measure again.
One change, one month, one number. Then the next fix.
When it is not the site
Sometimes the analytics say the site is failing and the site is fine. The traffic is wrong. An ad campaign set to broad match sends people looking for a job to a page selling a service. A blog post ranks for a question that has nothing to do with buying. None of those visitors was ever going to call, and no fix on the page will change that.
The tell is the source split from the section above. If one source converts and another does not, the problem is the source. Fix the ad targeting, or accept that the blog traffic is for reach rather than leads. Our Google Ads waste piece covers the common causes on the paid side.
And if every source is leaving at the same spot, the site is the problem, and it is a fixable one. The free audit scores the speed, mobile and trust items in a few minutes. The conversion rate optimization service does the measuring and fixing month by month if you would rather not, and the redesign guide is for the rare case where the leak turns out to be the platform itself.
Find out what your site is actually doing.
A free audit scores your site on speed, mobile, SEO and security, and lists the fixes in order of what they are worth. Delivered as a PDF to your inbox.
Fix it or replace it? Find out before you spend.
Tell us what your site is doing wrong and we will tell you, in plain words, whether it needs a repair or a rebuild. Free, and the answer is yours either way.
Which of these sounds like you? (pick any)
Questions people ask
Straight answers
Because visitors are leaving at a specific point before they act, and the point tells you the cause. Very short visits mean the page is too slow on phones. Visits of a few seconds with no scrolling mean the first screen does not match what they searched for. Longer visits with no call or form mean there is no clear next step or a trust gap. Find the point in your analytics first, then fix that one thing.
The number matters less than what the bounces are. A service business page where most visitors call from the header will show a high bounce rate and be doing its job. A page where visitors leave in under ten seconds without calling is failing whatever the rate says. Track call clicks and form starts, split by device and by source, and judge the page on those rather than on bounce rate alone.
Two causes explain most of it. The page is slow on a phone, so they leave before it paints, or the first screen does not say the thing they searched for, so they go back to the results. Both are visible in analytics as very short sessions, and both are fixable: compress the images and remove unneeded scripts for speed, and rewrite the first line of each landing page to name the search it serves.
Open it on your phone over cellular, not office Wi-Fi, and count the seconds until you can read the headline. Past about three seconds, a meaningful share of visitors have already left. A free speed test gives the same answer with numbers. If mobile sessions in your analytics are much shorter than desktop sessions, speed is almost always the reason.
Usually because the site was designed on a desktop and merely shrunk. On a phone the text is too small, the buttons are too close together, the phone number is not tappable, the form is awkward, and the page is slower on a cellular connection. Most visitors to a local business site are on phones, so a layout that fights them loses most of the traffic. The mobile guide shows what a page built for a thumb looks like.
Not first. Most leaks come from speed, the first screen, trust gaps and the form, and each can be fixed on the site you have in days. A redesign resets rankings and tracking and may reproduce the same leak in a new layout. Redesign only when the fixes cannot be done on the platform, which usually means it cannot be made fast or cannot work properly on a phone.
Where to go from here