Performance
Gzip, browser Cache-Control, the Tools performance suite, and why the warm process stays cheap.
5 min read
The big win is architectural: one event loop, plugins registered once, page cache in core. On top of that, Tools → Performance suite writes gzip and browser-cache env vars and restarts via tmp/restart.txt on Passenger/Plesk.
Gzip
JF_GZIP_ENABLED, JF_GZIP_LEVEL (1–9), JF_GZIP_MIN_BYTES. Compresses HTML, JSON, CSS, JS above the minimum size.
Browser cache
JF_BROWSER_CACHE_ENABLED, JF_BROWSER_CACHE_HTML_MAX_AGE (default 60s), JF_BROWSER_CACHE_STATIC_MAX_AGE (default 86400s), JF_BROWSER_CACHE_SWR (stale-while-revalidate, default 300s).
Admin APIs
/api/performance/settings|stats|clear|stats/reset (administrator), alongside /api/cache/*. Saving settings from Tools is the supported UI.
Tip
See How it works for the request lifecycle and Caching for object and page cache.