Caching stores reusable responses or files so a site can load with less repeated work. Your site may use browser caching, a WordPress cache plugin, host-level caching, or a content delivery network. Identify the active layers before changing them.
The Control Center does not currently provide a cache-purge tool. Use the controls belonging to your application, supported hosting cache, or CDN. Its WordPress inventory is not a cache or performance setting.
Clear stale content #
- Confirm that you saved or published the intended change.
- Open the page while signed out, preferably in a private browser window. Check the exact hostname and URL.
- Use your application's cache-purge action for the affected page or site.
- If hosting cache controls or a CDN are part of your service, clear the affected content there as well.
- Reload and compare the result on another device. A private window can help with browser state, but it does not bypass every server or CDN cache.
Purge only what you need when possible. A full cache purge can increase server work while visitors repopulate it.
Improve performance in measured steps #
Record the slow URL, whether the visitor is signed in, and the time of the test. Check an ordinary page and an interactive action separately. A cached home page can load well while search, checkout, or administration remains slow.
Resize oversized images, remove unused components, and test one performance change at a time. Avoid installing several plugins that attempt the same caching or asset-optimization task. Persistent object caching requires a compatible service from the host; adding a plugin alone does not provide that service. WordPress optimization guide
For personalized pages, follow the application vendor's cache exclusions. Check account pages, cart contents, forms, and logged-in responses before enabling a broad page-cache rule. Never accept another customer's content appearing in a shared cache as normal behavior.
Verify and troubleshoot #
Compare results under similar conditions and confirm that the site still works on mobile and desktop. If the problem appeared after combining or deferring scripts, revert that specific optimization and retest.
For intermittent slowness, collect timestamps, affected URLs, recent changes, and matching log entries. Ask support whether account limits or a hosting-side service contributed. Avoid repeatedly increasing PHP limits without identifying the failing request.
Related: PHP configuration, storage usage.
Leave a Reply