NEWPlugin intelligence: see which plugins each page really uses

A faster WordPress,
checkout untouched.

WPCacheX serves your pages before WordPress loads, keeps Cloudflare, Varnish and Redis in step, and optimizes CSS, JavaScript and images on your own server, testing every risky change on your key pages first.

Get WPCacheXSee how it works
✓ Every feature in every plan✓ Signed auto-updates✓ WordPress 6.6+ · PHP 7.4+
Page views, last 24 hours
0%100%
0%
Served from cache
91%
From cache
6%
Built
3%
Bypassed
Next step: test Critical CSS on your key pages
RequestsLive
0 pages served today
91%
From cache
6%
Built
3%
Bypassed
Recent requestsHow it works
/product/oak-desk/
20 ms · from the page cache
From cache
/shop/linen-shirt/
12 ms · from the page cache
From cache
/blog/spring-sale/
700 ms · built, now cached
Built
0 ms
Answer from cache
640 ms built
0.0 GB
Saved by WebP & AVIF
0 images
0 of 12
Key pages unchanged
Tested

An example site. On yours, every number is counted on your own server.

Works withWooCommerceElementorCloudflareVarnishNginxLiteSpeedRedisCloudPanel

See every layer.
Change nothing blind.

What each cache layer is doing, what a change would do before you make it, and what your visitors really got, in plain language.

Page cache
Served before WordPress loads
Active
Cloudflare
Edge HTML, purged in step
Connected
Redis
Database queries kept in memory
Connected

Every cache layer,
in step

Page cache, Cloudflare, Varnish, Nginx and Redis purge together: a change clears exactly the pages that showed it, at every layer, and preloads them again.

Testing: Delay JavaScriptNot applied yet
0 of 12key pages compared
Rendering at desktop size0%
HM
/ (home)
desktop · phone
Rendering
CO
/checkout/
desktop · phone
Rendering
CT
/contact/
form renders later on phone
Rendering

Tested on your key pages

Before a risky switch, your key pages, checkout included, are rendered with and without it at desktop and phone sizes and compared: errors, layout, styles and fonts. Nothing changes until you apply it.

Measured.
Not estimated.

Hit rate, answer times and savings are counted on your server from real requests, and key pages are measured every day, so a slowdown shows up with the change that came before it.

Served from cache
Last 7 days
04.8k9.6k14kMonTueWedThuFriSatSun
Sun · 12,480 from cache

One plugin.
Every layer of WordPress speed.

Replace a stack of cache, image and optimization plugins with one that knows what the others do. WPCacheX recognises more than twenty of them and asks which should own each job, so nothing runs twice.

Page cache, served before WordPress

Each page is built once and served before WordPress loads; on Apache and LiteSpeed, straight from the web server without starting PHP. Carts, checkout, accounts and signed-in visitors are never cached.

Cloudflare, Varnish, Nginx & Redis

Every purge reaches every layer at once. Cloudflare can cache your HTML at the edge with rules that never share a personal page, visitors' real IP addresses are restored, and Redis keeps database queries in memory.

Precise purge with cache tags

A change purges exactly the cached pages that showed it, at every cache layer, then preloads them. Menus, Elementor templates and block-theme templates no longer empty the whole cache.

CSS, JavaScript & fonts

Critical CSS or Remove unused CSS, worked out on your own server. Scripts that can wait load on the first interaction, and the tap that started it still works. Google Fonts in one request, or hosted on your site.

WebP & AVIF images

Copies made on your own server with the originals untouched, served with a fallback where one is needed, and lazy loading that never delays the main image. Camera data is left out unless you keep it.

Plugin intelligence

WPCacheX visits your pages as a visitor would and shows which plugins each page really uses. Unload a plugin's files where it is unused, or leave it out of those pages entirely so its code never runs there.

Tested on your key pages

Before a risky change, your key pages, checkout included, are rendered with and without it at desktop and phone sizes and compared: errors, layout, styles and fonts. Nothing changes until you apply it.

Analytics & performance history

Hit rate, answer times, bandwidth and image savings, counted on your server from real requests. Key pages are measured every day, and a slowdown is reported with the changes that came before it.

Remote management

Purge, preload, scan or check any connected site, or every site at once, from your wpcachex.com dashboard. Requests are signed and single-use, logged on the site, and its owner can switch them off.

Signed updates

Plugin updates nobody else can forge.

Supply-chain attacks spread through hijacked plugin updates. A WPCacheX install trusts exactly one thing: the Ed25519 public key compiled into it. Pick an attack and watch where it's stopped.

1
TLS channel
Certificate verification, never disabled
Checking
2
Compiled-in key
Only one public key is trusted
3
Ed25519 signature
Over the exact manifest bytes
4
Freshness
Manifest must be under 30 days old
5
Host allowlist
Downloads only from known hosts
6
SHA-384 digest
Package checked before install
7
Newer version
Strictly greater than installed
Verifying the update…
Built to be trusted

WordPress performance, without the guesswork

counted, not estimated

Real numbers only

Every figure in the dashboard is counted on your own server from real requests. Where something cannot be counted, the dashboard says so instead of guessing.

checkout: never cached

Stores stay correct

Carts, checkout and account pages are never cached or optimized, and payment, checkout and consent scripts are never delayed.

1 click

Undo anything

Any settings change can be undone in one click, and Emergency Safe Mode switches every optimization off at once while you troubleshoot.

on your server

Nothing outsourced

Page scans, measurements and image conversions run on your own server. Cloudflare and Google Fonts are contacted only if you connect or choose them.

Pricing

Simple, honest pricing

One licence covers every feature. Pick the number of sites you need — the more you run, the less each one costs.

Plans are being set up. Check back shortly.

In every plan

No feature tiers
Cache
Page cache before WordPress
Cache tags & preload
Cloudflare edge HTML
Varnish, Nginx & Redis
Browser caching
Optimize
Critical & unused CSS
JavaScript delay & defer
Fonts, combined or local
WebP & AVIF images
Lazy loading
Plugin intelligence
Control
Optimization Testing
Analytics & history
Safe Mode & one-click Undo
Remote management
Multisite & WP-CLI
Signed automatic updates

Good to know

No. Every plan includes every feature. The only difference is how many sites you can activate.

No. A new install runs with every feature for 7 days before it needs your licence, so you can set up and test a site first, and use one of your plan's sites on it when you are ready.

The site goes back to plain WordPress: caching and optimizations stop, because a cache that nobody purges would keep serving old prices and stock. Purging and Emergency Safe Mode keep working, and your settings are kept, so everything comes back the moment the licence is active again.

Yes. Release the site from your account dashboard and activate the licence on another one. Your plan sets how many sites can be active at once. A multisite network uses one licence.

Automatically, from a signed manifest. Each package is checked against the Ed25519 key built into the plugin and its SHA-384 digest before it installs.

WordPress 6.6 or newer and PHP 7.4 or newer. Apache, LiteSpeed and Nginx all work; on Apache and LiteSpeed cached pages can be served without starting PHP at all.

Already purchased? Sign in to manage your sites and downloads.

FAQ

WordPress performance questions, answered

WPCacheX is a WordPress performance plugin. It serves cached pages before WordPress loads, keeps Cloudflare, Varnish, Nginx and Redis in step with your content, optimizes CSS, JavaScript and fonts, makes WebP and AVIF copies of your images, and shows which plugins each page really uses. Every change can be tested on your key pages first and undone in one click.

No. Carts, checkout and account pages are never cached or optimized, nor is any visitor with something in the cart or signed in. Payment, checkout and consent scripts are never delayed, and before a risky change you can render your key pages, checkout included, with and without it and compare.

Yes. The editor and previews are never cached or optimized, an Elementor save purges the pages that show it, Elementor's own image loading is respected, and the hero background is preloaded. Elementor's frontend scripts, sliders and sticky headers are never delayed.

They do different jobs, and work best together. Cloudflare serves files from the edge; WPCacheX builds and stores each page once, tells Cloudflare exactly which pages changed so it can purge them, can cache your HTML at the edge with rules that never share a personal page, and restores your visitors' real IP addresses.

You can, area by area. WPCacheX recognises more than twenty of them, among them WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, FlyingPress, NitroPack, Autoptimize, Perfmatters, Imagify and ShortPixel, and asks which one should own page caching, file optimization, images and lazy loading, so two plugins never do the same job. With the Redis Object Cache plugin it works through that plugin instead of replacing it.

WPCacheX visits your pages as a visitor would and records which plugins each page really uses. It can then stop a plugin's CSS and JavaScript loading on pages that do not show it, and, on pages proven not to need it, leave the plugin out entirely so WordPress does not run its code there. Each change is checked page by page first, and a page that fails goes straight back to every plugin.

Yes. Hit rate, answer times, bandwidth saved, image savings and performance history are counted on your own server from real requests. Where a figure cannot be counted, for example pages your web server answered without PHP, the dashboard says so instead of guessing.

Only what a feature needs. Your licence check, signed updates and a daily install check-in (site address, versions, licence state and where your wpcachex.com panel can reach the site) go to wpcachex.com. Cloudflare is contacted only if you connect it, with your own API token, and Google Fonts only if you choose to host them on your site. Page scans, measurements and image conversions all run on your own server.

Ready for a faster WordPress?

One licence, every feature, signed automatic updates. Activate it on your sites in minutes.

Choose a planSign in