# Fast WordPress for Recruitment & Staffing Agencies — xSpeed Cache > Job boards are filter-heavy and database-bound, and candidates browse them impatiently. How recruitment agencies keep listings fast on WordPress with xSpeed Cache — including the exact AI prompt. Page: https://xspeedcache.com/use-cases/for/recruitment-agencies/ Category: Professional services Also covers: recruitment, recruiter, staffing, staffing agency, headhunter, talent, hr, job agency, employment agency, temp agency, executive search, hiring, candidates, vacancies ## The speed brief - **Who arrives** — A candidate filtering roles on their commute - **What they want** — Live listings, useful filters, a fast apply button - **How long you get** — One commute, competing with every job board ## When speed decides the outcome 1. **The browse** — Candidates filter by title, location, salary, contract type — all at once. 2. **The query** — Every filter combination is a database query the cache cannot pre-build. 3. **The apply** — A listing that takes five seconds is a candidate who applies elsewhere. ## The story Tobi runs a staffing agency with about four hundred live roles. The site serves two audiences that want opposite things: employers reading a polished, static pitch, and candidates hammering a filtered search for “remote, contract, senior, posted this week”. Page caching solved the first audience immediately and did nothing for the second, because every filter combination is a different query and none of them are a page you can pre-build. Listing pages stayed slow exactly where the candidates were. The object cache is what fixed it: repeated taxonomy and meta queries answered from memory instead of the database, so filtered results come back fast even though they are generated live. The employer-facing pages are static; the search actually searches. ## What a site like this needs - **Fast filtered search** — The core interaction is a query, not a page. It has to be quick even though it cannot be cached as HTML. - **Listings that are never stale** — A filled role still showing as open wastes a candidate’s time and embarrasses you with the client. - **Two audiences, one site** — Employer pages should be static and instant; candidate search should be live. The same install has to do both. ## The xSpeed features doing the work - **Object cache (Redis / Memcached)** — Repeated taxonomy and meta queries behind filtered search are answered from memory instead of the database. Guide: https://xspeedcache.com/docs/object-cache-redis-memcached - **Search results cache** — Common searches are cached with a short lifetime, so the popular filter combinations return instantly. Guide: https://xspeedcache.com/docs/search-results-cache - **Per-post cache rules** — Give job listings a short cache lifetime and static employer pages a long one, on the same site. Guide: https://xspeedcache.com/docs/per-post-cache-rules ## The exact AI prompt Connect via xSpeed MCP (https://xspeedcache.com/docs/mcp-server-setup) or xSpeed Hub, then paste: ``` Using xSpeed, my recruitment site has 400 live job listings and filtered search is slow. Benchmark it, connect the object cache for the repeated taxonomy and meta queries behind filtering, enable search results caching with a short lifetime, and set a short cache lifetime on job listings while employer and about pages get a long one. Then re-test a filtered search and show me the before/after query time. ``` What happens: Your AI wires up the object cache, tunes per-type cache lifetimes, and reports the improvement on a real filtered search. ## FAQ ### Can filtered search results be cached at all? Partly. Full-page caching cannot cover every filter combination, which is why the object cache matters most here — it makes the live query fast rather than trying to pre-build it. Popular searches can additionally be cached with a short lifetime, which covers the combinations candidates actually use. ### What happens when a role is filled? Unpublishing or editing the listing purges its cached page immediately, and a short cache lifetime on listings means even listing archives refresh quickly. Employer-facing pages, which change rarely, keep a long lifetime. ## More - [Full playbook: xSpeed for Membership & LMS](https://xspeedcache.com/use-cases/membership-lms/index.md) - [Professional services: Real estate agencies](https://xspeedcache.com/use-cases/for/real-estate/index.md) - [Professional services: Law firms](https://xspeedcache.com/use-cases/for/law-firms/index.md) - [Professional services: Accountants & bookkeepers](https://xspeedcache.com/use-cases/for/accountants/index.md) - [Professional services: Insurance agencies](https://xspeedcache.com/use-cases/for/insurance-agencies/index.md) - [All use cases](https://xspeedcache.com/use-cases/index.md) - [Free plugin](https://wordpress.org/plugins/xspeed/)