Loading tutorials…
Loading tutorials…
Typeform Insights shows you where respondents drop off. Most teams glance at it once and miss the patterns. This walks through the diagnostic sequence specialists use to lift completion 15-30%.
Who this is forAnyone with a live Typeform where completion rate has stagnated below 50%. The fixes are usually structural, not creative. Most teams find the leak in under an hour with the right framework.
What you'll need
Step 1
Open Insights → Results → Drop-off rate per question. The first question with a >20% drop is your prime suspect.
Open the form → Results → Insights.
Look for "Drop-off rate" per question. Typeform shows what % of respondents abandon at each question.
The expected baseline: 5-10% drop per question on a healthy form. Anything above 20% on a single question is a problem.
The first question with >20% drop is your prime suspect. Fix that one first before touching the rest of the form.
Step 2
Why are respondents bailing here? Common causes: too personal too early, required field they cannot answer, free-text field they do not want to type, field type mismatch.
Open the prime-suspect question. Read it as a respondent would. Ask: 'Would I answer this with a stranger in question 2?'
If the question asks for email, phone, name, or contact info early — move it to the last 1-2 questions.
If the question is a long-text or short-text field — consider replacing with multiple-choice if possible.
If the question is required but respondents may not have an answer ("What is your team size in Q3 next year?") — make it optional.
If the question is dropdown with 12+ options — convert to multiple-choice with the top 4-5 options + "Other."
Step 3
Each additional question past 7 cuts completion ~5-10%. Count questions. If over 8, plan to cut.
Count total questions in the form. 5-8 is the sweet spot. Past 10, completion drops sharply.
For each question past 7, ask: "Could I get this answer from a different source (CRM, enrichment tool) or follow-up email?"
If yes, cut the question. Email follow-up is free; lost leads cost money.
Common cuts: phone (use email enrichment), company size (use Clearbit/Apollo enrichment), title (often inferable from email domain).
Step 4
Required fields cause hard stops. Count how many fields are required. More than 3 = problem.
Open the form editor. For each question, check the "Required" toggle.
Required fields should be: email + one qualification field. That is 2 fields.
Anything beyond 3 required fields will cause hard-stops. Optional fields can still be answered — they just do not block submission.
Phone, name, company should be OPTIONAL even on lead-gen forms. You can request post-submission.
Step 5
Desktop completion rate is irrelevant. 60-70% of responses come from mobile. Test on real iPhone Safari and Android Chrome.
Copy the preview link to your iPhone. Open in Safari. Walk through the entire form.
Look for: auto-zoom on email fields (iOS bug if input lacks proper attributes), buttons that shift off-screen, picture-choice images that load slowly, dropdown menus that misalign.
Repeat on Android Chrome — font rendering and keyboard behavior differ.
Time the mobile completion. If it takes more than 90 seconds, the form is too long for mobile.
Fix mobile-specific issues by adjusting font size, reducing question count, or simplifying field types.
Step 6
Typeform pages with heavy media (background videos, picture-choice with large images) take 5-8 seconds to load on mobile. 30% of mobile users bail before the first question renders.
Run the form URL through PageSpeed Insights (mobile profile).
Look at "Largest Contentful Paint" — target under 3 seconds. If over 5 seconds, you have a load problem.
Common culprits: background video on welcome screen, picture-choice with un-optimized images, custom fonts that block render.
Fix: compress images (TinyPNG), remove background video, swap custom font for system font on welcome screen.
Step 7
Change ONE variable. Wait 7-14 days. Compare completion rate. Do not stack changes — you will not know which one moved the needle.
Pick the highest-impact diagnostic finding. Change ONLY that.
Wait 7-14 days for fresh data (or 100+ new responses, whichever comes first).
Compare new completion rate to baseline. If it lifted, keep the change. If not, revert.
Move to the next hypothesis.
Stacking changes is how teams "fix" a form for 6 weeks and end up worse than they started — too many variables, no signal.
Common mistakes
Glancing at Insights without identifying the prime-suspect question
What goes wrong: You see overall completion is low but can't pinpoint where the drop happens. Optimization is shotgun, not targeted. Months of fiddling without lift.
How to avoid: Always identify the SINGLE highest-drop question first. Fix that. Re-measure. Then move to the next.
Too many required fields
What goes wrong: Respondents hit a red 'this field is required' error and bail. ~10-15% of submissions die at the first required-field block.
How to avoid: Only email + one qualification field should be required. Phone, name, company optional.
No mobile testing
What goes wrong: Form looks fine on desktop. Mobile completion is 30% because the email field auto-zooms and breaks layout. You don't notice because you only check the form from your laptop.
How to avoid: Test every form on real iOS Safari + Android Chrome before publishing. Mobile is 60-70% of traffic.
Heavy media on welcome screen
What goes wrong: Welcome screen with background video takes 6 seconds to load on mobile. 30% bail before the first question renders. You blame the form copy when the issue is page weight.
How to avoid: Run the form through PageSpeed Insights. Remove background video, compress images, swap custom fonts for system fonts. Target LCP under 3 seconds.
Stacking changes without measuring
What goes wrong: You change 5 things at once. Completion lifts 4% (within noise). You cannot tell which change caused the lift. Next time you can't replicate it.
How to avoid: Change one thing. Wait 7-14 days. Measure. Iterate. Slow beats wrong.
Recap
Done — what's next
How to build a Typeform survey that actually gets completed
Read the next tutorial
Hand it off
Diagnosing this once is a project. Keeping completion rate high every quarter is a job. Specialists run monthly drop-off audits, quarterly mobile retests, and ongoing form-length optimization. From $14-16/hr — most ongoing engagements land at $200-600/mo depending on form volume.
See ongoing optimization rates
For lead-gen: 50-70%. For NPS/customer feedback: 60-80%. For long surveys (10+ questions): 30-50% is acceptable. Below 40% on a lead-gen form is a problem worth diagnosing.
Three usual causes: (1) form is too long for mobile attention spans, (2) email field auto-zoom on iOS Safari breaks layout, (3) page load time exceeds 5 seconds.
Not natively. Duplicate the form, change the variable, split traffic via UTM or VWO/Optimizely. Compare completion rates across variants.
After a single change, 7-14 days OR 100+ new responses, whichever comes first. Anything sooner is noise.
Typeform
Typeform's one-question-at-a-time UX is what makes it convert — and what makes it brittle. This walks through how to structure questions, pick the right field types, and ship a survey that hits 60%+ completion rate.
Typeform
Logic jumps are what turn Typeform from a survey into a smart funnel. Done right, they route every respondent to a personalized path. Done wrong, they create dead ends and respondents stuck on the wrong branch.
Typeform
Typeform captures the lead. Your CRM and email tool nurture it. The connection between them is where 90% of lead-routing problems hide. This walks through the right setup path for both HubSpot and Mailchimp.
Typeform
DIY Typeform is a great idea — until it isn't. This is the honest framework for when hiring beats DIY, plus what a specialist actually does that you may not be doing.