Mortgage Website Speed: Core Web Vitals for Loan Officers

You paid for the click. The borrower tapped your ad, the screen went white, a spinner turned, and somewhere around the third second they tapped back. That’s the quiet cost of a slow mortgage website: no complaint, no form, just a bounce you’ll never see in your CRM.

This post explains why speed matters for mortgage leads, what Core Web Vitals actually measure, the thresholds to aim for, and the fixes that make loan officer sites and funnels fast.

Does page speed affect mortgage leads?

Yes — slow pages lose visitors before they ever see your offer. Google’s 2017 research on mobile page speed reported that as page load time goes from one second to three, the probability of a bounce increases by 32%. From one second to five, it increases by 90%; to six seconds, 106%; to ten, 123%.

Increase in the probability of a bounce compared with a 1-second load, as reported by Google. Source: Think with Google, 'Find out how you stack up to new industry benchmarks for mobile page speed' (2017)

Show the data as a table

Page load time	Increase in bounce probability
3 s	32%
5 s	90%
6 s	106%
10 s	123%

That research is cross-industry and a few years old, and phones and networks have improved — but so have expectations. The direction is the point: every extra second costs a share of the people who were interested enough to tap.

For mortgage funnels the cost is double:

1. Organic visitors who leave before reading your program page.
2. Paid visitors whose clicks you already paid for.

What are Core Web Vitals?

Three measurements of how a page feels to real visitors: how fast the main content appears, how quickly the page responds, and whether things jump around.

Core Web Vitals thresholds (75th percentile of page loads)

Metric	What it measures	Good	Needs improvement	Poor
Largest Contentful Paint (LCP)	Loading — when the main content shows	≤ 2.5 s	2.5–4.0 s	> 4.0 s
Interaction to Next Paint (INP)	Responsiveness to taps and clicks	≤ 200 ms	200–500 ms	> 500 ms
Cumulative Layout Shift (CLS)	Visual stability — content jumping	≤ 0.1	0.1–0.25	> 0.25

Google measures these on real users (field data, shown in Search Console’s Core Web Vitals report) and you can approximate them in a lab test (PageSpeed Insights). Field data wins when they disagree, because it’s your actual visitors on their actual phones.

What makes mortgage websites slow?

Weight and order: too much stuff, loaded too early. The usual culprits on loan officer sites are well known:

• Images: full-size photos (often several megabytes) scaled down by the browser.
• Theme and builder scripts: page builders ship code for features the page doesn’t use.
• Third-party scripts: chat widgets, trackers, review badges and embedded rate tools loading before the page.
• Fonts: several families and weights, loaded without a fallback.
• Layout shift: images without dimensions, banners injected after load.

Illustrative example of page weight by type on a page-builder landing page. Run your own page through PageSpeed Insights to see yours. Source: Illustrative example created by Get Mortgage Funnels

Show the data as a table

Resource type	Share of page weight (example)
Images	46%
Third-party scripts	22%
Theme / builder scripts	18%
Fonts	9%
HTML & CSS	5%

Hosting matters less than people think. A light page is fast on modest hosting; a heavy page is slow on great hosting.

How do I make a mortgage site fast?

Serve static pages, right-size everything, and load extras later. The fixes in order of impact:

1. Static pages on an edge network. Pre-built HTML served close to the visitor beats a database-driven page assembled on every request.
2. Right-sized, modern images. WebP or AVIF, resized for the slot, with explicit width and height (prevents layout shift), lazy-loaded below the fold, and the hero image loaded eagerly.
3. Scripts after the page. Chat, reviews widgets and calculators initialise after the page is interactive — or when the visitor opens them.
4. Analytics after consent. Tags that wait for cookie consent don’t block anyone who hasn’t consented — a privacy win and a speed win.
5. Fewer fonts. One or two families, self-hosted, with font-display: swap.
6. Reserve space. Every image, embed and banner gets its dimensions up front so nothing jumps.

Most of the speed gap comes from what loads and when, not from the server. Static pages with disciplined scripts are fast by default.

Does speed affect ad costs?

It can. Google Ads’ Quality Score includes landing page experience, alongside expected click-through rate and ad relevance, and a better Quality Score can mean lower costs per click. Speed isn’t the only part of landing page experience — relevance and clarity matter — but a slow page undermines the rest.

On Meta, a fast landing page simply means more of the people you paid to reach actually see your quiz.

What should a loan officer test first?

Three pages on mobile: your homepage, your most-visited program page, and the landing page your ads point to.

1. Run each through PageSpeed Insights on mobile. Note LCP, INP (or Total Blocking Time in the lab) and CLS.
2. Open the Core Web Vitals report in Google Search Console for real-user data.
3. Look at the largest items in the “opportunities” list — usually images and scripts.
4. Fix the biggest one and retest.

Can a fast site still look good?

Yes. Fast doesn’t mean plain. Motion can be built with transforms and opacity (cheap for the browser), heavy effects can load lazily, and everything can switch off for visitors who prefer reduced motion. The rule is that nothing decorative blocks the content or the call to action.

Speed checklist for mortgage sites and funnels

• Static pages served from an edge network.
• Hero image eager; all other images lazy, right-sized, WebP/AVIF, with dimensions.
• No render-blocking third-party scripts; chat and widgets load later.
• Analytics and ad tags load only after consent.
• One or two self-hosted fonts with swap.
• No layout shift from banners or embeds.
• LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 in field data.
• Build to score 90+ on mobile PageSpeed — then watch real-user data.

Speed is the part of your funnel nobody notices when it’s right. That’s exactly why it’s worth getting right.

Statistics as cited. “Built to score 90+” is our build target; we report measured scores per site after launch.