# What's New in xSpeed Cache Free v1.4.1 and Pro v1.3.1 > xSpeed Cache Pro v1.3.1 and Free v1.4.1 add Cloudflare Enterprise: whole pages served from Cloudflare's edge, four-step setup, no Cloudflare account needed. - Published: 2026-10-11 - Updated: 2026-10-11 - Author: Abdur Rahman Emon - Tags: Release Notes, Cloudflare, CDN, xSpeed Cache, Product Updates - Canonical: https://xspeedcache.com/blog/whats-new-in-xspeed-cache-free-1-4-1-and-pro-1-3-1/ --- How far is your server from your visitors? A good page cache makes WordPress fast, but every visitor still has to reach your server to get a page. For someone on the other side of the world, that round trip alone can cost more time than the cache saves. xSpeed Cache Free v1.4.1 and Pro v1.3.1 change that with **Cloudflare Enterprise**, a new add-on that puts your whole site on Cloudflare's enterprise network. Most visitors are served a copy of your page from a Cloudflare location near them and never reach your server at all. You set it up from one panel in wp-admin, and you don't need a Cloudflare account. This post covers what Cloudflare Enterprise is, how setup works, what it costs, and everything else that shipped in Free v1.4.0 and v1.4.1 and Pro v1.3.0 and v1.3.1, released on 7 and 8 October 2026. ## What is Cloudflare Enterprise in xSpeed Cache? **Cloudflare Enterprise is an add-on that serves and purges your whole site from Cloudflare's enterprise edge, managed entirely from xSpeed Cache.** It is different from the Cloudflare integration xSpeed Cache already had. That integration connects *your own* Cloudflare account so xSpeed Cache can clear its cache. The add-on needs no account at all: the plugin arranges the Cloudflare side, and all you do is add a few DNS records. The add-on is a licence key, not a second plugin. It runs inside xSpeed Cache Pro, so there is nothing else to download or install. ![Where your pages come from: without Cloudflare Enterprise every page request travels to your server; with it, most requests are answered by a Cloudflare edge near the visitor, and your server is asked only for a fresh copy](https://xspeedcache.com/images/blog/xspeed-cfe-release-flow.webp) ## Why it matters - **Pages load from near your visitors.** Cloudflare holds whole pages, not just images and scripts, so a visitor in Sydney or São Paulo gets your page from a nearby location instead of waiting on your server. - **No Cloudflare account and no Cloudflare bill.** The add-on covers the Cloudflare side. There is nothing to sign up for and nothing extra to pay Cloudflare. - **The edge follows your own cache rules.** Cloudflare keeps a page for as long as your Page Cache expiry says, and the pages you exclude in xSpeed Cache are the pages Cloudflare never stores. There is no second set of rules to maintain. - **Purging stays in sync on its own.** Publishing or updating a post clears those pages on Cloudflare as well as on your server, and Purge All clears both. - **Enterprise features come included.** Every domain gets Always Online, Tiered Cache, HTTP/3, Brotli and automatic HTTPS rewrites, plus switches for a managed firewall (WAF), rate limiting, AI crawler blocking and more. ## How does it work? ### 1. Activate two licence keys Cloudflare Enterprise needs two licences on the same site: **xSpeed Cache Pro** and the **Cloudflare Enterprise Add-on**. Both keys go on one page, **xSpeed Cache → Settings → License**, and both are in your WPDeveloper account. Once the add-on key is active, the Cloudflare Enterprise page opens on its own and confirms the licence. If your copy of Pro is older than v1.3.0, the panel asks you to update Pro first. You'll find the panel under **xSpeed Cache → Network → Cloudflare Enterprise**. ### 2. Run the four-step setup Setup runs in four steps: **Setup, Verify, Connect and Done**. Each step opens only when the one before it is finished, with one short instruction, the records to add and a status line that checks on its own. ![Cloudflare Enterprise setup in four steps: Setup checks your domain, Verify adds a TXT and a CNAME record, Connect points your domain at Cloudflare, and Done confirms it is active, SSL ready and connected. About 15 minutes of work plus up to an hour for DNS](https://xspeedcache.com/images/blog/xspeed-cfe-release-setup.webp) - **Setup.** The panel checks your domain first: that it's online, that it isn't already running through a Cloudflare account, and that it works over HTTPS. These checks only look; they change nothing. - **Verify.** You add two DNS records, a TXT record that proves you own the domain and a CNAME that lets Cloudflare issue your SSL certificate. Visitors aren't affected by either. - **Connect.** You point your domain at Cloudflare, using a CNAME or A records, whichever your DNS provider supports. The panel records what your DNS pointed at before the switch, in case you ever want to move back. - **Done.** The panel confirms three things: Cloudflare Enterprise is active, SSL is ready, and your site is connected. Every DNS record has its own card with a Copy button beside each value, so there's no retyping. Plan on about 15 minutes of work plus up to an hour for DNS to spread. You can close the page at any point; setup carries on by itself and reopens where you left off. ### 3. Let purging run itself Once your domain is live, purging needs no attention. A post save, Purge All and a manual purge all reach Cloudflare. If Cloudflare can't take a purge right away, xSpeed Cache keeps it and retries, and purges triggered by visitor activity are sent at most once every 10 seconds, so a busy site doesn't flood the edge. While Cloudflare Enterprise is on, xSpeed Cache's CDN module and any second Cloudflare proxy stand down, so two layers never fight over the same pages. ### 4. Tune the edge and watch your usage The panel has six tabs: Performance, Security, Advanced, Domain, DNS and Danger zone. From there you can switch on Early Hints, image optimization at the edge, the WAF, rate limiting, Under Attack mode and AI crawler blocking, all saved straight to Cloudflare. The Domain tab gives a plain verdict on whether Cloudflare is serving your site, along with your certificate, this month's usage and the last purge. The usage line turns amber at 80% and red at 90% of your allowance, so the warning arrives while there's still room to act. ## Already hosting on xCloud? If your site is hosted on xCloud and you bought Cloudflare Enterprise there, you don't need the add-on. xSpeed Cache recognises it: the panel reads **Cloudflare Enterprise is managed by xCloud**, and every purge, from the dashboard, WP-CLI or cron, goes through xCloud's own purge plugin. Purge All sends one whole-domain purge. The add-on offer is also hidden on these sites, since your host already provides it. ## What it costs
What you needCost
xSpeed Cache Pro licenceRequired
Cloudflare Enterprise Add-on$5 per domain, per month
A Cloudflare accountNot needed
A Cloudflare billNone
The add-on page in your dashboard always shows the current price as the service reports it, and the Get it button on the sidebar card opens that page right inside wp-admin. ## Everything else in this release Cloudflare Enterprise is the headline, but these four releases carry plenty more. ![Also in this release. Free v1.4.0 and v1.4.1: smarter purging, forms keep working, non-Latin URLs and mobile preloading. Pro v1.3.0 and v1.3.1: the Cloudflare Enterprise add-on, four-step setup, per-device hero preload and smarter warming](https://xspeedcache.com/images/blog/xspeed-cfe-release-highlights.webp) ### Smarter purging (Free) - **Saving a post clears only the pages it changes:** the post itself, its archives and the listing pages that show it. The whole cache is cleared only when the change reaches something every page draws on, such as a menu or a Recent Posts widget, and the purge log says why. - **Opening wp-admin no longer empties the page cache and the edge.** - **WooCommerce updates purge once,** and a stock change purges its pages in a single batch. - **Content and site purges no longer delete minified CSS and JS files.** ### Better edge behaviour (Free and Pro) - **Forms on cached pages keep working.** The edge never keeps a page longer than the page's own lifetime, so forms stop failing when their security token expires. - **Tracking parameters stay off the edge.** Pages served for addresses with parameters such as `?utm_source=` are no longer stored at the edge, where a purge couldn't reach them. - **A new Health check** warns if Cloudflare stores pages that were marked do-not-store, such as cart and checkout pages. ### Media, preloading and more - **Non-Latin URLs cache correctly.** Pages with Chinese, Arabic or other non-Latin slugs each get their own cache entry and purge reliably. - **The preloader warms the mobile copy too** when Separate Mobile Cache is on, and in Pro a page counts as warm only once its phone copy is cached. - **Autoplay videos can start after the page has loaded.** Off by default. - **Hero images are preloaded per device** in Pro, using the image the rendering service actually measured. - **Connect a site from xSpeed Hub** through a consent page in wp-admin. ## How to update Go to **Dashboard → Updates** or **Plugins** in WordPress and update both xSpeed Cache and xSpeed Cache Pro. Cloudflare Enterprise needs Pro v1.3.0 or later, and the four-step setup arrives in Pro v1.3.1, so update both plugins together. ## Frequently asked questions ### Do I need a Cloudflare account? No. The add-on covers the Cloudflare side completely. You never create a Cloudflare account and there is no Cloudflare bill. If your domain's DNS already lives in your own Cloudflare account, set the new records to DNS only (the grey cloud) and turn off Universal SSL for the domain, as the setup guide explains. ### Is this the same as the existing Cloudflare integration? No. The existing integration connects your own Cloudflare account so xSpeed Cache can clear its cache. Cloudflare Enterprise puts your whole site on Cloudflare's enterprise network and serves pages from the edge, with no account of your own. ### Does it work on multisite? Yes. How it works depends on how your network is set up: - **Subdomains or mapped domains** (`shop.example.com`, `shop-brand.com`): each subsite has its own domain, so each one can be put on Cloudflare Enterprise separately. Each domain counts as one domain on your add-on licence. - **Subdirectories** (`example.com/shop`): every subsite shares the main site’s domain, so the main site sets it up once. Each subsite can see the status and purge its own pages. Only a network admin can set up, change or remove a domain, because it changes DNS for the network. ### Can I turn it off later? Yes. Point your DNS records back at your own server (the panel lists what they were), wait for the change to spread, then remove the domain from the Danger zone tab. Turning the module off purges the edge, and your add-on licence is kept, so you can come back later without buying again. ## Wrapping up Free v1.4.1 and Pro v1.3.1 take xSpeed Cache past your server and onto Cloudflare's enterprise edge, with a four-step setup, purging that keeps itself in sync and no Cloudflare account to manage. Update both plugins, and you'll find Cloudflare Enterprise waiting under Network. [Set up Cloudflare Enterprise](https://xspeedcache.com/docs/cloudflare-enterprise/)