Understanding PHP and version management

Updated on

Definition

PHP is the programming language used by most CMSs (WordPress, Joomla, PrestaShop). It is important to use the most recent version compatible with your site to ensure optimal performance and security.

PHP versions

PHP evolves over time: performance and security improvements, new features, and so on.

So it is always best to use the most recent PHP version possible that is compatible with your PHP scripts, and to update your site so that it supports new versions. That way, you get extra assurance of security and performance.

LRob does everything it can to offer you the latest PHP versions as soon as possible: on our shared servers, they are generally available within the week of release.

The up-to-date list of supported PHP versions can be found on the official site: https://www.php.net/supported-versions.php

PHP versions available with your LRob hosting

As of May 2025, here are the versions available on your LRob hosting:

  • PHP 8.4
  • PHP 8.3
  • PHP 8.2
  • PHP 8.1 (on simple request)
  • PHP 8.0 (on simple request)
  • PHP 7.4 (on simple request)
  • PHP 5.6 (on simple request)

If this page has not been updated for too long, please contact us so that we can tell you the current versions and update the information above.

Choosing a PHP version

LRob lets you choose your PHP version yourself. This is an advantage because you can use the script of your choice with the PHP version of your choice, and the very latest PHP versions become available very quickly at LRob.

Nevertheless, one rule must be followed to get optimal security and performance: you should therefore use the most recent PHP version supported by your script.

To set your PHP version:

  • Go to your Plesk control panel
  • Under your domain, go to the “PHP Settings” section
  • Select the desired PHP version, and confirm with “OK”
  • After a few seconds, the PHP version is active
  • Check that your site works properly before deciding whether to keep this version.

PHP handlers

The server delivering web files is generally Apache.

Apache only serves files and cannot natively run PHP code. PHP is therefore run by Apache through what is called a “handler”.

The oldest PHP handler was mod_php, an Apache extension that runs PHP; files then had to belong to Apache for PHP to be able to write to the web files.

Then CGI and FastCGI appeared, allowing much better performance but above all letting files belong to the user matching the site, which gives better independence between sites on a server and therefore better security. FastCGI thus halves page load times compared to mod_php while providing a strong security gain.

FPM (called “PHP application” in the French interface) is the latest handler, used by default on CentOS 7. It allows even better performance and better management of each site’s resources. FPM spawns one instance per PHP version. FPM also has the advantage of letting you set individually the maximum number of simultaneous FPM processes (and therefore PHP executions) for each site, as well as the number of “spare” processes (that is, waiting for a connection). Several modes exist, adjustable through the domain’s PHP settings when you select FPM. By default it is “ondemand”, so no process is started if there is no request in progress, but it is possible to pre-launch FPM handlers (at the cost of a little RAM) to slightly speed up response times.

Since Plesk Obsidian 18.0.39 (October 13, 2021), it is also possible to choose “dedicated FPM”. Dedicated FPM provides an independent FPM service/handler for a site. Technically, this means one extra system process (a “service”). At the cost of a little RAM usage, this slightly improves the handler’s startup speed, and therefore the site’s load time, improving the “TTFB” metric (initial server response time) by a few milliseconds. The dedicated FPM option is therefore best used on very high-traffic or most critical sites. The difference is in the order of a few percent of load speed, particularly on apps that are hungry for FPM processes such as Nextcloud. Finally, while the difference can be interesting, it remains relatively marginal compared with what optimizing the site’s code or a Redis cache can bring.

Note that handler settings, like all PHP settings, can be set at the Plesk service plan level (30-domain license or higher).