RapidaPRO only

Fast WordPress pages, a safe checkout

Rapida stores pages as static files and serves them before WordPress loads. It warms the cache from your sitemap, trims CSS and JavaScript, measures the LCP image in real browsers and cleans the database. Cart, checkout and account pages are never cached.

Cache served before WordPress loadsCart, checkout and account always freshCSS and JavaScript optimisations stay off until you switch them onThe X-Rapida-Cache header says where a page came from

The Rapida screens

Overview: 22 cached pages, minified files and the six steps a page goes through, each marked on or off
Cache: a separate copy for phones, rebuild time, rejected URLs, cookies and browsers, query parameters
CSS and JavaScript: minify, combine, unused CSS and extra critical CSS
Lighter pages: every switch starts off, four are on here
Database: counts before cleaning and one button per item
Preload: queue status, a stop button and the pages that could not be cached

A slow site loses visitors, careless optimisation breaks checkout

Without a page cache every visit runs PHP and database queries. Combining and delaying scripts without exceptions, on the other hand, can break payments, the address form or the cart counter.

  • ✗ Every page built from scratch on every visit
  • ✗ The first visitor after a cache clear waits the longest
  • ✗ Delayed scripts that break payments and forms
  • ✗ No data on how fast pages load for real visitors

Rapida speeds up the site and leaves shopping alone

  • ✓ Static copies of pages, a separate copy for phones
  • ✓ A preload queue from the sitemap, paused while the server is busy
  • ✓ Cart, checkout and account without cache and without CSS or JavaScript changes
  • ✓ LCP, INP and CLS measured for real visitors

What Rapida does, area by area

Each area has its own tab in the Rapida screen, saved on its own.

Page cache

An advanced-cache.php drop-in serves static HTML before WordPress loads. A separate copy for phones, lifespan, rejected URLs, cookies and user agents. Tracking parameters (utm_, gclid, fbclid) are ignored, and chosen cookies, such as a currency or language cookie, get their own copy of the page. Optional cache for search results and for logged-in users.

Purge rules

A saved post clears its page, the home page, archives, categories and tags (also the ones it lost), the author, the previous and next post and parent pages. A new slug or unpublishing also clears the old address. Menus, widgets, the theme and the Customizer clear everything. Extra URLs take patterns.

WooCommerce

Cart, checkout and account are never cached and never optimised. Visitors with something in the cart or a shop session get a fresh page. A stock quantity change clears the product only; a stock status change also clears its categories and the shop page. A separate cache per geolocation.

Preload

One queue warms pages from the sitemap at a set speed (pages per minute) and waits while the server is busy. With no sitemap it follows the links on the home page. After a full clear, pages that were cached come back first. Status, a stop button and a list of pages that could not be cached.

CSS

Minify (adds font-display: swap), combine adjacent files and remove unused CSS computed on the server: the rules a page uses are inlined, the full stylesheets load without blocking. Extra critical CSS goes in a text field.

JavaScript

Minify, combine, defer and delay until the first interaction, with ready-made lists of scripts that must run at once. A script manager turns files off per page, post type, archive and device, with a test mode for administrators.

Media

Native lazy loading with a set number of eager images, iframes, a YouTube preview image instead of the player, background images, missing image dimensions, WebP copies made on upload and in the background, local copies of Gravatar pictures.

Hints and LCP

Each page is measured once per device in a real browser. The LCP image is preloaded (with srcset), images above the fold load at once and sections below the fold render lazily with content-visibility. Banners, menus and dialogs are skipped.

Fonts

Google Fonts merged into one request with display=swap, optionally served from your own server or removed. Fonts measured above the fold are preloaded.

Lighter pages

jQuery Migrate, the admin icon font for visitors, the password meter outside account and checkout, embedding your site elsewhere, RSS feeds, self pingbacks, shortlink and REST links, revision limit, autosave interval, WooCommerce scripts only on shop pages. Every switch starts off.

Database

Revisions (all or older than N days), auto drafts, trash, spam, transients, orphaned meta and term links, cached embeds, table optimisation. Counts before cleaning, one button per item, a table list with size and engine, and a schedule.

Tools

Page check (cache hit, compression, browser cache), OPcache reset, settings export and import as a file without API keys, Site Health tests, and a notice when another active plugin also caches or optimises pages. WP-CLI: wp rapida purge, preload, cleanup-db, webp and status.

Security

security.txt, an e-mail on sign-in from a new browser, log out inactive users, application passwords for chosen roles only, blocked usernames, user names hidden from visitors, XML-RPC and the file editor off. Every switch starts off.

Web Vitals

LCP, INP, CLS, FCP and TTFB from a chosen share of real visitors, stored as daily histograms per device and page type for 90 days. A weekly PageSpeed Insights test of the home page. Off by default.

Compatibility

WPML, Polylang and TranslatePress: a saved post clears its translations and the language home pages. WooCommerce Multilingual: the currency gets its own copy of the page. Elementor and Avada: saving a template clears the cache. Purges are passed on to an nginx cache on the server, and a persistent object cache backed by Redis is left alone.

Read more on WPPoland: Use case: cache exceptions for cart and checkout, purge on stock change

Live in three steps

Page cache, preload and LCP image measuring are on by default. You switch on the rest yourself.

01

Install

Upload Rapida and activate it. It adds the advanced-cache.php drop-in and the WP_CACHE constant, and on Apache a marked block with browser caching and compression in .htaccess.

02

Check the header

Load a page twice and look for X-Rapida-Cache: HIT in the response headers. The Tools tab runs the same check with one button.

03

Switch optimisations on one by one

Turn on CSS, JavaScript and media options one at a time and look at the site after each change. The Overview tab shows which steps a page already goes through.

Who Rapida is for

WordPress sites that should be fast for visitors without putting orders and forms at risk.

WooCommerce stores

Product and category pages from the cache, cart and checkout untouched. A stock change clears only what changed.

  • ✓ Checkout without delayed scripts
  • ✓ A separate copy per currency
  • ✓ Shop scripts only on shop pages

Business sites and blogs

Preload keeps the important pages cached, and measuring in visitors' browsers shows which image delays the LCP.

  • ✓ Sitemap preload
  • ✓ LCP image preload
  • ✓ Web Vitals from real visitors

Multilingual sites

A saved post clears its translations and the language home pages; other pages of that language stay cached.

  • ✓ WPML
  • ✓ Polylang
  • ✓ TranslatePress

People who look after many sites

Export the settings to a file and load them on the next site. Purge, preload and status also run from WP-CLI.

  • ✓ Export without API keys
  • ✓ WP-CLI
  • ✓ Site Health tests

Support and resources

Every plugin has its own documentation with setup walkthroughs. Bugs and questions go to the public GitHub repository for that plugin, we answer in the open.

Maintenance status

This plugin is maintained. We have announced no end-of-support date, and when we do it will say so here and in a release.

Changelog

Need help beyond the plugin?

Send the store context in writing. You will receive a scoped recommendation, without a sales call.

Plugin configuration

A written setup scope for your store, theme and current plugin stack.

Request configuration

Compatibility audit

Check the plugin against checkout, HPOS, blocks, theme code and critical integrations.

Request an audit

Custom integration

A scoped connector or extension when the standard plugin stops short of your workflow.

Describe the integration

Your email is used to answer this request only. Marketing messages require a separate, explicit opt-in.

Frequently asked questions

What are the requirements?

PHP 8.1 or newer and WordPress 6.5 or newer. WooCommerce is not required; when it is active, Rapida turns on its shop rules.

Does Rapida work on nginx and Apache?

Yes. The advanced-cache.php drop-in serves the cache files from PHP, so it works the same on nginx and Apache. On Apache Rapida writes a marked block with browser caching and compression to .htaccess. On nginx it writes nothing to the server configuration.

Does it work with an object cache on Redis?

Yes. Rapida has no object cache of its own and never flushes it when pages are purged. When a persistent object cache backed by Redis is running, the Rapida screen shows its card with connection, hits and memory, and a button to flush it by hand.

Will Rapida break the cart or checkout?

Cart, checkout and account are never cached, and visitors with something in the cart or a WooCommerce session get a fresh page. By default those pages also get no defer, no delayed scripts, no unused CSS removal and no combined files.

Does it work on multilingual sites?

Yes, with WPML (the ?lang= mode is cached per language), Polylang, TranslatePress and WooCommerce Multilingual. A saved post clears its translations and the language home pages. WPML languages on separate domains are not cached.

Can I run Rapida next to another cache plugin?

No. Two plugins doing the same job can break pages or serve stale copies. Rapida shows a notice when another active plugin also caches or optimises pages.

What does Rapida not do?

It does not rewrite file URLs to a CDN, has no object cache of its own, does no lossy image compression, does not minify HTML, does not change the login URL and has no multisite network settings. It also never serves a stale copy while a page is rebuilt: a deleted or unpublished page leaves the cache at once.

How do I check that a page is cached?

Front-end pages carry an X-Rapida-Cache header: HIT, MISS or BYPASS with the reason. Add ?norapida to a URL to see the page without the cache and without optimisation.

How do I switch Rapida off?

Deactivation removes the advanced-cache.php drop-in, the WP_CACHE line and Rapida's cache folders.

What does the licence give me?

Updates and support. Every feature and setting works without it; an active licence brings updates and help.

How much does Rapida cost?

Rapida is paid only and is not in the WordPress.org directory. It costs 49 EUR a year for 1 site, 89 EUR for 5 sites and 149 EUR for unlimited sites. Visitors from Poland see an approximate PLN price: 215, 389 and 649 PLN.

Faster pages without risking the checkout

Page cache, preload, CSS, JavaScript, media, database and security in one plugin. Cart, checkout and account stay fresh.

See plans & pricing