Requirements
| WordPress | 6.5 or higher |
|---|---|
| PHP | 7.4 or higher |
| Other caching plugins | Run only one caching plugin at a time. Quick Fire Nitro warns you if it detects another active cache plugin |
| CDN / account | Optional. Any CDN works by entering its URL — no account linking or API keys |
Installation
- Download the ZIP file from your account
- Go to Plugins → Add New → Upload Plugin
- Upload the ZIP and click Install Now
- Click Activate
- Open Quick Fire Nitro from the admin menu and enable the features you want
If you have another caching plugin active (W3 Total Cache, WP Super Cache, LiteSpeed Cache, WP Fastest Cache, Cache Enabler, SG Optimizer, and similar), disable it first. Two caching plugins at once can break your site.
Quick Start
- Open Quick Fire Nitro in your admin sidebar — the Dashboard opens first
- Use Apply Recommended Settings for a safe baseline, or enable features tab by tab
- On the Caching tab, turn on Enable Page Caching
- Save, then load your site in a logged-out browser to confirm pages are being cached
- Test after enabling minification or JS delay — those are the settings most likely to need exclusions
The admin is organized into nine tabs: Dashboard, Caching, CSS, JavaScript, Media, Advanced, Speed Test, Tools, and Support.
Dashboard
The Dashboard is a performance overview with live cache statistics and one-click actions.
| Cached pages | How many pages currently have a saved static copy |
|---|---|
| Cache size | Total disk size of the cached files |
| Hit ratio | How often requests are served from cache versus generated fresh |
Quick Actions
| Clear Cache | Empties the page cache so the next visit regenerates fresh copies |
|---|---|
| Apply Recommended Settings | Turns on a safe, balanced set of optimizations in one click |
| Warm Up Cache | Crawls your sitemap to pre-build cached pages so even the first visitor gets a cached page |
If another caching plugin is detected, a conflict warning appears here so you can disable one of them.
Caching Tab
Page Cache
| Enable Page Caching | Save a static HTML copy of each page and serve it to visitors for fast delivery |
|---|---|
| Separate Mobile Cache | Store a separate cached copy for mobile devices so each gets the right layout |
| Force No-Cache (Dev Mode) | Sends no-cache headers to everyone and overrides page caching while on — use during development |
| Cache Lifetime (seconds) | How long a cached page is valid before it's rebuilt. Minimum 60; 3600 = 1 hour |
| Never Cache These URLs | Paths that should always be generated fresh (e.g. carts, account pages) |
Server Compression
| GZIP Compression | Compress pages and assets before sending them. Writes rules to .htaccess |
|---|---|
| Browser Caching | Tell browsers to cache static files for longer. Writes rules to .htaccess |
Admin Toolbar
Show Clear Cache in the Toolbar adds a one-click cache-clear button to the WordPress admin bar.
CSS Tab
Markup
| Minify HTML | Remove extra whitespace and comments from page HTML |
|---|---|
| Aggressive HTML Minify | Strip even more whitespace. Test your site after enabling |
| Remove Query Strings | Strip the ?ver= value from static asset URLs |
CSS
| Minify Inline CSS | Minify CSS inside <style> tags |
|---|---|
| Minify CSS Files | Minify local .css files and serve cached copies |
| Aggressive CSS File Minify | Apply extra compression to CSS files. Test after enabling |
Fonts
| Optimize Google Fonts | Add display=swap and preconnect so text shows right away |
|---|---|
| Self-Host Google Fonts | Download Google font files to your own site and serve them locally |
| Preload Fonts | Preload specific font files so they're available sooner |
JavaScript Tab
| Minify Inline JS | Minify JavaScript inside <script> tags |
|---|---|
| Minify JS Files | Minify local .js files and serve cached copies (can break some themes — test) |
| Defer JavaScript | Add defer so scripts don't block the page from rendering |
| Delay JavaScript | Load scripts only after the first user interaction. Test carefully |
| Delay Timeout (seconds) | Fallback delay before scripts load anyway. 0 = wait for interaction only |
| Delay Exclusions | Scripts that must run immediately and shouldn't be delayed |
| Minify / Defer Exclusions | Scripts to leave untouched by minify and defer |
| Remove jQuery Migrate | Drop the jQuery Migrate helper script from the front end |
Delay and aggressive minify give the biggest speed gains but are the most likely to need exclusions. Enable one change at a time and test the affected pages.
Media Tab
Lazy Loading
| Lazy Load Images | Load images only as they scroll into view; also adds decoding=async. Width and height are kept intact to prevent layout shift |
|---|---|
| Lazy Load iframes | Defer loading of embedded iframes until needed |
| Lazy Load Videos | Defer loading of embedded videos until needed |
LCP Image Preload
| Preload Main Image | Tell the browser to fetch your hero/main image with high priority so it appears sooner |
|---|---|
| Image URL | The full URL of your hero or main image |
WordPress Cleanup
| Disable Emojis | Remove the emoji detection script and styles |
|---|---|
| Disable Embeds | Remove the oEmbed discovery script |
| Disable XML-RPC | Turn off XML-RPC and remove the pingback header |
| Header Cleanup | Remove extra tags WordPress adds to the page head, such as the shortlink and RSD link |
Advanced Tab
Link Preloading
Uses the WordPress Speculation Rules API to begin loading the next page before the visitor clicks, so navigation feels instant.
| Mode | Prefetch (download only, safer) or Prerender (full render, fastest) |
|---|---|
| Eagerness | Conservative (on click), Moderate (on hover), or Eager (immediately) |
CDN
| Serve Files From a CDN | Rewrite static asset URLs (images, CSS, JS) to your CDN hostname |
|---|---|
| CDN URL | Your CDN base URL, e.g. https://cdn.example.com |
Cache Warm-up
Enable Cache Warm-up crawls your sitemap to pre-build cached pages, so the first real visitor already gets a cached copy. You can also trigger a warm-up from the Dashboard.
Speed Test Tab
A built-in speed test measures your site's loading performance using modern browser timing APIs and reports:
| Load time | How long the page takes to finish loading |
|---|---|
| LCP | Largest Contentful Paint — when the main content becomes visible |
| CLS | Cumulative Layout Shift — how much the layout moves while loading |
| First paint | When the browser first renders anything on screen |
Run the test before and after changing settings to confirm your optimizations are actually helping.
Tools Tab
Export Settings
Export to File downloads all your settings as a JSON file for backup or for copying to another site.
Import Settings
Upload a settings JSON file to restore or clone a configuration. This replaces your current settings.
Cache clearing and warm-up are also available from the command line — see WP-CLI Commands.
Support Tab
The Support tab includes a contact form to submit a support request, plus links to help resources at plugins-for-wp.com.
How Caching Works
When page caching is on, the first visitor to a page triggers WordPress to build the HTML as usual. Quick Fire Nitro saves that finished HTML to disk. The next visitor is served the saved copy directly, skipping the heavier WordPress and database work, so the page arrives much faster.
- Desktop and mobile can keep separate cached copies when Separate Mobile Cache is on
- Cached pages expire after the Cache Lifetime you set, then rebuild on the next visit
- Pages listed in Never Cache These URLs always generate fresh
- Optional gzip pre-compression and browser-caching headers are written to
.htaccess - Minified HTML/CSS/JS is cached too, so the minification work is done once and reused
Link Preloading
Link preloading uses the browser's Speculation Rules API to load the likely next page ahead of time. In Prefetch mode the next page is only downloaded; in Prerender mode it's fully rendered in the background so it appears instantly on click. Eagerness controls when that happens — on click, on hover, or immediately for visible links.
Prerender + Eager feels the fastest but uses the most bandwidth and CPU. Prefetch + Moderate is a good balance for most sites.
WP-CLI Commands
wp qfn clear | Clear the page cache |
|---|---|
wp qfn warm | Warm the cache by crawling your sitemap |
Handy for deploy scripts and cron jobs — clear the cache after a deploy, then warm it so visitors never hit a cold cache.
Plugin Conflicts
Running two caching plugins at the same time can double-cache pages, corrupt output, or break your site. Quick Fire Nitro detects other common caching plugins and shows a warning so you can disable one. Keep only a single caching plugin active.
Troubleshooting
My site looks broken after enabling minify or delay
- Turn the most recent setting back off and retest — aggressive minify and JS delay are the usual culprits
- Add the offending script to Minify / Defer Exclusions or Delay Exclusions
- Clear the cache after every change so you're testing fresh output
Changes aren't showing up
- Clear the cache (Dashboard, admin toolbar, or
wp qfn clear) - You're probably seeing a cached copy — test in a logged-out/incognito window
- If you use a CDN, purge it too
Pages don't seem to be caching
- Confirm Enable Page Caching is on and Force No-Cache (Dev Mode) is off
- Logged-in users and excluded URLs are served fresh by design — test logged out
- Check the Dashboard for a rising cached-page count and hit ratio
Another caching plugin warning appears
- Disable the other caching plugin — only one should be active
- Server-level caches (LiteSpeed, host page cache) can also conflict; pick one layer to manage caching
Images load late or the layout jumps
- Lazy loading keeps image width/height to avoid layout shift — make sure your images have dimensions set
- Set your hero image in LCP Image Preload so it loads with high priority
GZIP or browser caching isn't taking effect
- Those options write to
.htaccess; they need an Apache/LiteSpeed server with write access to that file - On Nginx, add the equivalent rules in your server config instead