themortgagefirm.com website review

17 files are served with short cache lifetimes, so returning visitors download them again (688 KiB).

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

9 images could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 63 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

About 66 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

7 third-party services load with your homepage (consently.net, Cloudflare CDN and JSDelivr CDN and others), adding 1.1 MB and 122 ms of main-thread time.

mortgagebigger.io costs a phone 1 ms of main-thread work and 681 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

11 KiB could be saved by minifying CSS.

11 KiB could be saved by minifying JavaScript.

Desktop scores 92 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies to ensure the basic…”.

The first text or image appears after 3.7 s on a phone. Good is under 1.8 s.

The page becomes fully interactive after 7.9 s. Good is under 3.8 s.

Visually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.

Real visitors wait 845 ms for your server to start answering (75th percentile). Good is under 800 ms.

17 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image is downloaded at several times the size a phone draws it, for example Website Banner Images March 2026-04-8BvY2J.jpg at 1,378 px wide, shown at 303 px. Resized copies would save about 95 KiB.

3 images (247 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

Your title is only 28 characters: “Welcome to The Mortgage Firm”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 67 pages on themortgagefirm.com and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://themortgagefirm.com/find-loan-officer, https://themortgagefirm.com/about, https://themortgagefirm.com/contact, https://themortgagefirm.com/licensing, https://themortgagefirm.com/support and https://themortgagefirm.com/terms-and-conditions and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://unpkg.com/[email protected]/dist/aos.css' violates the following Content Security Policy directive: "con…”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 524 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.