2.4×
organic enquiries
Castellan Realty
480 listings, eight photos each, and a search that has to feel instant on a phone in a car park.
- MLS feed
- Instant search
- Image pipeline
You're competing with portals that have engineering teams. You won't beat them on inventory, but you can beat them on speed, on local knowledge, and on being the agency people already trust in your area.
0.0s
Median listing page LCP
Mobile, full photo gallery.
8–12
Weeks, typical build
With feed integration.
0
Minute feed sync
Configurable per source.
Property search is image-heavy, filter-heavy, and impatient. Twelve listings with eight photos each is a lot of bytes, and a gallery that stutters on a phone loses the browse session that would have produced an enquiry.
So the technical work is mostly about weight and responsiveness: images served in modern formats at the right size, map and list views that don't reload the page, and search state that survives a back button. Then the feed — IDX, MLS, or your own CRM — synced reliably, with sold and withdrawn listings handled properly so the URL doesn't just 404.
The marketing side is local search. Area and neighbourhood pages with real substance — schools, transport, price trends, your own recent sales — earn the searches portals compete for weakly, because they can't write about a neighbourhood the way someone who works it can.
Every sector has its own set. Naming them up front is how a brief stops being a wish list.
Property photography is the point and also the payload. Unoptimised galleries make listing pages the slowest on the site, exactly where you need people to linger.
IDX and MLS feeds vary wildly in quality and update cadence. Mapping fields, handling missing data, and dealing with duplicates is most of the work.
Price, beds, type, and area filters returning results without a full page load. Anything slower and people go back to the portal.
Delisted properties often become 404s, discarding accumulated authority and links. Sold archives are also genuine local-search assets.
Thirty templated neighbourhood pages with the name swapped get discounted. Ten substantive ones with real local knowledge outrank them comfortably.
AVIF and WebP at multiple sizes, lazy loading below the fold, the hero preloaded, and blur placeholders so the layout never jumps.
Scheduled ingestion with field mapping, validation, and a reconciliation report. Missing or malformed records surface as alerts, not as broken listings.
Client-side filtering over an indexed dataset, with map and list views sharing state and URLs that are shareable and bookmarkable.
Sold listings kept with clear status and links to similar available properties, or redirected to the area page. Nothing valuable becomes a 404.
Your recent sales, price trends, schools, and transport, plus LocalBusiness and RealEstateListing schema. Written, not generated.
Not every service suits every sector. These are the ones that earn their keep in yours.
With the numbers, the timeline, and the parts that went sideways.
Our agents had started sending buyers to a portal because our own listings took nine seconds to load. That's a humiliating sentence to say out loud. It's a second and a half now, and people actually browse — we went from two pages a visit to nearly seven.
The map pack is where local demand lives. Here's how it's ranked, what to fix first, and the review process that quietly does most of the work.
Read itLCP, CLS, and INP explained by cause rather than definition — and the specific fixes that moved each one on real sites, in the order we try them.
Read itMost sites that fail to convert aren't ugly. They're unclear. Here's the sequence we follow, and the specific things we measure at each step.
Read itUsually yes. We've worked with RETS, RESO Web API, and a fair number of proprietary XML feeds. The variable is data quality — some feeds are missing fields or send duplicates, and handling that cleanly is most of the integration work. We'll review your feed during scoping and tell you what to expect.
Tell us the goal and the constraints. We'll tell you what it takes, what it costs, and what we'd do first.
Rather write first?hello@quesiono.com— we reply within one business day.