Area 03 of 11 · Caching
Pages answered in milliseconds instead of being rebuilt every time.
Ready-made pages are served from disk or memory instead of being built for every visitor.
The page is generated normally and saved as HTML.
A small drop-in answers from the saved copy in a few milliseconds.
Saving a post clears that page and the pages that list it. (Pro) The cache is rebuilt in the background.
Page cache Free+ Pro extras
Saves each page as ready-made HTML, so the server can answer in a few milliseconds instead of building the page from the database every time.
Visitors get a saved copy of each page. Logged-in users, form submissions, carts and checkouts are never cached. The cache clears itself whenever you save content, menus or settings.
After this a page is rebuilt on the next visit. 10 hours keeps form security tokens valid.
Separated by spaces. Add pages that show something different for every visitor.
After the cache is cleared, the site visits its own pages so they are cached again before real visitors arrive. Runs again once a day. Pages hidden from search engines are skipped.
Lower this on small hosting plans. 10 rebuilds 600 pages an hour without being noticed.
Browser cache Free
Tells browsers to keep images, styles and scripts so returning visitors do not download them again, and compresses files on the way out.
Images, fonts, CSS and JS are kept for a year (WordPress adds a version number to theme and plugin files, so changes still show up immediately). Text files are sent gzip or Brotli compressed. Written to .htaccess on Apache and LiteSpeed.
Object cache (Redis) Pro
Keeps database results in memory so wp-admin and pages that cannot be page-cached load faster. Needs a Redis server on your hosting.
Only turns on after a successful connection test. If Redis ever stops, the site keeps working without it.
Usually 127.0.0.1. Your host tells you if it is different, or gives a socket path like /var/run/redis/redis.sock.
6379 is the standard Redis port. Use 0 with a socket path.
Only if your Redis server requires one.
Use a different number for every site that shares the same Redis server.
REST API cache Pro
Saves REST API answers so a headless front end, app or widget gets content in milliseconds.
Only public GET requests from visitors who are not logged in are cached. The cache clears itself whenever content, menus or settings are saved.
A safety limit; saving content clears the cache straight away anyway.
Separated by spaces. Carts, forms and anything personal belong here.
Good to know
Logged-in users, carts, checkouts and URLs you exclude are never cached.
Deactivating Keel removes the drop-in and the cache folder; nothing is left behind.
(Pro) Redis keeps database results in memory, which also speeds up wp-admin.
Questions about Caching
Then leave the page cache off and keep browser caching. Keel never fights a host cache.
"Clear cache" in the admin bar, on any page.
Five minutes from now
Give your site a keel.
Steady when traffic spikes, calm when attacks come, found when people search. Start free; go Pro when a site needs more.