WP Performance Suite: caching, query load and page weight
Site speed is rarely one problem. Slow WordPress performance usually comes from three places: the page waits on the database, loads a framework it does not need, and pays for blocking requests before the first pixel appears. WP Performance Suite handles those causes in order: less work per request, fewer requests, smaller payload.
Where WordPress performance goes
A typical WordPress install spends most of its budget on repeated queries, plugins that load everywhere, and front-end libraries built for applications rather than pages. The suite starts with a measurement of that budget: how many queries per page, which assets block rendering, what TTFB the host actually returns.
The order matters. Caching a slow page makes a slow page faster, it does not make it light. Removing a dependency usually returns more than tuning a cache rule.
What is inside
- Query and cache layer. Caching and a scheduler from Atomic Framework: maintenance runs outside the request, not inside it.
- Front-end kit. Oat UI: semantic HTML, CSS and JS in about 10 KB, zero dependencies. Tables and file uploads come as small extensions. Live demo and documentation are on oat.ink.
- Indexing. Index Runner sends IndexNow notifications on publish and update, so new URLs do not wait for the next crawl.
- Server-side runtime. Redis and WebSocket support from Atomic Framework, used when a project needs live updates or background jobs without a second service.
Front-end without a framework
Oat styles semantic tags instead of class soup. A table, a form and a dialog work from markup; JavaScript only covers what CSS cannot. The whole library is smaller than one component of a typical UI framework, which changes the median page weight before any compression.
Oat Table adds sorting, filtering and row selection. Oat Upload adds drag-and-drop and progress. Both are extensions, so a project pays only for what it renders.
Indexing and measurement
Index Runner is a WordPress plugin under GPLv2 that speaks IndexNow: WordPress 5.8 and PHP 7.4 are enough. It removes the gap between publishing and the first crawl, which matters for news sections and product catalogs.
Measurement stays honest: before and after numbers come from the same host, the same page and the same tool. A cache hit rate without a TTFB number proves nothing.
How a project starts
The first step is an audit of one template: query count, asset list, TTFB. Then work goes in order of return: remove, defer, cache. Front-end changes ship with the theme, cache and query rules with the server.
For sites that need the full stack, the WordPress optimization service covers the audit and the rebuild. Source code for the components lives on GitHub: Oat, Oat Table.
