What this guide helps you do
A practical performance workflow for PHP versions, extensions, resource usage, caching and database symptoms. Performance tuning should begin with measurement, not random values copied from a forum. Shared cPanel accounts often expose PHP selection, resource usage and database tools but not root-level service tuning. Work inside those boundaries and escalate genuine server contention to the host. This guide is written for production-minded administrators and site owners: make a backup before material changes, keep credentials private, and prefer the controls supplied by your own hosting provider when its environment differs from a generic example.
Before you begin
Record the domain, server or station you are changing and the current working state. If the task touches DNS, SSH, firewall rules, databases, stream credentials or application configuration, make sure you have a recovery path first. Screens and menu names can vary between cPanel, AzuraCast, VDO Panel and Linux releases, so follow the purpose of each step rather than forcing an old screenshot onto a newer version.
Step 1: Check the application and plugin requirements, then confirm the PHP version in MultiPHP Manager or the provider’s PHP selector. Newer supported versions can improve performance, but compatibility must be tested first.
Check the application and plugin requirements, then confirm the PHP version in MultiPHP Manager or the provider’s PHP selector. Newer supported versions can improve performance, but compatibility must be tested first.
Step 2: Review resource usage for CPU, memory, entry processes or I/O if your host exposes CloudLinux or similar metrics. Repeated limit hits indicate a capacity or application problem that caching alone may not solve.
Review resource usage for CPU, memory, entry processes or I/O if your host exposes CloudLinux or similar metrics. Repeated limit hits indicate a capacity or application problem that caching alone may not solve.
Step 3: Enable application-appropriate caching. On LiteSpeed hosting, WordPress can benefit from LiteSpeed Cache when configured correctly; avoid stacking multiple full-page caching systems on top of each other.
Enable application-appropriate caching. On LiteSpeed hosting, WordPress can benefit from LiteSpeed Cache when configured correctly; avoid stacking multiple full-page caching systems on top of each other.
Step 4: Inspect slow database symptoms at the application layer: oversized autoloaded options, unindexed custom queries, enormous transient tables or plugins producing excessive queries. Use phpMyAdmin carefully for inspection and backups before destructive cleanup.
Inspect slow database symptoms at the application layer: oversized autoloaded options, unindexed custom queries, enormous transient tables or plugins producing excessive queries. Use phpMyAdmin carefully for inspection and backups before destructive cleanup.
Step 5: Measure again after each meaningful change. Page speed tools, server response time and real user behaviour matter more than a dashboard score achieved by breaking dynamic functionality.
Measure again after each meaningful change. Page speed tools, server response time and real user behaviour matter more than a dashboard score achieved by breaking dynamic functionality.
Verification checklist
Confirm pages still function for logged-in and logged-out users, carts/forms are excluded from inappropriate caching, PHP errors are not increasing, resource-limit events are reduced, and database backups exist before cleanup. Always test from the user side as well as the administrator side. A control panel saying “active” is useful evidence, but it is not the same as an external browser, player or SSH client proving that the full path works.
Troubleshooting method
When the result is not what you expected, avoid changing several unrelated settings at once. Identify the last known-good point, collect the exact error message and determine which layer is failing: DNS, network, authentication, service process, application configuration, web/stream delivery or browser/player. Check timestamps and logs around the failure. If you need to escalate to hosting support, include the affected hostname or station, the time of the test, what you expected, what happened instead and the checks you already completed. Do not include passwords, API keys or private stream keys in a public ticket or screenshot.
Keep the system maintainable
Document the final configuration after it works. Note the important URLs, service names, backup locations, renewal/expiry dependencies and any change that would surprise another administrator. Revisit the setup after major platform upgrades because defaults, supported runtimes and interface labels evolve. A reliable environment is not one that was configured once; it is one whose current state is understood, monitored and recoverable.
Where to go next
Use the related guides below to expand the setup rather than solving the same problem from scratch. If the platform has outgrown shared hosting or you need managed implementation, the service recommendation at the bottom of this guide links to the most relevant hosting, streaming, development or optimisation option on this site.
Interface labels and supported versions can change. Use the controls and documentation supplied with your current hosting environment, and keep a backup or recovery path before material changes.