We measured real estate website speed across twelve agent sites that an industry publication showcases as some of the best examples of the craft. The median mobile performance score was 30 out of 100. Not one of the twelve passed a single Core Web Vitals threshold.
These were not randomly chosen bad sites. They were the ones held up as examples to follow. That is what makes the result worth publishing.
What we found about real estate website speed
| Measure | Median | Best | Worst | Google’s threshold | Passed |
|---|---|---|---|---|---|
| Performance score | 30 / 100 | 44 | 5 | 90+ is good | 0 of 12 |
| Largest Contentful Paint | 12.1 s | 7.0 s | 34.4 s | 2.5 s | 0 of 12 |
| Total Blocking Time | 2.6 s | 0.9 s | 9.3 s | 200 ms | 0 of 12 |
| Cumulative Layout Shift | 0.007 | 0.000 | 0.561 | 0.1 | 11 of 12 |
| Page weight | 3.8 MB | 0.9 MB | 19.8 MB | — | — |
Three numbers deserve attention. The fastest site in the sample took 7 seconds to paint its main content — nearly three times Google’s threshold. The slowest took 34 seconds. And the heaviest page pulled 19.8 MB, which on a typical mobile plan is a real cost to the visitor.
The one bright spot is layout stability: eleven of twelve passed Cumulative Layout Shift comfortably. Modern themes have largely fixed the jumping-content problem. They have not fixed weight.
How we tested real estate website speed
Method matters more than the headline, so here it is in full.
- Sample: fourteen agent and brokerage websites named in a 2026 industry round-up of the best real estate website examples. Twelve returned complete results; two failed to load during testing and were excluded rather than scored as zero.
- Tool: Google Lighthouse 12, the same engine behind PageSpeed Insights.
- Configuration: mobile form factor, mobile screen emulation, simulated network and CPU throttling — Lighthouse’s default mobile profile.
- Scope: the home page only, one run per site, September 2026.
- Metrics: performance score, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift, total transferred bytes.
Limitations, stated plainly. Twelve sites is a small sample. Lighthouse produces lab data, not real-user field data, and a single run carries variance. Home pages are usually heavier than interior pages. And the sample came from one publication’s list, so it reflects sites chosen for visual design rather than a random cross-section.
What the sample cannot be accused of is being unrepresentatively bad. If anything it is biased toward sites with money and attention spent on them.
Disclosure: the site you are reading scores 76 on the same test. I built it, so treat that as context rather than proof.
Why is real estate website speed so consistently poor?
The same five causes turned up again and again, and none is mysterious.
- Full-screen hero video or a giant image. The single biggest contributor to a slow Largest Contentful Paint. A 4 MB hero is common and is the first thing a visitor waits for.
- Unoptimised photography. Property images uploaded at camera resolution, served to a phone at full size, in formats older than WebP.
- Framed IDX search. An iframe loads as a second document inside your page, with its own scripts and styles — a well-known drag on mobile performance.
- Plugin and script stacking. Chat widget, analytics, heatmap, review carousel, pop-up builder, animation library. Each seems small; together they produce the multi-second blocking times in this sample.
- Sliders and page builders. Convenient to edit, heavy to deliver, and usually loading assets for features the page never uses.
Notice that four of the five are decisions rather than technical constraints. That is encouraging: they can be reversed without rebuilding anything.
Which real estate website speed metric fails hardest?
Total Blocking Time, by a distance. The median was 2.6 seconds against a 200 millisecond threshold — thirteen times over. That metric measures how long the browser is too busy running JavaScript to respond to a tap.
In practice that is the site feeling frozen. A visitor taps “Contact” and nothing happens for a beat, so they tap again, and the page finally responds by doing something unexpected. Weight slows a page down; blocking time makes it feel broken.
Largest Contentful Paint was not far behind, with a median of 12.1 seconds. On a phone that is long enough for a meaningful share of visitors to leave before seeing anything at all.
Does poor real estate website speed actually cost you clients?
Honestly, less directly than speed advocates usually claim — and more than the results above would suggest is safe.
Page experience is a genuine but modest ranking signal; Google has been clear that great content outranks fast-but-thin content. So a slow site with strong local content can still rank. Speed is a tiebreaker, not a trump card.
Where it bites is conversion, and specifically the moment described in why most clients arrive already referred. Someone gets your name, looks you up on their phone in a car park, and forms a judgement in seconds. A twelve-second wait is not an SEO problem at that moment. It is a credibility problem.
How to test your own real estate website speed in five minutes
- Open PageSpeed Insights and enter your home page address.
- Read the Mobile tab, not Desktop. Desktop flatters every site and is not where your visitors are.
- Write down four numbers: performance score, LCP, TBT and CLS.
- Compare against this sample — median 30, LCP 12.1 s, TBT 2.6 s.
- Scroll to “Diagnostics” and look at the largest items. That list is your to-do list.
If you land above 50 on mobile you are already ahead of every site in this sample.
What should you fix first?
| Fix | Effort | Typical gain |
|---|---|---|
| Compress and resize images, serve WebP | Low | Large — often the single biggest win |
| Remove the hero video, or replace with a still | Low | Large on LCP |
| Delete unused plugins and scripts | Low | Large on blocking time |
| Defer non-essential JavaScript | Medium | Large on blocking time |
| Enable page caching | Low | Moderate, and helps everywhere |
| Move framed IDX to on-domain search | High | Moderate, plus SEO benefit |
| Rebuild on a lighter platform | High | Large, but do the cheap fixes first |
The top three cost nothing but an afternoon and would have moved most sites in this sample from the twenties into the fifties.
What Google actually requires
Real estate website speed is not judged on a single number. Google measures three specific things, and a page has to pass all three to count as good. These are the published thresholds.
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint | When the main content appears | Under 2.5s | Over 4.0s |
| Interaction to Next Paint | How fast the page responds to a tap | Under 200ms | Over 500ms |
| Cumulative Layout Shift | How much the page jumps about | Under 0.1 | Over 0.25 |
Thresholds are published by Google in its Core Web Vitals documentation. Layout shift is the one agents underestimate: a page that loads quickly but jumps as adverts and images arrive still fails, and it is the most irritating kind of poor real estate website speed for an actual visitor.
Why real estate website speed is worse than other industries
Five structural reasons, and none of them is that agents are careless. This category has a genuinely harder job than a typical small business site.
- Photographs are the product. Twenty high-resolution images per listing is the job, not an indulgence.
- IDX search is heavy. Live queries against a listings database cost far more than serving a static page.
- Map widgets are enormous. An embedded map can outweigh everything else on the page combined.
- Templates ship with everything enabled. Sliders, video backgrounds, chat widgets and analytics tags all load whether used or not.
- Nobody measures it. Real estate website speed is invisible on the developer’s fast laptop and painful on a phone on cellular data.
The last point explains most of the rest. Sites are built, approved and forgotten on desktop connections, so poor real estate website speed on mobile is never noticed by the people responsible for it.
The fixes, ranked by effort
Most agent sites gain more from the first three of these than from a redesign. Work down the list and re-test after each change.
- Compress and convert images to WebP. Usually the single biggest win available, and often a plugin setting rather than a project.
- Set width and height on every image. Removes most layout shift for almost no effort.
- Lazy-load anything below the fold, including maps and video embeds.
- Remove the hero slider. Sliders are heavy, nobody clicks past the first panel, and deleting one reliably improves real estate website speed.
- Audit third-party scripts. Chat widgets, heat-mapping, multiple analytics tags. Remove anything nobody reads.
- Enable caching and a CDN. Standard on decent hosting and often just a toggle.
- Only then consider better hosting or a rebuild.
Steps one to three are free and typically move a mobile score by twenty to thirty points. Agents reliably jump to step seven first, which is the most expensive way to improve real estate website speed and rarely the most effective.
What if the IDX is the slow part?
Common, and largely outside your control, which is worth knowing before you spend money trying to fix it. If the listings search is the bottleneck, these are your realistic options.
- Keep IDX off the home page. Put the search on its own page so your most-linked page is not carrying the weight.
- Load the search widget on interaction, not on page load.
- Ask your vendor for their own PageSpeed numbers. A vendor who has never measured real estate website speed on their own product is telling you something.
- Compare vendors on speed before signing. Test three of their live client sites on mobile.
Judge your own pages separately from the listings search. A fast set of neighbourhood pages and a slow IDX section is a normal and acceptable outcome, and far better than dragging the whole site down to the speed of the heaviest component.
How much does real estate website speed actually change rankings?
Less than SEO marketing implies, and more than nothing. It is a tie-breaker rather than a primary factor, which has two honest implications.
First, a fast page with nothing useful on it will not outrank a slow page that answers the question. Content decides the shortlist. Second, among pages of similar quality — which is exactly the situation in local property search — real estate website speed is one of the things that separates them.
The stronger argument is not about rankings at all. A visitor on a phone outside a house they are interested in will not wait twelve seconds, and no ranking benefit compensates for the ones who leave.
What good real estate website speed looks like in practice
Scores are abstract. These are the targets worth aiming at, and what each one feels like to someone standing outside a house on their phone.
| Mobile score | What it feels like | Verdict |
|---|---|---|
| 0–29 | Blank screen long enough to leave | Losing visitors daily |
| 30–49 | Noticeably slow, jumpy layout | Typical agent site — fixable |
| 50–69 | Acceptable, occasional stutter | Fine for a site with IDX |
| 70–89 | Fast | Better than most competitors |
| 90+ | Instant | Realistic only without IDX |
Aim for the middle of that table rather than the top. Real estate website speed in the 50 to 70 band on a page carrying live listings is a genuinely good result, and pushing beyond it usually means removing things visitors want.
Your brochure pages are a different matter. A neighbourhood page is text and a few photographs, so there is no excuse for it scoring below 70, and those are the pages competing in search.
The one-hour real estate website speed audit
You can do this yourself with free tools and no technical knowledge. Book an hour, work through it in order, and write the numbers down so you can compare next quarter.
- Run PageSpeed Insights on three pages — home, best neighbourhood page, one listing. Record the mobile score and the three Core Web Vitals for each.
- Note the largest items in the report. It names the specific images and scripts costing you the most, which removes all the guesswork.
- Open your own site on your phone on cellular data, not office wi-fi. This is the only test of real estate website speed that reflects how people actually arrive.
- Count the seconds until you can read something. Over four and you have a problem worth money to fix.
- Watch for the page jumping as it finishes loading. That is layout shift, and it is usually images without dimensions.
- Test two competitors the same way. Context matters more than the absolute number, and in most markets the bar is low.
Step six is the one that turns this from an anxiety into a strategy. If your competitors sit in the twenties and you reach sixty, your real estate website speed has become a genuine advantage in a market where almost nobody is paying attention to it.
Take the list of largest items from step two to whoever maintains your site. A specific request to compress four named images gets actioned; a vague complaint that real estate website speed is poor usually does not.
A closing thought on why this is worth your attention at all. Almost every other lever in online marketing requires you to beat someone who is trying just as hard as you are. Real estate website speed does not. The median agent site in our sample scored 30 on mobile, which means the bar in this category is not high and almost nobody is competing for it. An afternoon compressing images and removing a slider puts you ahead of most of your market on a measure Google has publicly confirmed it uses, and that visitors feel immediately whether or not they could name it. Few things in this business offer that ratio of effort to advantage.
Who to ask, and what to ask for
If you do not maintain the site yourself, the way you raise real estate website speed determines whether anything happens. A general complaint gets a general answer; a specific request gets actioned.
- Send the PageSpeed report link, not a description of it. The report names the exact files costing you the most.
- Ask for three specific things: compress and convert the images it names, add width and height attributes, lazy-load anything below the fold.
- Give a target. “I would like mobile above 50” is measurable; “make it faster” is not.
- Ask what it will cost before agreeing. Most real estate website speed work on a small site is an hour or two, not a project.
If the answer is that nothing can be done without a full rebuild, get a second opinion. That is occasionally true and much more often a quotation for work you did not ask for, and real estate website speed on a brochure site rarely requires starting again.
Frequently asked questions
Is a score of 30 actually bad?
It is poor by Google’s banding — 0 to 49 is red, 50 to 89 amber, 90 plus green. But context matters: a score of 30 with a 7 second paint is very different from 30 with a 30 second paint. Look at the underlying metrics rather than the headline number.
Why does my site score well on desktop and badly on mobile?
Because the mobile test simulates a mid-range phone on a throttled connection, while desktop assumes a fast machine on broadband. Mobile is the honest measurement for real estate, where buyers browse on phones. Always read the mobile tab.
Will fixing speed improve my rankings?
Modestly, and only once content and relevance are in place. Page experience is a real signal but a light one. The stronger argument for fixing speed is that visitors who leave before the page renders cannot become clients, regardless of where you rank.
Can a site with IDX ever be fast?
Yes, if the search is not framed and the rest of the page is disciplined. The lightest site in this sample was under 1 MB. IDX adds weight to the search pages specifically; it does not require your home page to be 12 MB.
How often should I test real estate website speed?
Quarterly, and after any change to the site. Sites get slower gradually as pages, images and scripts accumulate, so a calendar reminder catches drift that nobody would otherwise notice until it was severe.
Which pages should I test?
Three: your home page, your best neighbourhood page and one listing page. They have different weights and different problems, and an average across all three describes your real estate website speed far better than the home page alone.
Is a perfect score worth chasing?
No. Getting from 30 to 70 is worth real effort; getting from 85 to 100 is a hobby. Pass the three Core Web Vitals thresholds and spend the remaining time writing content.
The bottom line
Twelve showcased agent websites, median mobile score of 30, and not one passing a Core Web Vitals threshold. Real estate website speed is not a solved problem at any price point — several of these sites plainly cost thousands.
The encouraging part is how ordinary the causes are. Oversized images, a hero video, and too many scripts explain most of it, and all three are fixable without a rebuild. Measure your own site before you believe anyone — including me.
Asraful Islam
Real estate website developer and founder of Reaplex. 200+ real estate websites built, rated 5.0 from 180+ reviews on Fiverr and Upwork.
More about me
