xSpeed Cache: AI-Powered Performance Hub with MCP, Caching & CDN
Active Installs
8,000+
Last Updated
September 22, 2026
First Released
May 27, 2026
Download History (Last one month)
Contributors
Your visitors decide to stay or leave in under 3 seconds. xSpeed Cache makes sure they stay.
Most caching plugins bury you in settings, charts and upgrade popups. xSpeed Cache does the opposite. Install it, flip one switch, and your site loads faster. No bloat, no upsells nagging you, no PhD required.
Built by the team at WPDeveloper, trusted by over 6 million WordPress users worldwide.
What This WordPress Caching Plugin Does
xSpeed Cache is a full-site performance plugin. It caches your pages, shrinks your code, compresses your files and serves everything as fast as your server physically can, including an AI-powered audit that tells you exactly what is slowing your site down.
The result: pages that load in milliseconds, not seconds. Better Google PageSpeed scores. Happier visitors. Better SEO rankings.
If you have been searching for how to speed up WordPress site performance without hiring a developer, this is the shortest path there. It is built to speed up WordPress from the first page load, not after a week of tuning.
The Speed Advantage No Other Free WordPress Cache Plugin Offers
When xSpeed Cache caches a page, it does not just save it. It serves it directly from the server, bypassing PHP entirely.
That means:
- With xSpeed static cache: 5 to 15ms response time
- Without it (PHP-served cache): around 85ms response time
That is up to 17x faster page delivery on cache hits. No other free WordPress cache plugin does this across Apache, nginx and LiteSpeed automatically, which is what makes it worth comparing against any other best WordPress cache plugin shortlist you are working from.
Features at a Glance
AI Assistants and the WordPress MCP Server
xSpeed Cache ships a WordPress MCP server, so a Claude WordPress MCP connection, or any other MCP client, can inspect and tune your site through the same tools the dashboard uses. Every action is bounded by what you allow when you connect, which is what separates a real WordPress MCP plugin from a chatbot bolted onto a settings page.
- MCP server appears on the Overview as a capability card, so an AI connection can be set up without hunting for a panel
- OAuth discovery, with dynamic client registration bounded by stored-client limits, redirect URI limits, name and URI length limits and per-IP rate limiting
- Read-only MCP connections can read status through every per-command tool, while write actions stay refused
- Credentials cannot be written by an AI assistant unless you explicitly grant that permission when connecting
- WP-CLI parity:
wp xspeed purge,wp xspeed preloader status,wp xspeed score run,wp xspeed optimizeandwp xspeed settings list|get|update - The
optimize_sitetool measures the site, applies recommended settings one at a time, re-checks the page after each change and reverts anything that breaks it
Disable Bloat
Turn off WordPress features you do not use. Each one is a request your server does not have to make.
- Disable dashicons on the frontend
- Remove oEmbed, RSS feeds, XML-RPC, jQuery Migrate and REST API authentication headers
AI-Powered Site Audit (Pro)
xSpeed Pro scans your specific site and tells you exactly which performance features will help the most, with severity ratings and concrete reasons rather than generic advice.
Page Caching That Speeds Up Your WordPress Site
Your pages are saved as static HTML files and served instantly to visitors, before WordPress even loads. This is the fastest way to speed up WordPress page delivery, and the cache rebuilds itself automatically whenever you publish a post, switch themes or update a plugin. You never have to think about it.
- Static-file rewrite path that bypasses PHP entirely for a 5 to 15ms TTFB
- Auto-purge on publish, update, comment and theme change
- One-click cache purge from the admin bar
- Exclude specific URLs such as
/cart,/checkoutand/my-account - Set your own cache expiry, from 1 to 720 hours
- Separate mobile cache for phone and tablet visitors
- Per-post cache rules with custom expiry, or disable caching for individual posts
Code Minification for WordPress Page Speed Optimization
Strips all the unnecessary whitespace, comments and characters from your HTML, CSS and JavaScript without breaking anything. Smaller files are one of the most reliable WordPress page speed optimization wins available.
- Minify HTML, CSS and JavaScript
- Combine CSS and JS files to reduce HTTP requests
- Defer or delay JavaScript so it does not block page rendering
- Async CSS loading
- Removes
?ver=query strings from asset URLs (generated files underwp-content/uploadskeep theirs, so a page-builder or consent-banner edit still reaches returning visitors) - Safe-minify automatically skips already-minified files and falls back if anything looks off
GZIP Compression
Makes every file your server sends smaller, so browsers download them faster.
- Auto-configures GZIP on Apache and LiteSpeed
- Shows a ready-to-paste config snippet for nginx and IIS
- Detects if your server already has GZIP active, so there is no double-configuration
Lazy Load WordPress Images, Videos and Iframes
Lazy load WordPress media so images, videos and iframes load only when a visitor scrolls to them, rather than all at once on page load.
- Lazy load images, iframes and videos
- Automatic Cumulative Layout Shift fix so your layout does not jump
Font Optimization for WordPress Core Web Vitals
Web fonts are one of the most common causes of slow-loading pages, and fixing them is one of the easiest ways to increase WordPress page speed. Together with lazy loading and the LCP preload, this is practical core web vitals optimization rather than a score-chasing trick.
- Adds
font-display: swapso text is visible immediately while fonts load - Preloads above-the-fold font files for instant rendering
- Removes the blank-text flash caused by slow Google Fonts responses
Browser Cache
Tells browsers to remember your static files such as images, CSS and JS, so returning visitors load your site even faster.
- Sets proper
Cache-ControlandExpiresheaders - Works automatically with no manual configuration needed
Cache Preloader
Warms up your cache automatically so the very first visitor after a purge still gets a fast page.
- Sitemap-driven cache warmer
- Auto-warms cache when you publish or update content
Redis Object Cache for WordPress (Redis and Memcached)
Speed up database-heavy installs with a persistent object cache WordPress can rely on between requests. Set up Redis object cache WordPress support, or Memcached, in seconds and keep every repeated query in memory.
- Connect Redis or Memcached in seconds
- View status and flush the object cache from the dashboard
- Works as a drop-in persistent object cache, so object cache WordPress lookups are not repeated on every page load
WordPress CDN Plugin Support with Cloudflare Integration
Serve your static files from a WordPress CDN for faster global delivery. Point it at whichever provider you already use, including a WordPress CDN free tier, so you are not locked into one network while you decide which is the best WordPress CDN for your traffic.
- Pull-zone URL rewriting for any CDN provider
- Built-in Cloudflare WordPress CDN integration: connect your zone, auto-purge on publish and toggle development mode
- Works as a WordPress CDN plugin for any pull zone, with no separate connector to install
WordPress Database Cleanup and Optimization
A bloated database slows down every page load. This WordPress database cleanup plugin keeps yours clean and helps speed up WordPress database queries without a separate tool.
- Optimize database tables
- Remove post revisions, spam, trash, transients and orphaned meta
- Schedule automatic cleanup so it runs on autopilot
Built to Handle WordPress Edge Cases
xSpeed Cache handles the edge cases other plugins miss:
- Multisite ready. Each site in the network gets its own cache and settings.
- LiteSpeed server? xSpeed Cache detects the LiteSpeed Cache server module and steps back to avoid conflicts.
- WooCommerce? Logged-in customers and checkout pages are never cached.
- WordPress Site Health. xSpeed Cache adds its own health check under Tools then Site Health, so you always know your cache config is working correctly.
- Works on any server. Apache, nginx, LiteSpeed, IIS and any standard PHP host.
Designed for Everyone
Non-technical users: A 3-step setup wizard walks you through first-time configuration in under 2 minutes. Settings auto-save, so there is no Save button to forget.
Developers: REST API at /wp-json/xspeed/v1/, developer filters (xspeed_skip_minify, xspeed_strip_asset_version, xspeed_cache_skip_for_post, xspeed_cache_expiry_for_post), WP_DEBUG awareness, and a React 18 and TypeScript admin UI.
Agencies: Use the xspeed_branding filter to white-label the dashboard for clients.
Private By Default
xSpeed Cache never collects personal data, stores IP addresses or uses tracking cookies. Every optimization runs locally on your server. By default it makes no calls to any third-party server. The only request is a quick check to your own site’s home URL to confirm GZIP is active, rate-limited to once per hour.
xSpeed Cache also includes optional usage analytics. You are asked in two places: a clearly labeled consent control in the setup wizard, and the switch in xSpeed Cache Settings Privacy & usage data. Nothing is sent until you confirm from one of them. When enabled, xSpeed Cache shares non-sensitive diagnostics: your WordPress and PHP version, active theme and plugins, server type, site language, and which xSpeed Cache features you have switched on, so we know what to keep fast and compatible. No page content is ever sent, and you can turn it off again at any time from xSpeed Cache Settings Privacy & usage data. See the External services section below.
Backed By a Team You Trust
xSpeed Cache is developed by the trusted team at WPDeveloper, a leading WordPress marketplace used and loved by millions of users.
Loved xSpeed Cache?
If xSpeed Cache makes your site faster, please leave a review on WordPress.org. It really helps.
External services
xSpeed Cache contacts your own site (the gzip probe below); when usage analytics is enabled, an analytics service; only if you choose to submit the optional deactivation survey, that same service; and — only when you run a speed test yourself — one external performance-score provider. Analytics consent is asked in two places — a clearly-labeled control in the setup wizard, and the switch in xSpeed Cache Settings Privacy & usage data — and nothing is sent until you confirm from one of them; turning the switch off stops all collection and clears the scheduled send. The deactivation survey is separate and never sends anything unless you explicitly click Submit. External scores are off by default, turn on the first time you press Test, and never run on their own.
Self-hosted gzip probe
- What it does: Issues a single
GETrequest to your site’s home URL (home_url('/')) with anAccept-Encoding: gzipheader to detect whether your web server is already serving gzipped responses. The response body is discarded; only theContent-Encodingheader is read. - When it runs: On demand when the admin dashboard loads server status, throttled to once per hour via a transient (
xspeed_gzip_active). - Where the request goes: Your own site (
home_url()). This request goes only to your own server. - What is sent: No personal data, no site identifiers, no payload — just a standard HTTP
GETfrom your server back to your server.
Third-party libraries
This plugin bundles the following GPL-compatible third-party libraries:
matthiasmullie/minify
Used for CSS and JavaScript minification.
- Source: https://github.com/matthiasmullie/minify
- License: MIT
matthiasmullie/path-converter
Dependency of matthiasmullie/minify.
- Source: https://github.com/matthiasmullie/path-converter
- License: MIT
React / React DOM / Scheduler
Used for the xSpeed Cache admin interface bundle.
- Source: https://github.com/facebook/react
- License: MIT
lucide-react
Used for admin interface icons.
- Source: https://github.com/lucide-icons/lucide
- License: ISC
- Upload the
xspeedfolder to the/wp-content/plugins/directory, or install the plugin through the WordPress Plugins screen directly. - Activate the plugin through the Plugins screen in WordPress.
- Open xSpeed Cache from the admin menu. The 3-step setup wizard walks you through first-time configuration in under 2 minutes.
- Settings auto-save, so there is no Save button to forget.
Screenshot Gallery
Yes. xSpeed Cache works on Apache, nginx, LiteSpeed, IIS and any standard PHP host. GZIP auto-configures on Apache and LiteSpeed, and a ready-to-paste config snippet is provided for nginx and IIS.
No. xSpeed Cache detects the LiteSpeed Cache server module and steps back to avoid conflicts.
Yes. Logged-in customers and checkout pages are never cached, and you can exclude specific URLs such as /cart, /checkout and /my-account.
Yes. Each site in the network gets its own cache and settings.
Not exactly. A WordPress MCP adapter usually exposes core WordPress data. The xSpeed Cache MCP server exposes the performance tools this plugin owns, such as cache purging, preloader status, score runs and settings reads and writes, so an assistant works on speed rather than on content.
Yes. A WordPress MCP Claude connection uses OAuth discovery, and the MCP server appears on the Overview as a capability card so you can set it up without hunting for a panel. Read-only connections stay read-only.
That is for you to judge, but here is the honest basis for comparison. The static-file rewrite path serves cached pages before PHP loads, across Apache, nginx and LiteSpeed, which most free plugins do not do. Object caching, CDN support and database cleanup are included rather than reserved for a paid tier.
In most cases yes. Page caching, minification, GZIP, lazy loading, font optimization, browser caching, object caching, WordPress CDN support and database cleanup are all in one plugin, so you are not stacking a WordPress page speed plugin on top of a cache plugin on top of a database tool.
It targets the parts a plugin can influence. The static cache improves server response time, the LCP preload picks the largest image on the page rather than the first, lazy loading defers offscreen media, and the automatic Cumulative Layout Shift fix stops the layout jumping. Page weight and DOM size are reported to you, since only a person can fix those.
The MCP server lets an AI assistant connect to your site and use the same tools the dashboard uses, such as purging cache, checking preloader status, running a score and reading or updating settings. Read-only connections stay read-only, and credentials cannot be written unless you explicitly grant that permission when connecting.
Very unlikely. xSpeed Cache includes safety checks for every optimization: minification falls back to the original if anything looks off, and the cache bypasses logged-in users, admin pages, AJAX and REST requests automatically. If something ever looks wrong, you can toggle any feature off individually.
Click Purge in the xSpeed Cache dashboard, or use Purge xSpeed Cache in your admin bar. The cache also clears itself automatically whenever you publish or update content.
Yes. The built-in Cloudflare module connects your zone and auto-purges Cloudflare’s cache whenever xSpeed Cache purges its own, so both caches stay in sync.
Yes. Either toggle the option off in the admin UI, enable WP_DEBUG (xSpeed Cache automatically skips HTML minification when debug is on), or use the xspeed_skip_minify filter.
By default, no. The only request is a check to your own site’s home URL to confirm GZIP is active. Usage analytics and external performance scores are covered in detail in the External services section.
Changelog
[1.3.5] – 2026-09-22
Consent banners now survive Delay JS on every site that ships one, Turbo Render works on any theme rather than only Elementor, JS-injected YouTube/Vimeo embeds load only on click, and nginx sites are no longer told to fix a configuration that was already correct.
Media:
– New: YouTube and Vimeo players that a theme or plugin injects with JavaScript after page load now get the same click-to-load facade as regular embeds, so no player code loads until a visitor presses play.
Optimization:
– New: Turbo Render works on any theme or page builder. It recognises Divi, Bricks, Oxygen and Beaver Builder sections directly, and where no builder is recognised it falls back to the page’s own structure, so the feature is no longer inert outside Elementor.
– Improved: Turbo Render is the new name for the feature previously called Render Skip — the same mechanism, named for what the visitor gets rather than what the browser postpones.
– Fixed: Consent banners from Cookie Notice, Moove, Termly, Usercentrics, Iubenda, OneTrust, Borlabs, Real Cookie Banner and SureCookie are never delayed, so a visitor is always offered the choice before leaving.
– Fixed: Complianz and NotificationX banners stay protected even when another plugin strips the id WordPress prints on their script.
– Fixed: An author’s data-no-optimize, nowprocket or similar opt-out is now read as an attribute rather than matched anywhere in the tag, so a script is neither wrongly delayed nor wrongly skipped because the marker appeared in a URL, a class or a neighbouring inline block.
– Fixed: A script you name yourself in the Delay JS target list is now delayed even when it is a consent banner — the built-in banner protection yields to an explicit choice.
Health:
– Fixed: nginx sites with a working configuration are no longer told to paste in a server snippet they already have. Site Health and the dashboard now reach the same verdict, and a check that cannot conclude says so instead of warning.
Preloader:
– Fixed: Cache warming no longer identifies itself in a way that common firewall rule sets block, so newly published posts are warmed again on sites running 7G/8G-style protection.
[1.3.4] – 2026-09-20
Consent-manager scripts marked late are now always left alone, below-fold sections skip rendering work until they are needed, and xSpeed’s MCP server shares a site cleanly with other MCP plugins.
Optimization:
– New: Below-fold sections are rendered lazily with content-visibility: auto, so the browser skips their layout and paint work until they scroll into view.
– New: Block-editor stylesheets are stripped from anonymous frontend pages that do not use any blocks.
– Fixed: Scripts that another plugin marks data-no-optimize or data-no-minify late — as consent managers such as Borlabs Cookie do — are restored to their original URL and left alone by minify, defer and delay, however late the marker is stamped.
AI / MCP:
– Improved: The AI & agents screen now leads with the MCP server and says what each of its tools does, with descriptions shown in full.
– Improved: An assistant already connected over OAuth may ask for approval once more after updating — nothing needs re-entering, and read-only connections stay read-only.
– Fixed: An AI assistant can now connect to xSpeed and to another MCP plugin on the same site. xSpeed’s OAuth details moved to an address of their own under /xspeed/mcp, and the site-wide address is handed over as soon as another plugin asks for it — where nothing else wants it, xSpeed keeps answering there.
Dashboard & Admin UX:
– Fixed: Buttons can carry a border and always show keyboard focus, and the Cloudflare Dev-mode controls use proper button styling.
[1.3.3] – 2026-09-16
Consent gets a dashboard home, the cache engine learns to leave non-HTML alone, and uncacheable pages now tell the CDN so.
Privacy & Analytics:
– New: A “Privacy & usage data” panel to view and withdraw usage-analytics consent any time, with a matching wp xspeed privacy command.
– Improved: The setup wizard’s analytics consent now defaults to off and is only ever an explicit opt-in.
Caching:
– Fixed: WordPress’s virtual robots.txt (and favicon) is no longer cached or minified, so every directive and newline reaches crawlers intact.
– Improved: /robots.txt joined the default cache exclusions, and the sitemap pattern now matches sitemaps.xml too — existing installs keep their working exclusion through the rename.
Cloudflare & CDN:
– New: A page xSpeed refuses to cache now sends no-store edge headers, so a CDN never freezes a half-optimized or excluded page.
– Fixed: The deferred Cloudflare purge batch is bounded, cleared on deactivation, and says so when a purge is refused.
Optimization:
– Fixed: Scripts marked data-no-optimize or data-no-minify are left completely alone by minify, defer and delay — consent-manager configurations always ship current.
– Fixed: xSpeed’s own scripts are never deferred or delayed by its own optimizer.
– Fixed: The Conservative preset now switches LCP preload and preconnect off, matching its “page cache + GZIP only” promise.
Dashboard & Admin UX:
– Improved: Preload now reports what actually happened — how many pages are warming, and the server’s reason when a crawl cannot start.
Reliability:
– Improved: Uninstall now removes all usage-tracking state, the scheduled send, and every leftover option row.
Older releases are listed in changelog.txt, included with the plugin, and at xspeedcache.com/changelog.
" width="120" height="120">
Available Versions
| Version | Download | Type |
|---|---|---|
| 1.3.5 | Download | Stable |
| 1.3.4 | Download | Stable |
| 1.3.3 | Download | Stable |
| 1.3.2 | Download | Stable |
| 1.3.1 | Download | Stable |
| 1.3.0 | Download | Stable |
| 1.2.4 | Download | Stable |
| 1.2.3 | Download | Stable |
| 1.2.2 | Download | Stable |
| 1.2.1 | Download | Stable |
| 1.2.0 | Download | Stable |
| 1.1.8 | Download | Stable |
| 1.1.7 | Download | Stable |
| 1.1.6 | Download | Stable |
| 1.1.5 | Download | Stable |
| 1.1.4 | Download | Stable |
| 1.1.3 | Download | Stable |
| 1.1.2 | Download | Stable |
| 1.1.1 | Download | Stable |
| 1.1.0 | Download | Stable |
| 1.0.9 | Download | Stable |
| 1.0.8 | Download | Stable |
| 1.0.7 | Download | Stable |
| 1.0.6 | Download | Stable |
| 1.0.5 | Download | Stable |
| 1.0.4 | Download | Stable |
| 1.0.3 | Download | Stable |
| 1.0.2 | Download | Stable |
| 1.0.1 | Download | Stable |
| 1.0.0 | Download | Stable |
| Development | Download | Trunk |
