# Fast WordPress for Job Boards & Directories — xSpeed Cache

> Directory sites are faceted-search engines wearing a WordPress theme, and the queries are the bottleneck. How to make filtering fast with xSpeed Cache — including the exact AI prompt.

Page: https://xspeedcache.com/use-cases/for/job-boards/
Category: Tech & agencies
Also covers: job board, directory, listing site, classifieds, marketplace, business directory, property portal, aggregator, faceted search, filters, submissions, niche site

## The speed brief

- **Who arrives** — Someone narrowing thousands of entries to five
- **What they want** — Filters that respond and results that are current
- **How long you get** — Every filter click is a chance to lose them

## When speed decides the outcome

1. **The filter** — Category, location, price, date — combined, and changed constantly.
2. **The query** — Each combination is a fresh database query no page cache can pre-build.
3. **The bounce** — Directories live or die on browse speed. Nothing else about them is sticky.

## The story

A directory looks like a content site and behaves like a database application. Every visitor arrives and immediately starts combining filters — category, location, price band, date posted — and each combination is a query that has never been run in that exact shape before.

That is why page caching alone disappoints here. The homepage gets fast, the about page gets fast, and the one screen everybody actually uses stays exactly as slow as it was, because it cannot be pre-built.

What moves the needle is the layer underneath: an object cache holding the repeated taxonomy and meta lookups, short-lived caching on the common searches, and a database that gets swept so the query planner is not fighting years of accumulated cruft. The filters start feeling instant, which is the only feature this kind of site really has.

## What a site like this needs

- **Filters that respond immediately** — Browse speed is the product. Everything else on the site is secondary to how the filters feel.
- **Fresh listings without stale caching** — New submissions have to appear promptly, which caps how long anything can be held.
- **A database that stays lean** — User submissions, expired listings, and revisions accumulate fast and drag every query with them.

## The xSpeed features doing the work

- **Object cache (Redis / Memcached)** — Repeated taxonomy and meta lookups behind every filter combination are answered from memory. Guide: https://xspeedcache.com/docs/object-cache-redis-memcached
- **Search results cache** — The filter combinations people actually use get cached with a short lifetime, so the popular paths are instant. Guide: https://xspeedcache.com/docs/search-results-cache
- **Scheduled database cleanup** — Expired listings, revisions, and transients are swept on a schedule with OPTIMIZE TABLE included. Guide: https://xspeedcache.com/docs/scheduling-automatic-database-cleanup

## The exact AI prompt

Connect via xSpeed MCP (https://xspeedcache.com/docs/mcp-server-setup) or xSpeed Hub, then paste:

```
Using xSpeed, my WordPress directory site is slow on filtered browsing. Benchmark a filtered search first, then connect Redis object caching, enable search results caching with a short lifetime, cache static pages aggressively, and schedule a weekly database cleanup with table optimisation. Re-run the same filtered search and show me the before/after.
```

What happens: Your AI reports the query time on a real filtered search before and after — the number that decides whether people keep filtering.

## FAQ

### Why does page caching not fix a directory?

Because the pages people use are generated per query. A page cache stores finished HTML for a URL; a filtered search is effectively a new URL every time, so most requests miss. The object cache works a layer lower, on the repeated database lookups those queries share, which is why it is the one that helps here.

### Will caching delay new listings appearing?

Only by as long as you allow. Publishing a listing purges the archives it belongs to, and search-results caching uses a short lifetime by design. You set the ceiling; a few minutes is typical and invisible to users.

## More

- [Full playbook: xSpeed for Membership & LMS](https://xspeedcache.com/use-cases/membership-lms/index.md)
- [Tech & agencies: Freelance web developers](https://xspeedcache.com/use-cases/for/freelance-developers/index.md)
- [Tech & agencies: SaaS & startup sites](https://xspeedcache.com/use-cases/for/saas-startups/index.md)
- [All use cases](https://xspeedcache.com/use-cases/index.md)
- [Free plugin](https://wordpress.org/plugins/xspeed/)