Something looks broken after I pressed Auto.
Apply the Safe preset in the Tools tab first. It keeps page caching, browser caching and lazy loading, and turns off minification, deferred and delayed JavaScript, the CSS delivery settings and the other Auto settings that change how a page looks, including any you turned on yourself. The preset card in the Tools tab lists every setting it turns off. Then clear the cache (Admin bar > Prime Cache > Clear All Cache) and check menus, sliders and forms again.
If Safe fixes it and you want to keep the rest of Auto, apply Auto again and turn settings off in this order, clearing the cache after each step:
- 01Delay JavaScript Execution and Maximum Delay , if you turned them on yourself. Auto does not turn them on in the free plugin.
- 02Load JavaScript Deferred
- 03Load CSS Asynchronously (Free) , then Inline Small CSS Files
- 04Minify HTML , Minify CSS and Minify JavaScript
What does Auto change, exactly?
In the free plugin, Auto turns on: page cache with mobile caching, gzip compression, browser cache headers, .htaccess Optimization (only when .htaccess is writable), HTML / CSS / JavaScript minification, removal of HTML comments, lazy loading for images, iframes and videos (the first six images stay eager so the largest image is not delayed), missing image width/height, a local copy of jQuery when the theme loads it from a CDN, deferred JavaScript, inline small CSS, asynchronous loading of non-first CSS, Google Fonts display=swap, disabling emoji and embeds, removing version query strings, limiting DNS prefetch, disabling block CSS on classic themes, link prefetching and cache preloading. On WooCommerce sites it also turns off WooCommerce scripts on non-shop pages and cart fragments, and adds the cart, checkout and account pages to the exclusions.
Auto does not turn on Delay JavaScript Execution, WebP conversion or Brotli compression in the free plugin. Prime Cache Pro adds its own items to Auto (see the Description).
Does it edit wp-config.php?
The free plugin does not. It reads wp-config.php to see whether WP_CACHE is set, and never writes to it. Page caching works without WP_CACHE . If you add define( 'WP_CACHE', true ); yourself, cached pages are served before WordPress core loads, which is faster still. Prime Cache Pro can add the line for you with one click and writes a backup first.
Can I use it with another cache plugin?
Do not run two page caches at once. Deactivate the other cache plugin before you activate Prime Cache. Prime Cache detects 14 known caching and optimization plugins and warns you when one is active.
My host already has a server cache.
Do not let two page caches serve the same pages. When the host’s cache sits in front of Prime Cache, Prime Cache’s purge does not reach it, so visitors can keep seeing an old copy after you update a post. Decide which one serves your pages. If you keep the host’s cache, clear it as well whenever you clear Prime Cache. Prime Cache Pro detects common server-side caches and tells you when one is in front of the site.
Logged-in users see old pages.
They should not by default. Logged-in users are never served cached pages, and page optimizations are skipped for them. If you turned on Logged-in User Cache in the Page Cache tab, every logged-in user shares one cached copy with anonymous visitors; turn it off.
How do I clear the cache?
Multiple ways: the admin bar menu (Prime Cache > Clear All Cache and other options), Dashboard quick actions, WP-CLI ( wp prime-cache flush ), or the automatic purge triggers.
Is it available in Japanese?
Yes. The admin screens are translated into Japanese.
Does it help Core Web Vitals?
The features target the usual Core Web Vitals bottlenecks: page caching and preloading shorten server response time (TTFB, which feeds LCP), minification and deferred JavaScript reduce render-blocking resources, lazy loading and WebP conversion cut image weight, and keeping the first images eager protects the LCP image. Results depend on your theme, hosting and other plugins, so measure before and after each change.
What are the server requirements?
WordPress 5.8+, PHP 7.4+. For WebP conversion, the GD or Imagick PHP extension is required.
Does it work with Nginx?
Yes. Page caching, file optimization, media optimization, and all PHP-based features work on any server. The .htaccess Optimization feature needs a server that reads .htaccess and can be left off on Nginx.
Does it support WooCommerce?
Yes. WooCommerce cart, checkout, and account pages are automatically excluded from caching. Additional WooCommerce optimizations include disabling scripts on non-WC pages and disabling cart fragments AJAX.
Can I disable cache for a specific page?
Yes. Edit the post/page and check “Disable cache for this page” in the Prime Cache metabox in the sidebar.
Does the .htaccess fast path work for all requests?
The .htaccess fast path serves cached pages without loading PHP. It requires: lowercase Host header, no query string (unless cache_query_strings is disabled), no Vary Cookies, ASCII-safe URL paths, and GET requests only. Requests that don’t match these conditions are served by the PHP engine, which is still fast but not zero-PHP.
Does it support WordPress multisite?
Page caching is not supported on multisite installations. Other features (file optimization, lazy load, image optimization, etc.) work normally on multisite.
How does the image optimization work?
When WebP conversion and auto-convert are on, JPG/PNG images are converted to WebP on upload, including every thumbnail size. WebP is served to supporting browsers via .htaccess rewrite rules, picture tags, or URL rewriting.
Does Prime Cache send data to external services?
No. The free plugin does not send your data or API requests to any third-party service. Cache preloading only requests URLs on your own site. Some optional features may add browser resource hints (such as preconnect) for external assets your site already uses, but Prime Cache itself does not transmit data to external services.