Prostor
← All articles
14 August 2026

Website speed and buyer drop-off: the tax on heavy property sites

Property websites carry the heaviest media on the web: renders, tours, maps. Where the seconds actually go, what they cost in lost buyers, and the fixes that do not require deleting the beauty.

Property sites carry some of the heaviest media on the web. Renders at print resolution, drone video in the hero, a 3D tour, two map widgets and an animation library, all competing for the same first seconds. Each element earned its place in a meeting. Together they are a tax on every visitor.

The tax is measurable. Google's own research found that as mobile load time goes from one second to three, the probability of a bounce grows by about a third, and more than half of mobile visits are abandoned past the three second mark. Nothing about property buyers makes them more patient; they arrive from an ad, on a phone, with four competitor tabs already open.

Where the seconds go

The same offenders appear in almost every audit we do. Hero images exported straight from the render studio at 8000 pixels wide. Autoplay video that starts downloading before the headline paints. Map and tour widgets that load their whole engines on page open, whether the buyer scrolls there or not. Font families in six weights when the design uses two. And builder-generated markup where half the page is wrapper divs, which is one of the quieter reasons we build money pages on code.

None of these are exotic. That is the good news: boring problems have boring fixes.

Fixes that keep the beauty

Images do most of the damage and give back the most. Serving renders in modern formats at the displayed size, with lazy loading below the first screen, routinely cuts page weight several times over with zero visible loss. The hero stays cinematic; it just stops weighing eight megabytes.

Everything interactive loads on intent. Video plays when tapped. The tour and the map wake up when scrolled into view. The unit selector renders its first state on the server so the buyer sees apartments, not a spinner. Progress photos from the last three years live in an archive, not on the main feed.

Then the layer under the media: server-rendered pages, static where nothing changes per visitor, media on a CDN. This is the part buyers never see and always feel.

Speed is also a trust signal

An off-plan buyer is deciding whether a developer keeps promises. The site is the first promise: this is how we do things. A page that stutters on a phone whispers the wrong answer before the brochure says a word. Fast sites read as competent, and competence is exactly what off-plan trust is built from.

Speed also feeds visibility. Core Web Vitals sit inside Google's ranking systems, and slow pages get crawled less eagerly, by search engines and AI assistants alike. The technical work pays twice: once in conversion, once in traffic.

What we do on projects

Every site we ship gets the same regimen: server rendering, images optimised at build time, interactive blocks that load on intent, and a speed check on real phones before launch, not after complaints. If you want to know where your project site stands, send us the link and we will reply with the numbers and the three heaviest fixes, written down, free.

Questions

How fast should a property website load?

The useful target is under two and a half seconds to meaningful content on a mid-range phone over mobile network, not on the designer's laptop. Buyers browse from phones, often from ads, and every extra second sheds a slice of them before the page even appears.

Why are developer websites so heavy?

Renders exported at print resolution, videos that autoplay, map widgets, tour embeds and animation libraries, all on one page. Each item is justified alone; together they add up to tens of megabytes that mobile visitors pay for.

Do we have to remove renders and tours to be fast?

No. Modern formats and lazy loading keep the beauty: images served in WebP or AVIF at the size actually displayed, video loaded on click, tours and maps loaded when scrolled into view. The page starts fast and the media arrives as needed.

How do we check our real speed?

PageSpeed Insights on the key money pages (home, project page, unit selection), looking at the mobile score and Core Web Vitals, plus one honest test on a cheap phone over mobile data. If the selector page takes five seconds, that is where the leads leak.

First page of the Prostor project brief template
Resource

Project brief template

The same document we send clients before we start. Seven sections, about twenty minutes to fill in, and it removes half the questions from the first call.

What is inside
  • Company and project
  • The task and what success looks like
  • Who buys
  • What the site needs
  • Timeline, budget, constraints
  • Taste and examples
  • Materials and sign-off
PDF · 3 pages · fill it in by hand or in any editor

Tell us the task in four answers

Answer with the buttons or in your own words — that is enough for us to come to the call with thoughts instead of generic questions.

Question 1 of 4

What do you need?

Ruslan Kochubarov
Ruslan Kochubarov
Founder, art director

Tell us about the task

Book a 15-minute call or leave a request — we reply within one business day and send a brief and relevant examples.

Book a call
  1. 1We read the request and reply within one business day
  2. 2We take 15 minutes on a call to unpack the task
  3. 3We send a scoped estimate with timings