Skip to content

Rapida

Rapida is a paid WordPress plugin with no free edition and no WordPress.org listing. It stores pages as static files and serves them before WordPress loads, warms the cache from your sitemap, trims CSS and JavaScript, measures the LCP image in real browsers and cleans the database. WooCommerce cart, checkout and account pages are never cached.

  • Getting started - installation, drop-in setup, verification and first steps.
  • Configuration - cache rules, CSS and JS optimization, LCP hints and database tasks.
  • Troubleshooting - cache bypass reasons, drop-in errors, WooCommerce and JS issues.
  • FAQ - common questions about multisite, page builders, headers and CDN.
  • PHP 8.1 or newer.
  • WordPress 6.5 or newer.
  • WooCommerce is optional. When it is active, the shop rules below switch on.
  • A writable wp-content folder (for the advanced-cache.php drop-in and the cache files) and a writable wp-config.php (for the WP_CACHE line).
  1. Upload the plugin, activate it and activate your licence. The licence gives updates and support; every feature and setting works without it.
  2. Rapida writes wp-content/advanced-cache.php and sets WP_CACHE in wp-config.php. On Apache it also writes a marked block with browser caching and compression to .htaccess. On nginx it writes nothing to the server configuration: the drop-in serves the cache from PHP on every server.
  3. Open Rapida in the admin menu. Load a front-end page twice and look for X-Rapida-Cache: HIT in the response headers, or press the page check on the Tools tab.
  4. Switch on CSS, JavaScript and media options one at a time and look at the site after each change.

Run one page cache on a site. Rapida shows a notice on the Plugins screen and on its own screen when another active plugin also caches or optimises pages.

Page cache, a separate copy for phones, .htaccess rules (Apache), measuring pages in real browsers, sitemap preload, hover prefetch, leaving cart, checkout and account pages unoptimised, and removing the emoji script. Everything else starts off: minify, combine, unused CSS, defer, delay, lazy loading, Lighter pages, Security and Web Vitals.

The Overview tab shows which steps a page goes through (page cache, CSS, JavaScript, images, measuring, security), the cache size and, with Web Vitals on, the measured results. Every other tab is saved on its own. The admin bar has Clear cache and Clear this page, and post lists have a Clear cache row action. Administrators, editors and shop managers may clear the cache.

  • Static HTML is served by the drop-in before WordPress loads.
  • A separate copy for phones when the theme prints different HTML on phones.
  • Rebuild cached pages after (hours): 0 keeps pages until content changes. Expired pages are warmed again.
  • Never cache chosen URLs (patterns allowed), cookies or user agents.
  • Query parameters: tracking and ad parameters such as utm_, gclid and fbclid are ignored; parameters you list get their own copy; any other parameter skips the cache.
  • A separate copy per value of chosen cookies, such as a currency or language cookie (at most 50 copies per URL).
  • Cache only for visitors with chosen cookies.
  • Optional cache for short search queries and for logged-in users (one private copy per login session).
  • Pages are never stored on a non-canonical URL. The Link, X-Robots-Tag, Content-Security-Policy and Content-Language headers of a page are sent again on a cache hit.
  • A Rapida box on posts, pages and products switches the cache or single optimisations off for that page.

Front-end pages carry X-Rapida-Cache: HIT, MISS or BYPASS; reason=.... The reason is a short fixed word that says why a page was not served from the cache. Add ?norapida to a URL to see the page without Rapida’s cache and optimisation.

  • A saved post clears its own page, the home page, the posts page, its archives, categories and tags (also those it lost), the author page, date archives, the previous and next post and parent pages.
  • Unpublishing, a new slug or a new parent also clears the old address.
  • Widgets, menus, the theme, the Customizer, the front page setting and other site-wide options clear everything. Editing or deleting a public term clears everything.
  • Also clear these URLs when any post changes: extra paths, (.*) for any path.
  • Purges are passed on to an nginx page cache on the server through the action its purge plugin listens on.
  • Cart, checkout and account pages are never cached. Visitors with the cart or session cookies bypass the cache.
  • Leave cart, checkout and account pages as they are (on by default): no defer, delay, unused CSS or combined files there.
  • A stock quantity change clears the product page only. A stock status change also clears its categories and the shop page. Price and product saves clear the product.
  • Coming soon mode clears everything.
  • A separate cache per geolocation when the shop uses geolocation with page cache support.
  • The cart fragments request for an empty cart is answered from a cached reply.
  • On the Lighter pages tab: WooCommerce scripts and styles only on shop pages, and no cart refresh script while the cart is empty.
  • One queue warmed at a set speed (pages per minute), paused while the server is busy. It uses Action Scheduler when present (every WooCommerce site) and WP-Cron otherwise.
  • The sitemap is found automatically; extra sitemaps can be listed. Without a sitemap, Rapida follows the links on the home page.
  • After a full clear, pages that were cached come back first.
  • A daily or weekly re-warm of the whole site.
  • The tab shows the queue status, a stop button and the pages that could not be cached.
  • Speculation rules (prefetch or prerender) on WordPress 6.8+, or prefetch on hover in other browsers. Font and file preload, DNS prefetch.
  • Minify CSS (adds font-display: swap) and Combine CSS files (adjacent files with the same media, order kept).
  • Remove unused CSS: computed on the server for each page; the rules it uses are inlined and the full stylesheets load without blocking. A safelist keeps classes added by scripts. Load CSS without blocking uses the same engine; use one of the two. Extra critical CSS is added to the inline block.
  • Minify JavaScript (files named .min.js are left alone) and Combine JavaScript files (off while delay is on).
  • Defer JavaScript: inline jQuery code waits for jQuery.
  • Delay JavaScript until the first interaction, with a list of scripts that run at once and a safe mode where only third-party scripts wait.
  • Combining is rarely faster over HTTP/2; it is there for sites with many small files.

The Scripts tab lists the styles and scripts each page loads while you browse the site as an administrator. Turn files off per page, post type, front page, archive, shop, search or URL pattern, for logged-in or logged-out visitors and per device. Test mode applies the rules to administrators only.

  • Native lazy loading; the first images on a page (3 by default) and the measured LCP image stay eager.
  • Lazy iframes and videos, a YouTube preview image instead of the player (size selectable), lazy background images from style attributes and stylesheets.
  • Missing image width and height added.
  • WebP: copies made on upload and in the background (wp rapida webp), kept only when smaller, deleted with their image, and served when Serve WebP copies is on. One cached page fits every browser.
  • Gravatar pictures copied to the uploads folder and refreshed weekly.
  • Google Fonts merged into one request with display=swap, served from your server or removed.

With Measure each page in real browsers on, the first visit per page and device reports the LCP image and what sits below the fold. The cached page is then rebuilt with the LCP image preloaded (with srcset), images above the fold eager, and sections below the fold rendered lazily with content-visibility. Banners, menus, dialogs and fixed elements are skipped, and you can add your own exclusions. Div blocks can be included for themes and page builders that build sections from divs. Same-site fonts measured above the fold can be preloaded (at most 3 per page).

Every switch starts off: WooCommerce assets only on shop pages, no cart refresh script while the cart is empty, remove jQuery Migrate, remove the admin icon font for visitors, password strength meter only on account and checkout, remove block editor presets on classic themes, stop embedding this site elsewhere, turn off RSS feeds, no self pingbacks, remove shortlink and REST API links, a revision limit and an autosave interval. The Heartbeat tab sets the polling in the admin, the editor and on the site.

Revisions (all, or older than N days), auto drafts, posts and comments in the trash, spam, unapproved comments, pingbacks and trackbacks, transients, orphaned post, comment, term and user meta, orphaned term links, cached embeds and table optimisation. The tab shows counts before cleaning, one button per item and a table list with size, overhead and engine (MyISAM tables can be converted to InnoDB). Cleanup can run daily, weekly or monthly.

  • Page check: cache hit, compression and browser cache headers for a URL.
  • OPcache reset and settings reset.
  • Export and import of the settings as a JSON file. API keys and tokens stay on the site.
  • Site Health tests: WP_CACHE, the drop-in, a writable cache folder and late scheduled tasks.
  • A cache size card, and an object cache card when a persistent object cache backed by Redis runs (connection, hits, memory, a flush button). Page purges never flush the object cache.

Every switch starts off: security.txt and pgp-key.txt with Site Health checks, an e-mail on sign-in from a new browser, log out inactive users, application passwords for chosen roles (with a revoke button on the Users screen), blocked usernames, lowering the role of users who stop signing in (with restore), registered and last sign-in columns, user names hidden from visitors (?author=N, the users sitemap, oEmbed, REST /wp/v2/users), XML-RPC off, the WordPress version hidden and the file editor off.

Off by default. A sampled share of real visitors reports LCP, INP, CLS, FCP and TTFB; the share is set in the browser, so cached pages are measured too. Results are stored as daily histograms per device and page type for 90 days. A weekly PageSpeed Insights test of the home page needs an API key. The Overview tab shows the 28-day p75, ratings and 90-day trends.

  • WPML: the ?lang= mode is cached per language; a saved post clears its translations and the language home pages. Languages on separate domains are not cached.
  • Polylang and TranslatePress: a saved post clears its translations and each language home; other pages of that language stay cached. The Polylang language cookie is a cache variant.
  • WooCommerce Multilingual: the currency cookie is a cache variant.
  • Elementor and Avada: template and option saves clear the cache, and their CSS is cleared with a full clear.
wp rapida purge
wp rapida preload [--stop]
wp rapida cleanup-db
wp rapida webp
wp rapida status
  • Filters: rapida_cache_page (return false to skip storing the current page), rapida_ignored_query (query parameters that never split the cache), rapida_post_purge_urls (URLs cleared with a post), rapida_sitemap_preload_list (sitemaps to warm), rapida_buffer (the page HTML before it is stored).
  • Actions: rapida_before_clean_post, rapida_after_clean_post, rapida_before_full_purge, rapida_purged.
  • No CDN URL rewriting.
  • No object cache of its own.
  • No lossy image compression with backups; WebP copies give most of the gain.
  • No separate cache copy for WebP or AVIF: one cached copy fits every browser.
  • No stale copy while a page is rebuilt: deleted and unpublished pages leave the cache at once.
  • No HTML minify and no removal of ?ver=.
  • No login URL change, no site-wide switch to turn comments off, no multisite network settings, no e-mailed reports and no 404 log.

Deactivation clears the cache, removes the drop-in, the WP_CACHE line and Rapida’s cache folders, and stops its scheduled tasks.