內容簡介
RunCache 是一款免費的 WordPress 快取外掛，結合了全頁快取、Redis 物件快取及 CDN 功能，能有效提升網站性能與擴展性，並且不需要特定的主機環境。
【主要功能】
• 全頁快取：七種快取類型，依速度排名
• Redis 物件快取：持久化查詢結果，提升效能
• 自動清除快取：根據變更自動清除快取頁面
• 支援多種伺服器：兼容 NGINX、Apache、LiteSpeed 等
• 零配置快取：簡易設置，快速提升網站效能
• Cloudflare 快取：在邊緣伺服器快取 HTML
外掛標籤
開發者團隊
② 後台搜尋「RunCache – Full-Page, Object, and Edge Caching」→ 直接安裝（推薦）
原文外掛簡介
RunCache is a free WordPress caching plugin that combines a full page cache, a Redis object cache, and a CDN (content delivery network) in one place. It caches your pages in the web server itself, not only in PHP, and it runs on any server you control.
RunCache is built by RunCloud but does not require RunCloud hosting or a RunCloud account. It performs no license check and never contacts RunCloud.
See RunCache in Action
Why a Server-Level Cache Plugin Is Faster
Most WordPress caching plugins work at the application level. They still start PHP, load WordPress, and run a drop-in before returning the stored HTML, so much of the cost of building the page is incurred on every request.
RunCache configures caching at the server level, allowing supported server configurations to return cached pages without starting PHP or opening a database connection. On a cache hit, NGINX, Apache, or LiteSpeed reads the stored page and returns it directly, so PHP never starts, and no database connection opens. That is what visitors feel in Time to First Byte (TTFB), and it matters most during traffic spikes, when PHP workers are the bottleneck.
Server-level caching normally comes with a catch: it works only on one web server, or only on one host’s servers. RunCache is built the other way round. It supports NGINX, NGINX FastCGI, Apache, LiteSpeed, Redis, and Cloudflare, detects what your server actually runs, and offers only the types that will work.
Move hosts, and the same plugin and the same settings screen follow you.
Full Page Cache: Seven Types, Ranked by Speed
Instantly improve your site’s performance and scalability with zero-configuration caching and sensible defaults. RunCache writes the configuration for the type you pick and only offers what your server supports. Compare cache types.
NGINX FastCGI Cache: NGINX stores and serves the page itself, so PHP never starts on a hit. Fastest option on an NGINX stack. Needs shell access, plus ngx_cache_purge to purge single URLs. Setup guide.
Apache: mod_rewrite rules in .htaccess serve the stored file before the request reaches PHP. Nearly as fast as FastCGI and easier to enable, because .htaccess is usually already writable. Needs mod_rewrite, mod_headers, and a restart.
LS Cache: uses the cache engine built into LiteSpeed Web Server and OpenLiteSpeed. Comparable to FastCGI, and shown only when a LiteSpeed server is detected.
NGINX Cache: NGINX serves the stored HTML file directly. Simpler than FastCGI and needs no extra module, but varies on fewer request conditions.
Redis Cache: stores full pages in Redis rather than on disk. Slightly slower, because PHP still reads from Redis, but the right answer when several containers or servers share one cache.
PHP File Cache: serves stored HTML from a drop-in before WordPress loads. PHP starts, but your theme, plugins, and database are all skipped. Needs no server access, works on shared hosting, and is active the moment you activate RunCache.
Cloudflare Cache: caches your HTML at Cloudflare’s edge and purges it when you publish, serving pages near the visitor rather than from your server. Helps international traffic the most, and works in front of any of the six above. Setup guide.
Redis Object Cache
WordPress runs the same queries on every page load, fetching options, theme settings, and user data over and over, and the built-in object cache is cleared at the end of each request.
Redis Object Cache makes it persistent. WordPress checks Redis first, and on a hit, the value returns without touching the database. This is the layer that speeds up wp-admin, WooCommerce checkout, and membership areas, because none of those pages can be served from a page cache at all. Learn more, and secure Redis with ACLs before you expose it.
Clear the WordPress Cache Automatically
You should rarely need to clear the cache manually, because RunCache purges the pages your changes actually affected. Learn more about RunCache’s Cache Purging settings.
On publish and edit: clears that post and the archives it appears on, not the whole cache. On by default.
On comments: clears the post the comment belongs to, so it appears at once. On by default.
On-site changes: theme switches, permalink changes, and site title edits clear everything. On by default.
Optional triggers: menus, widgets, sidebars, Customizer, plugin activation, and upgrades. These ship off, because on a busy site, they clear far more than most people want.
Manual and scheduled: clear everything, one URL, or only expired entries, from the settings page, the admin bar, or WP-CLI.
Cache Preloading
A cache only helps visitors who arrive after it is built. The first request after a purge still waits for WordPress, and on a large site, that cold request is the slowest of the day.
Cache Preloader rebuilds those pages in the background, after a purge or on a schedule, so the cache is warm before anyone asks. It is rate-limited to 1-120 URLs per minute, so tune it to what your server can handle. Preloader settings, how WP-Cron schedules it.
Cache Rules and Exclusions
Caching the wrong page is worse than not caching, so RunCache ships safe defaults and lets you extend them all. Cache Rules reference.
URL Path Exclusion: wp-admin, REST API, feeds, sitemaps, login, cart, checkout, and account pages are excluded out of the box.
Cookie Rules: logged-in users, commenters, and visitors holding a WooCommerce cart bypass by default.
Query String Rules: ignore tracking parameters so ?utm_source= variants share one cached copy instead of duplicating it.
Browser and IP Rules: let a developer, editor, or uptime monitor always see the live page.
Additional Cache Key: store a separate copy per request header, which is how you serve desktop and mobile markup on one URL.
DONOTCACHEPAGE: always honored so that any plugin can force a bypass with no configuration from you.
Asset CDN
BunnyCDN, any Custom CDN hostname, or Cloudflare APO. Rewrites image, CSS, and JavaScript URLs so static files are served near the visitor, and purges the zone on demand. BunnyCDN setup.
What Is Never Cached
Logged-in users and commenters, cart, checkout, My Account, WooCommerce AJAX fragments, POST requests, feeds, REST requests, sitemaps, password-protected posts, page builder previews, and 404s.
Also Included
Import and Export Settings: move a configuration between sites as JSON, turning an hour of cache tuning into a one-minute setup on every client site after the first. Import and export.
WP-CLI native: wp runcache purge, preload-all, enable, status, and stats, so clearing the cache fits into a deploy script.
Multisite: network-enabled, cached pages namespaced per site, configured per site rather than network-wide.
Free, With No Paid Tier
All the features above are in this plugin. No pro version, no license key, no locked settings, no upsells, and no feature that stops working after a trial.
There is also no meter. No page view cap, no bandwidth cap, no limit on how many sites you install it on, and no yearly renewal. Nothing is throttled as your traffic grows, and RunCache does not send your site through a mandatory third-party optimization service. External requests are made only when you choose to configure an integration, such as Cloudflare or BunnyCDN.
Documentation and Support
RunCache product page
Introduction to RunCache
Getting started
All documentation
Do I really need a WordPress caching plugin?
WordPress performance FAQ
Support forum
External Services
RunCache contacts two third-party services, and only when you enable that integration and enter your own credentials. Otherwise, it makes no external requests. It contains no analytics, telemetry, or tracking. Web server detection and preloading requests stay on your own domain.
Cloudflare powers the Cloudflare Cache and APO integrations. Sent: your API token or account email and key, zone identifier, site hostname, and page URLs, and the cache rule, APO setting, or purge request. Sent when you save credentials, when a rule changes, on every purge, and at uninstall to remove the rule it created. Terms, Privacy.
BunnyCDN powers the Asset CDN integration. Sent: your API key and Pull Zone identifier, asset and page URLs, and the purge request, when you verify or save credentials, and on every purge. Terms, Privacy.
