PHP OPcache is enabled by default on all WordPress sites hosted on Pressidium, including Production and Staging environments.

WordPress Site Health may report Opcode cache is not enabled. That message is not a Dashboard setting, and it is not proof that PHP OPcache is off on Pressidium.

This guide applies to Pressidium Managed WordPress Hosting. You cannot turn OPcache on or off in the Dashboard.

What you can check in the Dashboard

You can confirm the PHP version. You cannot see OPcache status there.

  1. Open Websites, then select the website.
  2. Select Production or Staging in the navigation bar.
  3. Open Settings.
  4. Check the PHP version shown in PHP Engine.

Switching PHP version is not an OPcache toggle. Follow Switch your PHP runtime only when you intend to change the runtime.

The warning discussed here appears in WordPress admin under Tools > Site Health. Checking your PHP version in the Pressidium Dashboard does not establish whether OPcache is running.

Why WordPress Site Health may say opcode cache is not enabled

Pressidium disables several opcache_* PHP functions, including opcache_get_status and opcache_get_configuration. See Which PHP functions are disabled?.

The WordPress Site Health opcode-cache check, introduced in WordPress 7.0, uses opcache_get_status. If that function is unavailable or does not return a status showing OPcache enabled, the check reports Opcode cache is not enabled.

The warning therefore does not, by itself, prove that OPcache is off. It also does not establish that OPcache is running or that the warning is a false positive for your site.

Do not enable the disabled opcache_* functions yourself to retest Site Health.

Check OPcache with phpinfo() (optional)

If you are comfortable uploading and deleting a PHP file, you can inspect the OPcache status reported by the PHP runtime serving your website. Run this check separately for Production or Staging, depending on which environment you are investigating.

  1. Using SFTP or SSH, create a temporary file named opcache-check.php in the website’s document root for the environment you are checking. Use only these contents:
<?php phpinfo(INFO_MODULES);
  1. Open /opcache-check.php through that environment’s website URL in your browser. INFO_MODULES limits the output to loaded modules and their settings.
  2. Find Zend OPcache, then check the Opcode Caching row. Up and Running means OPcache reports that it is active for the PHP runtime handling this request. The presence of the section or an opcache.enable value alone is not the same as this runtime status.
  3. Note the result. If you need to share it with Support, capture only the relevant OPcache rows.
  4. Delete opcache-check.php through SFTP or SSH immediately after checking, even if the result is missing or unexpected. Confirm the URL no longer serves the configuration page.

This check does not call opcache_get_status, so disabling that function does not inherently prevent phpinfo from reporting OPcache status. It reports on the runtime serving that web request; it does not verify every server or the other environment. An SSH/CLI check can differ because command-line PHP has a separate OPcache setting.

If Zend OPcache is missing, Opcode Caching reports Disabled, the page cannot be displayed, or the result conflicts with WordPress Site Health, contact Support for help interpreting it. Do not change PHP settings to try to make the results match.

What you cannot change yourself

There is no published Dashboard control for OPcache.

Do not add php_flag or php_value directives to .htaccess. On this platform that causes a 500 Internal Server Error, because the stack does not use the Apache PHP module. See How to override php.ini variables.

A php.ini change is a Support request. Pressidium evaluates those requests. Do not assume Support will expose or toggle OPcache that way.

When to open a ticket

Open a support request when:

  • You are unsure what the Site Health warning means for your site and need help assessing it.
  • The optional phpinfo check is unavailable, reports a missing or disabled OPcache status, or conflicts with Site Health.
  • The site is slow and you need help investigating the performance issue.
  • You need a php.ini change evaluated, and you can name the variable and value.
  • You need an exception for a disabled opcache_* function, knowing Pressidium may refuse it.

Include the team name, website, environment (Production or Staging), PHP version shown in PHP Engine, WordPress version, and the exact WordPress Site Health text. If the site is slow, describe the affected pages and when the issue started.

If you ran the optional phpinfo check, include the Opcode Caching result and when you checked it. You do not need to leave the file on the site for Support.

Do not switch PHP version only because of the warning.

Where to go next