You could go through the code, disable plugins and even reinstall the CMS software, but these solutions could create downtime and root-cause analysis could still come up with nothing. Instead of tediously combing through web application code and plugins, CloudLinux PHP X-Ray lets you monitor and diagnose performance in CMS applications such as WordPress, Joomla, or Drupal without affecting uptime.
After the PHP X-Ray feature BETA release in CloudLinux OS+ many of our customers requested the same tool for their end-users to be able to scan their website and identify performance bottlenecks in case of a slow website or another issue. So we are happy to announce a new PHP X-Ray App that end-users of web hosting services can use from web-interface
Performance issues can stem from several factors -- sluggish and poorly optimized plugins, slow database queries, code functionality, external calls to slow APIs, or possibly spikes in website traffic. PHP X-Ray offers tracing tools that easily plug into your end-users' CMS and analyzes the site to help them identify the root cause.
After running a PHP X-Ray trace, end-user can drill down to their site and identify the exact plugin or other issue causing performance degradation. In just a few minutes, site owners managing a CMS website can identify performance issues without the overhead of traditional root-cause analysis.
The beta for PHP X-Ray Admin was so popular, our testers asked for an end-user version that supports their CMS-based websites. We’ve released a new end-user PHP X-Ray version that can be used for individual CMS websites that runs as an installed plugin.
# yum install lvemanager alt-php-xray --enablerepo=cloudlinux-updates-testing
# yum update lvemanager alt-php-xray --enablerepo=cloudlinux-updates-testing
For any administrators familiar with the LVE Manager, the admin interface has one additional change: an additional checkbox in the User Interface of LVE Manager in → Options tab → Setting tab. The “Hide the PHP X-ray app in web-interface” is checked by default and must be unchecked to allow end-users to access the trace dashboard:
As you can see in the image above, the end user can trace multiple domains and subdomains, view the status of their trace, set the IP to check, set the number of requests to collect, and set a timeframe for collection. End-user traces are limited to one trace at a time, and end users cannot see admin traces.