Dana’s agency lists a hundred properties, each with twenty photos. Buyers binge them at night, flicking listing to listing: and every slow gallery is a listing effectively removed from the market.
The IDX plugin, the map widget, the mortgage calculator, each added seconds. New listings went up hourly, so nobody dared cache anything; someone once saw a sold property still showing, and caching got switched off for a year.
The answer was rules, not surrender: listing pages cached and auto-purged on update, galleries converted to WebP and lazy-loaded, the map delayed until a buyer touches it. A hundred listings, all instant, none stale.
02
When speed decides the outcome
Three beats. Everything xSpeed Cache does on this page is aimed at the gap between the second and the third.
1
The shortlist
Six tabs, six agents, one afternoon of comparing.
2
The gallery
Forty photos per listing, and they want to see all of them.
3
The enquiry
The tab that loaded first is the tab they filled the form on.
03
What a site like this actually needs
Not a redesign. Three properties the site has to have before anything else matters.
01
Galleries that keep up with flicking
Twenty photos per listing, forty listings per session, image weight decides the browsing experience.
02
Never a stale listing
A sold property showing as available is worse than slow. Cache must purge the moment a listing changes.
03
Third-party widgets on a leash
Maps, IDX feeds, and calculators are needed, after the listing paints, not before.
04
The xSpeed features doing the work
Each one is a real setting with a real guide. Nothing here is a marketing abstraction.
Connect your AI with xSpeed Hub MCP (or to this one site directly), then paste this into Claude or ChatGPT. It is written for this business, not a generic template.
COPY & PASTE
Using xSpeed, optimize my real estate site: cache all listing pages with automatic purge on update, convert galleries to WebP with lazy loading, and delay the map and mortgage-calculator scripts until interaction. Confirm that editing a listing refreshes its cache, then benchmark a listing page before and after.
What happens: Every listing serves from cache, updates the second it changes, and the gallery keeps pace with a buyer’s thumb.
06
Questions from Real estate agencies
Yes. This is exactly what auto-purge and per-post rules are for. Each listing’s cache rebuilds the moment it is edited, so buyers see current status at cached speed. A sold listing never lingers.
Dynamic and third-party content can be excluded or delayed per URL, so the IDX-driven parts stay live while everything around them serves from cache.