If you have been trying to find a benchmark for mortgage application completion rate, you have probably noticed there is no widely published one. There is no widely published industry benchmark for this metric comparable to the standardized mortgage data available through HMDA. That is not an oversight. It is a reflection of how many variables shape the number, and why a single figure would tell you almost nothing useful about your own site.
This article explains what application completion rate actually measures, why the number varies so widely from one broker site to the next, what tends to cause borrowers to leave mid-process, and how to build a baseline that is meaningful for your own funnel. If you are trying to figure out whether your numbers are working, this is where to start.
There is no single mortgage application completion rate that can be called “good” across all brokers. Application length, traffic source, device type, form design, and how you define a “start” all affect the number. The useful benchmark is your own rate over time, measured consistently and compared against itself as you make changes.
What Application Completion Rate Actually Measures
Application completion rate is the percentage of people who start a mortgage application and finish it. The definition sounds straightforward, but the number changes depending on where you draw the starting line, and different definitions produce very different rates from the same underlying data.
Some brokers count everyone who lands on the application page as a starter. Others count only people who interact with at least one field. Others count people who open the first section of a multi-step form. Each definition produces a different denominator, which is one of the main reasons any published comparison between brokers is rarely meaningful.
Before you can measure your completion rate, you need to decide which version you are measuring. The next section explains the three most useful ways to frame it.
Three Related Metrics Worth Distinguishing
These three metrics are related but measure different things. Mixing them up produces numbers that are hard to act on.
Formula: Application starts ÷ application page visitors × 100
This measures how many people who arrive on your application page actually begin filling it in. A low start rate points to a problem with what the visitor encounters before they commit to starting: the appearance of the form, the amount of information requested upfront, a lack of context about what happens next, or a trust issue. The application itself may be fine. The problem is at the entry point.
Formula: Completed submissions ÷ application starts × 100
This measures how many people who began the application actually finished it. A low completion rate with a healthy start rate points to friction inside the form itself: field complexity, document requests, session timeouts, or a point where the borrower ran into something they were not prepared for. These are the most directly actionable numbers because they tell you where inside the process people are stopping.
Formula: Completed submissions ÷ application page visitors × 100
This is the combined funnel view. It tells you what percentage of everyone who arrived on your application page ended up with a completed submission in your system. It is useful as a headline number, but it combines the start-rate problem and the completion-rate problem into one figure, which makes it harder to diagnose where to act first.
Tracking all three separately gives you a much clearer picture than any single number. If your start rate is low, the problem is at the entry point. If your start rate is healthy but your completion rate is low, the problem is inside the form. If both are low, there are likely two separate issues worth addressing in sequence, starting with whichever is the larger drop-off.
Why There Is No Universal Benchmark
There is a tempting version of this article that provides a number: “a good completion rate is X%.” There is no single widely accepted benchmark that can meaningfully be applied across mortgage applications, and presenting one as if it could would mislead more than it would help.
The variables that make comparison between brokers difficult include:
- Application length and format. A short web inquiry form with five fields is a fundamentally different instrument from a full Uniform Residential Loan Application (URLA / Fannie Mae Form 1003) delivered through a point-of-sale platform such as Floify, Blend, or Encompass. Brokers sometimes discuss completion rate without specifying which type of form they mean, which makes any comparison unreliable. A multi-step URLA wizard where the borrower cannot see how many steps remain will behave differently from a short lead inquiry form on a landing page, and treating these as the same metric produces figures that cannot be acted on.
- Traffic source and visitor intent. A visitor who clicked from a real estate agent referral is in a different position than one who found your site through a blog post about mortgage rates. The same form will produce different numbers across these groups.
- Page placement and surrounding context. An application linked from a homepage CTA produces different numbers than one embedded on a loan-type page a visitor read before clicking.
- Device type. Mobile visitors and desktop visitors interact with forms differently, particularly when the form requires document uploads, date fields, or long text entry.
- Whether the visitor arrived with any prior context. A borrower who has already thought about their numbers approaches the application differently from one encountering these questions for the first time.
Because these variables compound, two brokers reporting very different completion rates may both be running their funnels well. The numbers are not comparable without knowing the underlying conditions. The more useful question is not “how do I compare to other brokers?” but “how does my rate compare to my own baseline last month, and what changed?”
Where Borrowers Tend to Drop Out
While no universal benchmark exists, there are common points in the application funnel where drop-off tends to concentrate. Understanding these can help you identify where to look first in your own data.
Broker sites often send visitors directly to a full application without an intermediate readiness step. A visitor who clicks Apply Now and immediately encounters a long form asking for employment history or SSN may leave before starting. Whether they were ready to apply is a separate question. The entry point itself can contribute to low start rates when it does not give the visitor a clear sense of what they are about to do or why completing the form is the right next step for them.
Requests for SSN, date of birth, and detailed employment information early in a form can contribute to abandonment among visitors who have not yet decided to fully commit to the process. Testing whether moving high-friction fields later in the sequence improves completion is one approach brokers use to address this. The effect will vary depending on your specific form and traffic.
Steps that require document uploads (pay stubs, bank statements, tax returns) can stop borrowers who do not have those files available at that moment. If the form does not communicate that the borrower can save progress and return later, or does not explain exactly which documents are needed, some visitors will exit and not come back. A follow-up prompt for incomplete applications is one way some brokers address this, though results will vary.
Form validation errors that are not clearly explained, session timeouts that clear previously entered data, or a missing confirmation screen can all prevent a completed application from being submitted. These are worth testing directly. Running through your own application on both desktop and mobile is the most reliable way to identify issues at this stage before they affect real applicants.
How Traffic Source Affects the Numbers
Visitors from different sources arrive with different levels of context and intent. Tracking your completion metrics separately by traffic source, if your analytics setup allows it, will often reveal that one channel is pulling your overall average down while another is performing well.
The table below is analytical rather than predictive. It describes what each source context suggests and what to examine, not what completion rate to expect.
| Traffic Source | Likely Visitor Context | What to Examine |
|---|---|---|
| Branded search | Visitor already knows the broker by name | Application start rate and completion rate. Drop-off here is worth diagnosing closely because the visitor searched specifically for the broker or brand. |
| Generic search | Visitor may still be comparing options | Landing page to application progression. The path from search result to application start matters as much as the application itself. |
| Organic informational content | Visitor may be earlier in their research process | Content to readiness-step to application progression. Visitors from informational content may not be ready to apply and may benefit from an intermediate step before the application. |
| Referral | Visitor may arrive with prior broker context from the referring party | Application friction and completion rate. If these visitors are dropping off, examine both the entry point and the form to determine where the largest loss occurs. |
| Social media | Intent can vary substantially depending on the content that brought them | Whether a pre-application or readiness step between social content and the application changes the completion rate for this segment. |
If you are tracking total completion rate across all sources in a single number, you are likely looking at an average that obscures both your best-performing channel and your worst. Separating even two or three sources gives you a more accurate starting point for improvement.
Mobile UX as a Separate Variable
If a large share of your first visits come from mobile, the gap between mobile browsing and completing an application is worth measuring directly. Many mortgage applications involve long field sequences, document upload steps, and detailed financial entry that can be more cumbersome on a phone than on a desktop.
If you can segment your completion data by device type, check whether mobile visitors start and complete the application at materially different rates than desktop visitors. That difference, if it exists, is a separate problem from your overall completion rate and may warrant a separate fix.
Desktop browser developer tools simulate screen sizes but do not replicate the keyboard behavior, tap targets, or session experience a borrower encounters on their phone. Running through your own application on a real mobile device periodically is the most reliable way to identify friction that does not show up in a desktop test.
How to Establish Your Own Baseline
Rather than looking for an industry figure to compare against, the more actionable approach is to establish your own baseline and measure improvement against it. Here is how to do that using standard analytics without any additional tooling.
Step 1: Decide which metric you are tracking
Choose one of the three metrics from the earlier section and be consistent. If you are tracking application completion rate (starts to submissions), you need a way to count starts separately from page views. If you are tracking page-to-completion rate, page views and form submissions are enough. Pick the one that your analytics can actually support and stick with it.
Step 2: Set a 60-day measurement window
One or two weeks of data may be too short to establish a reliable baseline, particularly for lower-volume broker sites. Mortgage applications are not quick decisions: some visitors arrive, leave, and return days later to complete the process. A 60-day window is a practical starting point that captures this behavior and reduces the effect of short-term variation from campaigns or seasonal traffic shifts, though the right window will depend on your traffic volume. If your application page receives fewer than 50 sessions per month, prioritize reaching a minimum of 100 to 150 total visits before drawing any conclusions. Below that threshold, a single week of unusual traffic can move the rate enough to look like a meaningful change when it is just noise.
Step 3: Record the number and note the conditions
At the end of the window, write down your rate alongside the conditions: which traffic sources were active, whether you ran any paid campaigns, roughly what the volume was. Those notes are as important as the number itself when you want to understand a change later.
Step 4: Change one thing at a time
A common error is making several changes at once and not knowing which one moved the number. Change one element, measure for 30 days, then evaluate before making the next change. Small changes at a high drop-off point will produce more improvement than optimizing a step lower in the funnel where fewer people are leaving.
A 3 percentage point improvement in page-to-completion rate on a site receiving 200 application page visits per month is 6 additional completed applications per month. Over a year, that is 72 applications that would otherwise have been lost at some point in the funnel. On low-traffic sites the percentage looks modest. The absolute number of recovered applications is what matters to the pipeline.
The Role of a Pre-Application Step
One structural reason completion rates can be low is that broker sites often send visitors directly to an application, regardless of where that visitor is in the process. A first-time visitor who arrived from a blog post and a referred client who just left a real estate agent meeting land on the same Apply Now button. The form is identical. The context is completely different.
A pre-application step addresses this by giving visitors a way to understand their own situation before deciding whether to continue to the full application. Rather than encountering a long form cold, the visitor first works through their estimated payment, debt-to-income ratio, and other financial factors in an educational context. A visitor who chooses to continue after seeing those numbers has worked through their own financial picture before reaching the application.
The effect on completion rate is not guaranteed and will depend on your specific traffic and form setup. What the pre-application step changes is the composition of who reaches your application, not the application itself. The leaky funnel problem often starts before the application page, at the point where visitors who were not yet ready enter a path they were unlikely to complete regardless of how well the form was designed.
MDE Pro is one approach to this. It provides a borrower readiness assessment in about 20 seconds, shows the visitor their estimated payment, DTI, and readiness indicators in an educational format, and gives visitors a clear next step toward the broker’s existing application. It is not a pre-qualification or pre-approval tool. It is an educational readiness step that sits between the broker’s site content and their application, so that the visitors who continue to the application have had the chance to understand their own numbers first.
See How MDE Pro Works as a Pre-Application Step
MDE Pro provides a borrower readiness assessment in about 20 seconds and gives visitors a clear next step toward your existing application. Your dashboard tracks every stage of the funnel.
View the Live DemoQuestions about your broker website conversion funnel? Email services@ournethelps.com
