Zuko Blog

Should you use “Confirm Password” on your forms and websites?: A Case Study

We achieved a 56.3% increase in form conversions by removing “Confirm Password” while not negatively affecting the password reset rate.

Should you force a user to confirm a password when they complete your form? Those in the “YES” camp argue that it cuts out unnecessary calls to customer support when the user has mistyped and subsequently mis-entered their password. From the “NO” side, the contention is the requirement introduces unnecessary friction into the form so reduces conversion rates. The “NO” gang further argue that users generally copy and paste their password to confirm anyway so asking them to confirm will make no difference whatsoever to the volume of incorrectly entered passwords. Besides, there is always a “Forgotten Password” option as a last resort.

There are strong opinions on this topic so we thought we would help inform the debate by resurfacing one of our previous pieces of research on the topic. It comes from the days when we were known as Formisimo rather than Zuko (hence the different branding) and is based on our sign-up form.

At first glance, the Formisimo registration form looked pretty straightforward:

The Formisimo registration form before the changes
The registration form before the changes


We did notice, however, that over a quarter of abandonments were on the “Confirm Password” field. While this wasn’t the worst field for abandonments (many abandoned after only focusing on the first “Name” field), it did ring alarm bells - if users had gotten that far, why not complete the form?

So, to live our test, learn and refine, mantra we decided to trial some changes. We had only used a “Confirm Password” feature out of a nebulous sense that it was best practice to do so. We had no firm data-backed hypothesis to include it in the first place.

For full disclosure, we did make a few other changes at the same time:

The new form

Now, we know the professional A/B testers among you will be screaming at us that we should have only made one change at a time to be certain of the conclusions. You are right, but that is the way it was done at the time and we can’t go back and change it now.

The results of the test were:

This test was, overall, clearly a success for us. Removing the requirement to confirm the password reduced unnecessary friction in the form and had no negative effect on overall experience regarding remembering passwords.

Needless to say, we have never gone back to confirming passwords in our forms and we likely never will.

For more form advice, tips and best practice check out our Big Guide to Form Optimization.


Zuko's Big Guide to Form Optimization and Analytics Cover Shot

Looking to improve your web form conversion?

Check out Zuko's Big Guide to Form Optimization & Analytics

More from our blog:

Are discount coupon codes a good idea for your eCommerce checkout?
Best practice advice on the use of discount code fields in your checkout or form
Should you use “Confirm Password” on your forms and websites?: A Case Study
We removed the requirement to confirm password on our registration form and increased conversion rates by 56%
Should you use Captcha on your Web Forms?
We look at the effects of using Captcha on your forms and the alternative systems you can use
Form Analytics Glossary
An overview of form analytics terminology in a handy glossary

Zuko is the most powerful form analytics platform available on the market. Find out how to improve yor form and checkout conversion by taking a product tour.

PRODUCT TOUR
zuko full colour logo
Formisimo Ltd, Colony, 5 Piccadilly Place, Manchester, M1 3BR
VAT Number: GB181252425
Registered in England as company number 08859680
New Business: sales@zuko.io
Support: support@zuko.io
This website stores data such as cookies to enable important site functionality including analytics, targeting, and personalization. By remaining on this web site you indicate your consent.