Built-in caching

1. Search Result Caching (Object Caching)

Real estate searches are “expensive” for a server because it has to filter thousands of houses by price, location, and amenities simultaneously.

• How it works: When a user searches for “3-bed villas in Miami,” Zozonest calculates the results and then “caches” that specific list in the server’s memory for a set period (usually a few hours).

• The Benefit: If the next user performs the same search, Zozonest delivers the cached list instantly instead of asking the database to do the math all over again.

2. Transient API Integration

Zozonest utilizes the WordPress Transient API. This is a way of storing temporary data in the database with an expiration date.

• Use Case: The “Featured Properties” slider on your homepage doesn’t change every minute. Zozonest caches the “Featured” list so it doesn’t have to query the database every time a new visitor lands on your homepage.

• Auto-Clear: The plugin is smart enough to “flush” (delete) this specific cache whenever you add a new property or update an existing one, ensuring users always see the latest data eventually.

3. Map Marker Caching

Loading 500+ pins on a Full Map can lag the browser.

• Built-in logic: Zozonest often caches the coordinates of your properties into a single JSON file. Loading one small file is much faster for a browser than querying the database for the latitude/longitude of every single house individually.