WordPress support often begins after the real performance cost has already happened.

A typical WordPress support case starts with a visible symptom: a slow page, a high server load, a poor PageSpeed result, a cache miss, a plugin conflict, or a backend that feels heavy.

Support usually sees the result, not the starting point

Most fixes are useful within their layer: tune a cache plugin, reduce assets, disable a heavy feature, upgrade hosting, inspect queries, or adjust a theme. These actions can improve a site, but they usually begin after WordPress has already loaded too much of itself for the request.

The earlier question is simpler and harder: did this request require the full PHP, plugin, hook, and database workload that WordPress executed before the page became measurable?

The missing support layer is execution scope

A complete support answer should not only ask how to repair the output. It should also ask which parts of WordPress needed to run before that output existed.

Rush - Powered by LiteCache belongs to this upstream layer. It narrows execution before classical caching, delivery, and browser optimization have to deal with the page.

Read the extended note on why WordPress performance support needs the upstream execution layer.