How to Set Up xSpeed Cache on WordPress in 2026

Updated September 2026

A slow WordPress site costs you visitors, rankings, and conversions. xSpeed Cache is ours: we build it at WPDeveloper as an all-in-one WordPress caching and performance plugin that serves pages as static files before PHP and WordPress even load, delivering cache hits in as little as 5–15ms and making pages load up to 17× faster on cache hits. This guide walks you through installing xSpeed, understanding what it optimizes automatically, configuring the settings that matter most, and confirming the speed gains for yourself.

Quick summary: the five minutes that matter

What You’ll Need

• A self-hosted WordPress site (admin access required)
• A few minutes to install and configure the plugin
• A baseline speed measurement, taken before you activate anything

That last item is the one people skip and regret. Run a scan on your homepage now, while the site is still in its current state, so you have something to compare against later.

Step 1: Install and Activate xSpeed Cache

1. From your WordPress dashboard, go to Plugins → Add New.
2. Search for xSpeed Cache.
3. Click Install Now, then Activate.

Once activated, xSpeed adds its own settings page to your dashboard, where all caching and optimization controls live. Our installing and activating guide covers the manual upload route if your host blocks directory installs.

Already running another caching plugin? Import its settings before you remove it. WP Rocket in particular keeps everything in a single wp_options row and deletes that row on uninstall, so migrating from WP Rocket has to happen in the right order or there is nothing left to read. W3 Total Cache and WP Super Cache are handled the same way, and our migration reference lists what travels across.

Step 2: What Activation Does, and What Turns Caching On

xSpeed is deliberately conservative on activation. It creates its cache folder, applies a small recommended starter set on a fresh install (GZIP, browser cache headers, HTML and CSS minification) and sends you to the setup wizard. It does not start page caching on its own: writing the cache drop-in and the WP_CACHE line is a change you should choose, so it happens when you apply a preset in the setup wizard or switch it on in the Page Cache panel. From then on, repeat visits, and first visits after a page is cached, load from static files instead of triggering a full PHP/WordPress/database cycle. This is where most of the initial speed boost comes from.

It also ships exclusions rather than an empty box. Cart, checkout and account pages are kept out of the page cache automatically when WooCommerce is active, which is the setting most likely to cause real damage if it is left to you to remember. Not every free caching plugin does this, and which free caching plugins actually cache checks twelve of them against their own source.

From there, you can layer on additional optimizations to push performance further.

Step 3: Configure the Core Performance Settings

Open the xSpeed Cache settings page in your dashboard to review and enable the optimizations that fit your site. The free version includes:

• Page, Mobile, Browser & Object Caching. Cache your content at multiple levels so both desktop and mobile visitors get fast, static responses, and repeated database queries are avoided.
• Minify & Combine CSS/JS/HTML. Strip out unnecessary characters and combine files to reduce the number of requests and the amount of code the browser has to parse.
• Lazy Load. Defer loading of images and other media until a visitor actually scrolls to them, speeding up initial page load.
• GZIP Compression. Compress your site’s files before they’re sent to the browser, cutting down transfer size.
• CDN rewrite & Cloudflare integration. Serve static assets from your CDN hostname, and purge Cloudflare’s edge whenever your own cache purges. See the CDN and Cloudflare docs.

Enable each optimization one at a time and reload your site after every change. This makes it easy to spot whether a setting improves things or causes a conflict with your theme or other plugins. The page cache documentation covers what each control does.

Object caching deserves a note of its own. It is the setting that speeds up the pages no page cache can touch, which on a store means checkout and account pages. Pointing it at Redis? Two of the defaults that ship with the usual drop-in will stop a site the moment Redis restarts or fills up, and our Redis walkthrough fixes both in a line each.

Step 4: Confirm It Is Actually Working

Now check the result, and check it the way a stranger arrives rather than from the admin screen that just told you it worked.

Point the free xSpeed Scan at your homepage and at one real post. No account is required. It grades the caching signals in the response a browser actually receives, times the first byte, and names whichever caching plugin answered, which is how people find out the plugin they deleted last year is still running.

Prefer to do it by hand? Our guide to reading the response yourself sorts the headers that genuinely prove a hit from the six that merely look like they do, and explains why WordPress Site Health can show a healthy page cache on a site with caching switched off.

Three things to expect from the numbers

• Sign out first. Nearly every caching plugin hands signed-in users a freshly built page, so an admin browser reports a miss forever and teaches you nothing.
• Go past the homepage. Home pages are frequently handled by their own rules, which is how a fast front page hides a post cache that never engaged.
• Do not wait for the Lighthouse score to move. Our study of 958 WordPress sites found median TTFB falling by 73% while LCP stayed put. A cache shortens server time and nothing else; images and third-party scripts own the rest, which is the subject of our piece on caching that did not work.

If a page doesn’t show the improvement you expected, revisit Step 3 and confirm the relevant caching or minification setting is actually enabled for that page type. These five account for most of what goes wrong in the first week:

Step 5: Explore xSpeed Pro for Deeper Optimization

Once you’re comfortable with the free feature set, xSpeed Pro adds tools for teams that want to go further:

• Recommendations engine. Get specific, prioritized suggestions for improving your site’s performance.
• Composite performance score. Track a single, overall score for your site’s speed health over time.
• Frequently-missed URLs & per-URL hit/miss heatmap. See exactly which pages aren’t being served from cache so you can fix it.
• Self-healing cache. Automatically recovers from cache issues without manual intervention.
• Plugin-conflict auto-resolution. Reduces the manual troubleshooting needed when another plugin interferes with caching.
• Critical CSS. Load only the CSS needed for above-the-fold content first, improving perceived load speed.
• Cloudflare APO and edge cache settings. Serve your cached HTML from Cloudflare’s edge and set the zone’s cache level and browser TTL. APO also needs a paid Cloudflare plan.

Where the line falls, for the settings people ask about most:

Free is the complete toolkit and it stays free. Pro is the layer that runs it for you, across 46 modules in total.

xSpeed Pro is available on Personal, Business, Agency, and Enterprise plans: yearly ($29, $49, $99, $199 per year) or as a one-time lifetime licence ($79, $149, $249, $399, founding pricing), so you can pick the tier that matches the number of sites and level of support you need. Every plan carries a 14-day money-back guarantee. To see exactly where the line falls, our free and Pro breakdown marks each feature by tier, and the 80-capability comparison puts the same marks against eight rival plugins.

Running more than one site

One site is a settings page you visit twice. Fifteen client sites is a job nobody wants, because the settings drift and no one notices until a client asks why their store got slower.

xSpeed Hub is ours too, and it reports cache status, hit ratio and cached-page counts for every connected site from one place, then applies a single policy across all of them. If you run a WooCommerce store, optimizing your checkout page covers the pages that must stay out of the cache and how to make everything around them fast.

Wrapping Up

Getting started with xSpeed Cache takes just a few minutes: install and activate the plugin, run the setup wizard to switch page caching on, turn on the free optimizations that fit your site, and confirm the results from outside your server. From there, xSpeed Pro is there if you want deeper insights and more advanced tuning.

What to do this week:

1. Scan your homepage before you install anything, and write the number down.
2. Install and activate xSpeed Cache, apply the Conservative preset in the setup wizard (page cache and GZIP only), then scan again.
3. Turn on minification and lazy load, one at a time, reloading the site after each.
4. Enable object caching, and measure a page you cannot page-cache.
5. Scan one real post logged out, and confirm the cache evidence says what you expect.

Ready to speed up your site? Install xSpeed Cache and start with Step 1 today, or see the plans if you already know which tier you need.