xSpeed Cache: AI-Powered Performance Hub with MCP, Caching & CDN

AI-Powered Site Audit (Pro)

xSpeed Pro scans your site and tells you which performance features will help the most, with severity ratings and concrete reasons.

Page Caching

Pages are saved as static HTML files and served before WordPress loads. The cache rebuilds itself when you publish a post, switch themes or update a plugin.

• 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 , /checkout and /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

• 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 under wp-content/uploads keep theirs, so a page-builder or consent-banner edit still reaches returning visitors)
• Safe-minify skips already-minified files and falls back if anything looks off

GZIP Compression

• 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 Images, Videos and Iframes

• Lazy load images, iframes and videos so they load when a visitor scrolls to them
• Adds missing image sizes so the layout does not jump

Font Optimization

• Adds font-display: swap so text is visible immediately while fonts load
• Preloads above-the-fold font files
• Removes the blank-text flash caused by slow Google Fonts responses

Browser Cache

• Sets Cache-Control and Expires headers for images, CSS and JS, with no manual configuration

Cache Preloader

• Sitemap-driven cache warmer, so the first visitor after a purge still gets a fast page
• Auto-warms the cache when you publish or update content

Redis and Memcached Object Cache

• Connect Redis or Memcached in seconds, as a drop-in persistent object cache
• View status and flush the object cache from the dashboard

CDN and Cloudflare

• Pull-zone URL rewriting for any CDN provider
• Cloudflare integration: connect your zone, auto-purge on publish and toggle development mode

Database Cleanup

• Optimize database tables
• Remove post revisions, spam, trash, transients and orphaned meta
• Schedule automatic cleanup

Built to Handle WordPress Edge Cases

• Multisite ready. Each site in the network gets its own cache and settings.
• LiteSpeed server? xSpeed Cache also clears the server’s LiteSpeed cache whenever it clears its own. If the LiteSpeed Cache plugin is active, xSpeed Cache will not turn on its own page cache or the other features that overlap, so the two never run at once.
• WooCommerce? Logged-in customers and checkout pages are never cached.
• WordPress Site Health. xSpeed Cache adds its own check under Tools → Site Health.
• Works on any server. Apache, nginx, LiteSpeed, IIS and any standard PHP host.

Designed for Everyone

Non-technical users: A 3-step setup wizard configures the plugin in under 2 minutes. Settings save automatically.

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 stores no IP addresses and sets no tracking cookies. Out of the box, the only request it makes is a check to your own site’s home URL to confirm GZIP is active, at most once an hour.

Usage analytics is optional and off by default. If you turn it on in the setup wizard or in xSpeed Cache → Settings → Privacy & usage data, it sends your email address and display name, your site’s setup and which xSpeed Cache features you use. Page content is never sent. See the External services section below for every service the plugin can contact.

If xSpeed Cache makes your site faster, please leave a review on WordPress.org.

External services

Out of the box, xSpeed Cache contacts only your own site (the gzip probe below). Every other service on this list runs only after an administrator turns it on, connects it or presses a button. None of them runs on a fresh install.

Usage analytics is off by default. The setup wizard shows it as an unticked switch, and xSpeed Cache → Settings → Privacy & usage data has the same switch. Nothing is sent until you turn it on. Turning it off stops all sending and clears the scheduled send. The deactivation survey is separate and sends nothing unless you click Submit. Speed tests and xSpeed Scan run only when you press Test or Scan, never on a schedule.

Self-hosted gzip probe

• What it does: Sends one GET request with Accept-Encoding: gzip to your site’s home URL, to see whether your server already gzips responses. Only the Content-Encoding header is read.
• When it runs: When the dashboard loads server status, at most once an hour.
• Where the request goes: Your own site. Nothing is sent anywhere else.

Third-party files (hosts you list)

• What it does: Downloads CSS and JavaScript files from other hosts and keeps a copy on your site, so visitors load the copy.
• When it runs: Only after an administrator turns on xSpeed Cache → Optimization → Third-party files. It is off by default. After that, a file is downloaded a minute or so after a page that uses it is first built, and checked again every 7 days (you can change this).
• Where the requests go: Only to the hosts on the list in that screen, which starts with cdnjs.cloudflare.com, cdn.jsdelivr.net, unpkg.com, code.jquery.com, ajax.googleapis.com, use.fontawesome.com, maxcdn.bootstrapcdn.com, stackpath.bootstrapcdn.com and cdn.datatables.net. A host you remove from the list is never contacted. An empty list contacts nobody.
• What is sent: A plain GET for the file, with no cookies, no site address and no visitor data.
• Limits: HTTPS only, files up to 1 MB by default, and CSS or JavaScript only.

xSpeed Hub (app.xspeedcache.com)

• What it does: Lets you manage this site, with other sites, from one xSpeed Hub account and one AI connection.
• When it runs: Only after an administrator connects the site to xSpeed Hub from xSpeed Cache → AI & agents. A site that was never connected makes no Hub requests.
• What is sent: The site URL and this site’s MCP token, which the Hub uses to call the site’s own MCP endpoint. The token is sent when the site is connected, when the connection status is checked, when the token changes (Rotate, or Connect after Disconnect), when you disconnect, and with speed-test requests you start.
• After an xSpeed Scan: When a scan you run from the plugin finishes on a connected site, the site sends the Hub that scan’s id, so the Hub can compare it with the site’s earlier scans. Only the id and the site URL are sent. The Hub reads the report from the scan service itself.
• Where the request goes: app.xspeedcache.com, operated by WPDeveloper.
• The broker URL: The AI & agents screen also shows an api.xspeedcache.com address that you can paste into an AI client. The plugin never contacts that address. Only your AI client does, and only if you set it up that way.
• Terms and privacy: Terms , Privacy .

Usage analytics and deactivation survey (send.wpinsight.com)

• What it does: Tells WPDeveloper which WordPress setups and xSpeed features are in use, so we can fix what breaks.
• When it runs: Only after an administrator turns on “Share usage data” in the setup wizard or in Settings → Privacy & usage data. It sends once a day, and once more when the plugin is deactivated.
• What is sent: The site URL and name, WordPress and PHP versions, site language, charset, text direction, multisite status, server software, active and inactive plugins, theme name and version, the xSpeed version and xSpeed’s own settings. The send when you turn the switch on, and the one at deactivation, also include the email address and display name of the administrator who did it. The daily se