Opcode Cache

Opcode cache is a mechanism that temporarily stores compiled PHP code in your server's working memory. When a visitor requests a WordPress page, the server normally translates the PHP files into machine code with each request. With opcode cache, that translation operation happens only once, after which the compiled version is reused. For an average WordPress site, this results in a speed gain of 30 to 70 percent, especially with many simultaneous visitors.

How opcode cache speeds up the translation process

PHP is an interpreted language. That means that with each request, the server reads the source code, parses it, compiles it to bytecode and then executes it. For a WordPress homepage with dozens of plugins and a theme, this process can hit hundreds of files. Opcode cache stores the bytecode in RAM and skips parsing and compiling on subsequent requests. Only when a PHP file changes, the cache for that file is refreshed. This saves computing power and noticeably lowers your site's response time.

From APC to OPcache: the evolution

Early opcode caches such as APC (Alternative PHP Cache) were community extensions that you had to install manually. Since PHP 5.5, OPcache is the official opcode cache and comes with PHP by default. Modern hosting providers activate OPcache automatically, but many SMBs with older or self-managed servers have not yet enabled the extension. Check via phpinfo() that opcache.enable is set to 1. If it's not, you're missing out on a free performance boost that improves Google Core Web Vitals immediately.

What opcode cache brings to WordPress sites

For an ecommerce store running WooCommerce or a content site with many visitors, opcode cache makes the difference between a slow and a smooth experience. Every second of speed gain increases conversion and lowers bounce rate. In a thoughtful WordPress hosting environment, opcode cache is among the basic features, along with object cache and a CDN. In practice, we see with clients that enabling OPcache halves the server load during peak hours. That means you can continue to grow longer on the same hosting package and scale up less quickly. For an SMB with a limited IT budget, that's a tangible cost savings.

Opcode cache is not just a technical optimization, but a practical lever for businesses that depend on a fast WordPress site. Applications range from ecommerce stores with thousands of products to content platforms with complex data structures. Here are four situations where opcode cache makes all the difference.

High traffic ecommerce stores

A WooCommerce ecommerce store with 500 products and 20 plugins loads dozens of PHP files with each request. During a Black Friday promotion or a social media campaign, the number of simultaneous visitors can increase fivefold. Without opcode cache, the server has to recompile all the code with each request, leading to slow load times and timeouts. With OPcache, the bytecode remains in memory and the server can process three to five times as many requests per second. For a professional ecommerce store, this is essential to avoid lost sales during peak hours.

Content platforms with many dynamic pages

A news site, knowledge base or community platform often generates pages dynamically based on user roles, taxonomies and custom post types. Each page request triggers queries and PHP logic. Opcode cache speeds up PHP execution, but note that it does not replace page cache or object cache. For optimal speed, combine opcode cache with a page cache plugin like WP Rocket or a server-side cache like Varnish. In practice, we see with content platforms that opcode cache reduces time to first byte (TTFB) by 40 to 60 percent, directly contributing to better Core Web Vitals scores.

Multisite environments and SaaS platforms.

WordPress Multisite runs dozens or hundreds of subsites on a single codebase. Each subsite shares the same PHP files, but executes unique queries and logic. Opcode cache stores the shared bytecode once, benefiting all subsites. For a SaaS platform or a franchise organization with local websites, this provides huge efficiency gains. The server does not have to recompile the core, plugins and themes for each subsite. This lowers hosting costs and makes scaling easier.

When opcode cache is the right choice and when it is not

Opcode cache makes sense for any WordPress site running PHP 5.5 or higher. It requires no extra memory or configuration and delivers immediate results. But: opcode cache does not solve slow database queries, unoptimized images or lack of page caching. If your site remains slow after enabling OPcache, the bottleneck lies elsewhere. First, check your Core Web Vitals and use a tool such as Query Monitor to identify bottlenecks. Opcode cache is a foundation, not a panacea.