Why mortgage website speed matters (and how to measure it)

Mortgage website speed matters because borrowers leave slow pages before they ever see your calculators, program pages or apply button. Google’s research on mobile pages found that the probability of a bounce increases 32% as page load time goes from one second to three seconds, and 113% from one second to seven seconds.

This guide explains what “fast” means in measurable terms, how to test your own site in five minutes, and the handful of decisions that make the biggest difference.

What does a slow site cost a loan officer?

Every extra second of waiting loses some visitors before they read a word. For a loan officer, those visitors are often the highest-intent ones: a referral from a realtor checking you out on a phone between showings, or a borrower who clicked an ad you paid for.

Source: Think with Google (2017) and Google research via AMP blog (2017-02-28)

Show the data table

Increase in bounce probability as mobile load time grows (from a 1-second baseline)

Item	Value
1 s → 3 s	+32%
1 s → 7 s	+113%

These figures are from 2017 research, but the principle has not changed: people are less patient on phones than on desktops, and most mortgage research now starts on a phone.

What do Core Web Vitals measure?

Core Web Vitals are Google’s measures of real-world page experience. There are three, each with a “good” threshold.

Source: web.dev Core Web Vitals thresholds, read 2026-10-19

Show the data table

LCP thresholds: where 'good' ends and 'poor' begins

Label	LCP (seconds)
Good up to	2.5s
Poor above	4s

How do you test your mortgage website’s speed?

Testing takes five minutes and needs no technical skill.

1. Open PageSpeed Insights and enter your home page address.
2. Choose Mobile (that is what most borrowers use and what Google evaluates first).
3. Read the Core Web Vitals assessment at the top. If it shows real-user field data, that is the most important result.
4. Note the performance score (lab data). 90–100 is rated good.
5. Repeat for a program page and your application page.
6. Look at the opportunities list: oversized images, unused JavaScript and render-blocking resources are the usual culprits.

What makes a mortgage site fast?

Four decisions account for most of the difference.

• Pre-built static pages on a CDN. Pages are generated in advance and served from a network close to the visitor, so there is no database or plugin work per request.
• Small, correctly sized images. Modern formats (WebP), multiple sizes for different screens, explicit width and height to avoid layout shift, and lazy loading below the fold.
• Fewer scripts, loaded later. Chat widgets, trackers and embeds are the heaviest items on most mortgage sites. Load them after the page, on interaction, or only after cookie consent.
• Sensible fonts. One or two font families, self-hosted, with a fallback that displays immediately.

Speed checklist for your next site review

• LCP within 2.5 seconds on mobile for the home and program pages.
• No layout jumps when images or fonts load.
• Hero image under about 200 KB in a modern format.
• Chat and tracking scripts load after content or after consent.
• No more fonts than you need.
• Forms and calculators respond instantly to taps.

What usually slows mortgage websites down?

When we audit slow mortgage sites, the same culprits appear again and again.

• Oversized hero images. A full-resolution photo straight from a camera or stock site can be several megabytes on its own.
• Chat and tracking widgets. Each third-party script adds network requests and processing, often on every page.
• Page builders and plugin stacks. Each plugin adds code whether or not the page uses it.
• Embedded calculators from other domains. Iframes from third parties load their own code and fonts.
• Web fonts loaded without care. Several families and weights, loaded before the text can display.
• Video backgrounds. Beautiful, heavy and rarely worth it on a phone.

Fixing these rarely requires a redesign. It requires deciding what each page genuinely needs and loading everything else later or not at all.

How do speed and conversion connect?

Speed affects conversion in two ways. First, people who leave before the page loads never see your offer. Second, a page that responds slowly to taps (a laggy calculator, a form that hesitates) feels untrustworthy, and trust is everything in a decision as large as a mortgage. A fast, stable page signals care before a borrower reads a word.

That is why we treat speed as part of the core promise rather than a technical extra: the fastest pages give your calculators, program pages and apply buttons the best chance to do their job.

A performance budget for a mortgage site

A performance budget is a set of limits you agree on before building, so speed does not erode over time. A sensible budget for a loan officer site:

• Main content visible within 2.5 seconds on a typical mobile connection.
• Hero image under about 200 KB in a modern format.
• No third-party script on the critical path of the first view.
• Chat, analytics and marketing tags loaded after content or after consent.
• One or two font families with a fast fallback.
• No layout shift when images, fonts or banners load.

When a new feature would break the budget, find a lighter way to achieve the same effect rather than quietly accepting a slower site.

What about mobile networks and older phones?

Many borrowers browse on mid-range phones over mobile data, often while doing something else. Test your site on a mid-range Android phone, not only on a new laptop with fast Wi-Fi. If pages feel slow there, they are slow for a large share of your audience. Lighthouse in PageSpeed Insights simulates a slower device and network for exactly this reason.

How often should you check?

Check speed at launch, after any significant change (a new widget, a new hero, a new plugin), and on a regular schedule such as monthly. Keep a simple record of scores and Core Web Vitals so you can spot slow drift before it becomes a problem.

Does speed matter for compliance and accessibility too?

Indirectly, yes. Pages that load slowly often shift around as images and banners arrive, which is disorienting for everyone and especially for people using magnification or screen readers. Cookie banners and chat widgets that pop up late can cover the content a visitor was reading. A fast, stable page is easier to use for all borrowers, and that supports both accessibility and the fair, consistent experience lenders aim for.

Speed also affects how reliably consent tools work. If a slow tag manager loads before the consent banner, tracking can fire before a visitor has chosen. Lightweight sites that load analytics only after consent avoid that problem by design.

What should you ask a provider about speed?

When you compare website providers, speed claims are easy to make and easy to check. Ask for:

1. A live client site on the same platform you can test yourself in PageSpeed Insights.
2. How images are processed and served (formats, sizes, lazy loading).
3. Which scripts load on every page, and which load only after consent or interaction.
4. Where pages are hosted and whether a CDN is included.
5. What happens to speed when you add a chat widget, a video or a booking calendar.
6. Whether they monitor real-user Core Web Vitals after launch.

A provider who builds fast sites will be happy to answer all six.

The bottom line

Speed is not a technical vanity metric; it is the difference between a borrower reading your FHA page and a borrower hitting back. Measure it on mobile, fix the big four, and keep third-party scripts on a short leash. If you would rather not think about it at all, our fast mortgage websites are built this way by default, and the schema guide covers the other half of technical quality.