{"id":495642,"date":"2025-06-11T11:43:51","date_gmt":"2025-06-11T11:43:51","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=495642"},"modified":"2025-06-18T04:35:09","modified_gmt":"2025-06-18T04:35:09","slug":"how-to-enable-wordpress-full-page-caching","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/how-to-enable-wordpress-full-page-caching\/","title":{"rendered":"How to Enable WordPress Full Page Caching"},"content":{"rendered":"\n

If you’re running a WordPress site and want website faster performance<\/a> but don\u2019t want to use plugins, this guide is for you.<\/p>\n\n\n\n

We will show you how to enable full page caching using define('WP_CACHE', true);<\/code> and a few lines of code. No plugins, no bloat\u2014just clean and simple optimization.<\/p>\n\n\n\n

\"full-page-cache-wordpress\"<\/figure>\n\n\n\n

What Does define('WP_CACHE', true);<\/code> Do?<\/h3>\n\n\n\n

This line tells WordPress to enable caching support. It looks for a file called advanced-cache.php<\/code> in the wp-content\/<\/code> directory.<\/p>\n\n\n\n

If it finds that file, it will try to serve cached content before loading the entire WordPress engine.<\/p>\n\n\n\n

Why WordPress Won\u2019t Cache Automatically<\/h3>\n\n\n\n

Adding WP_CACHE<\/code> does not cache your site by itself. You need to create the logic to store and serve cached files. Normally, plugins handle this. But you can do it yourself with a few lines of code.<\/p>\n\n\n\n

Step 1: Create Your Cache File<\/h3>\n\n\n\n

Inside wp-content\/<\/code>, create a file called advanced-cache.php<\/code>. Paste the following code:<\/p>\n\n\n\n

<?php\n$cache_key = md5($_SERVER['REQUEST_URI']);\n$cache_file = __DIR__ . '\/cache\/' . $cache_key . '.html';\n\nif (file_exists($cache_file) && (filemtime($cache_file) > (time() - 3600))) {\n    readfile($cache_file);\n    exit;\n}\n\nob_start();<\/pre>\n\n\n\n
This code checks if a cached file exists and is fresh. If yes, it serves it and skips WordPress.<\/p>\n\n\n\n
Step 2: Save Output to Cache<\/h3>\n\n\n\n
At the end of your footer.php<\/code> file or right after wp_footer()<\/code>, add:<\/p>\n\n\n\n
<?php\nif (defined('WP_CACHE') && WP_CACHE) {\n    $cache_key = md5($_SERVER['REQUEST_URI']);\n    $cache_file = WP_CONTENT_DIR . '\/cache\/' . $cache_key . '.html';\n    file_put_contents($cache_file, ob_get_contents());\n}\nob_end_flush();\n?><\/pre>\n\n\n\n
This saves the full page as an HTML file so it can be loaded next time without running WordPress.<\/p>\n\n\n\n
Step 3: Create the Cache Directory<\/h3>\n\n\n\n
In most cases, the cache<\/code> folder inside wp-content\/<\/code> needs to be created manually, but your theme or server environment auto-generates it.<\/p>\n\n\n\n
Make a folder inside wp-content\/<\/code> named cache<\/code>. Give it write permissions (usually 755 or 775).<\/p>\n\n\n\n
Step 4: Set Cache Rules<\/h3>\n\n\n\n
To avoid caching for logged-in users or specific pages, you can extend the logic. For example:<\/p>\n\n\n\n
if (is_user_logged_in()) return;\n<\/pre>\n\n\n\n
This helps avoid issues with user-specific content like carts or dashboards.<\/p>\n\n\n\n
Step 5: Test Your Cache<\/h3>\n\n\n\n
Open your site in incognito mode. View the source and refresh twice. You should see faster load times on repeat visits.<\/p>\n\n\n\n
Bonus Tips (Without Plugins)<\/h3>\n\n\n\n