Soft2Hosting

WordPress Caching on Shared Hosting: Page Caching, mod_expires & Plugin Setup

01 Oct 2026 · 3 min read

Optimizing page loading speed for WordPress websites running on cPanel shared hosting is essential for improving visitor engagement, conversion rates, and search engine visibility. Because shared hosting environments distribute server resources among multiple accounts, unoptimized dynamic database queries and repeated PHP script executions can slow down your site during traffic spikes. Implementing structured caching techniques minimizes server load while delivering static, pre-rendered pages to your visitors in milliseconds.

Understanding How Caching Works in WordPress

Every time a visitor opens an uncached WordPress page, the server executes a series of resource-heavy operations: it initiates the PHP runtime, loads core files, activates plugins, queries the MySQL database for post content and metadata, processes your theme templates, and finally compiles the resulting HTML. When dozens of visitors access the site simultaneously, this cycle can consume substantial CPU and memory resources.

Caching intercepts this cycle at multiple levels:

Full-Page Caching: When the first visitor requests a page, a caching plugin saves the generated HTML output to disk. Subsequent visitors requesting that same page receive the pre-built HTML file directly, bypassing PHP execution and database queries entirely.
Browser Caching: Tells the visitor's web browser to store static files (such as images, CSS stylesheets, and JavaScript files) locally on their device, preventing repeat requests for identical assets during navigation.
Object Caching: Stores complex database query results in temporary memory so that dynamic components (such as shopping carts or customer profile headers) load without repeatedly executing SQL queries.

Step 1: Configuring Browser Caching via mod_expires in .htaccess

The Apache web server provides a powerful module called mod_expires that manages HTTP Expires and Cache-Control headers. By configuring browser expiration rules in your root .htaccess file, you instruct browsers on how long to retain static media.

To implement browser caching, log in to your cPanel dashboard, open the File Manager, navigate to public_html, edit your .htaccess file, and add the following block above the standard # BEGIN WordPress section:

<IfModule mod_expires.c>
    ExpiresActive On

    # Default expiration period
    ExpiresDefault "access plus 2 days"

    # Static media files (cache for 1 year)
    ExpiresByType image/jpg "access plus 1 year"
    ExpiresByType image/jpeg "access plus 1 year"
    ExpiresByType image/gif "access plus 1 year"
    ExpiresByType image/png "access plus 1 year"
    ExpiresByType image/webp "access plus 1 year"
    ExpiresByType image/svg+xml "access plus 1 year"
    ExpiresByType image/x-icon "access plus 1 year"

    # CSS and JavaScript (cache for 1 month)
    ExpiresByType text/css "access plus 1 month"
    ExpiresByType application/javascript "access plus 1 month"
    ExpiresByType text/javascript "access plus 1 month"

    # Web fonts (cache for 1 year)
    ExpiresByType font/woff2 "access plus 1 year"
    ExpiresByType font/woff "access plus 1 year"
    ExpiresByType font/ttf "access plus 1 year"
</IfModule>

Safety Precaution: Always make a backup copy of your existing .htaccess file (e.g., .htaccess.bak) before applying custom directives. A syntax error inside .htaccess will trigger an immediate HTTP 500 Internal Server Error.

Step 2: Selecting and Configuring a Page Caching Plugin

On shared hosting, choose a lightweight, reliable caching plugin that matches your server environment:

LiteSpeed Cache: If your shared hosting plan utilizes LiteSpeed web server technology (such as Soft2Hosting Business Pro or Enterprise Pro), install the official LiteSpeed Cache plugin. It communicates directly with server-level cache modules, delivering superior performance with minimal PHP overhead.
WP Super Cache: For standard Apache shared hosting, WP Super Cache generates static HTML files that Apache serves directly without invoking the PHP interpreter. In WP Super Cache settings, select Caching On and choose the Simple delivery method.

Crucial Plugin Rule

Never install or activate two page-caching plugins simultaneously. Running multiple caching tools concurrently leads to conflicting .htaccess rewrite rules, corrupt cache headers, and broken page rendering.

Step 3: Handling Dynamic Page Exclusions for WooCommerce

While caching static blog articles and business brochure pages is straightforward, dynamic ecommerce pages must never be cached. If your shopping cart or checkout page is cached, one customer might see another customer's personal details or cart contents.

In your caching plugin's settings, ensure the following URLs are explicitly added to the cache exclusion list:

/cart/
/checkout/
/my-account/
/wc-api/*

Most reputable caching plugins automatically detect WooCommerce and apply these exclusions, but manual verification in plugin settings guarantees that customer checkout sessions remain completely private.

Step 4: Monitoring Inodes and Disk Quotas in cPanel

Full-page caching creates hundreds or thousands of static HTML files on your storage volume. In shared hosting, every file and folder accounts for one inode. If your caching plugin generates excessive cache files without regular purging, your account could approach its inode quota.

To maintain healthy resource utilization:

Set cache garbage collection to purge expired pages every 24 hours.
Avoid aggressive caching of search query URLs (e.g., /?s=query) to prevent cache directory bloating.
Monitor your disk space and inode count in cPanel's Statistics sidebar.

Soft2Hosting provides shared hosting plans with fast NVMe storage, free SSL certificates, and cPanel management. Plans such as Business Pro and Enterprise Pro include LiteSpeed caching support to keep your WordPress websites loading swiftly.

Review plan options on Soft2Hosting Shared Web Hosting.