Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Collection

Conversion Rate Troubleshooting

Conversion problems usually announce themselves as one of a handful of symptoms: a rate that fell after a relaunch, a rate that fell overnight with nothing redesigned, a rate that jumped with no change anyone can name, visitors leaving a landing page in the first seconds, forms that are started and never sent, forms that are sent and never arrive, phones converting far below desktops, and tests that never reach a verdict. Each page in this section starts from one of those symptoms, separates the causes in a diagnosis table, and gives a check, a fix, a verification step and a prevention habit for each. The method behind every cause is taught in a landing page, funnel, research or testing guide, and each page links to it rather than repeating it.

Looking for how to use this library? Read the guide below the list.

All 9 pages in this collection

How these pages work

Every page follows the same sequence. It opens by confirming that the symptom is real and locating it: which pages, which devices, which sources and which step of the journey. A diagnosis table then sets out what you can see, the check that confirms or rules out each cause, the cause and the fix. Each cause gets a short section with the fix, a way to verify that the fix worked and the habit that stops the fault returning, followed by a routine that catches the whole family of causes before the next release or campaign.

The pages do not re-teach method. How a page should be built is in the anatomy of a landing page; how to locate a leak step by step is in the funnel analysis tutorial; how to plan, run and read a test is in the experimentation section. A troubleshooting page sends you to the relevant section once a cause is confirmed, and a fix that changes what visitors see should go through a controlled A/B Test wherever the traffic allows one.

Which page to start from

Choose the row that matches what you can observe, not the cause you already suspect. The problem pages beneath this introduction are listed automatically, so each diagnosis appears here as soon as it is published; until then, the guide in the middle column holds the relevant checks.

What you are seeingStart withBackground
Conversion rate fell soon after a new site, template or relaunch went liveConversion rate dropped after redesignWebsite migration checklist
Conversion rate fell sharply on a particular day and nothing was redesignedConversion rate dropped suddenlyFunnel analysis
Conversion rate rose sharply and nobody can name a change that explains itConversion rate jumped overnightConfirmation and thank-you pages
Visitors leave a landing page within seconds of arrivingLanding page bounce rate highMessage match
Many visitors start a form and few submit itForm abandonment too highForms that convert
People say they sent the website form and nobody at the business received itWebsite form submissions not arrivingForms that convert
Phones convert far below desktops, month after monthMobile conversion rate far below desktopSpeed and mobile
Free trials start, but few become paying customers once they endFree trial users not converting to paidSign-up and trial-start flows
A test has run for weeks and still has no winnerA/B test not reaching significanceSample size and significance
Test results look wrong: uneven arms, swings, a winner that did not holdCommon testing pitfallsA/B testing guide

Measurement, traffic or page: rule them out in that order

Every conversion rate (CVR) has a numerator and a denominator, and both can move without a single visitor behaving differently. Check measurement first because it is the cheapest to confirm: compare the conversions in analytics with the orders, leads or bookings the business recorded for the same days. If the two disagree by more than usual, the problem is counting, and the analytics troubleshooting section owns the tag, consent and event faults. Check traffic second: break the period down by source, campaign and device. A new campaign, a change in an ad platform's targeting or a burst of automated visits changes who arrives, and a lower rate from a different crowd is not a page problem.

Only when the counting holds and the traffic mix is stable does the page come into question. Even then, the symptom usually points at a specific part of the journey. Fast exits from the first screen point at the Landing Page promise, speed or layout. Losses at a form point at fields, errors and doubts, the territory Nielsen Norman Group's form usability recommendations cover. Losses in a checkout point at costs, accounts and payment. When the clicks come from one ad platform and the fault lives only there, the platform's own hub, such as Google Ads troubleshooting or Meta Ads troubleshooting, is the better starting point.

When to run conversion research instead

A troubleshooting page answers one question about one symptom. When the rate has always been low rather than recently changed, when several symptoms appear together, or when nobody can say where in the journey visitors are lost, a research sprint is the better tool. The conversion research methods guide combines analytics, recordings, surveys and usability sessions to find where and why people leave; the research section turns those findings into hypotheses and a prioritised backlog; and the landing pages and funnel and checkout sections hold the fixes. The research sprint tutorial runs those methods on one funnel and one question until a backlog is ready, and the tutorials on session recordings and heatmaps, on-page polls and surveys, usability testing and expert review take one method at a time. The conversion rate optimisation pillar shows how research, testing, funnels and landing pages fit together.