Skip to main content

​
Compatibility

Yes, and you should. Lightify caches the HTML, your host caches at the edge, and the integrations keep them in step by purging both together. Kinsta, WP Engine, SiteGround, Cloudways, RunCloud, SpinupWP, GridPane, Rocket.net, and WordPress.com are all detected automatically.
No. Two plugins writing advanced-cache.php will fight, and which one serves a given request becomes unpredictable. Pick one.
Yes. Install the official Cloudflare plugin and Lightify purges Cloudflare whenever it purges itself. Without that plugin it has no credentials, so you would purge Cloudflare manually.Turn off Rocket Loader if you use it. It reorders script execution and fights with defer and delay.
Yes. Cart, checkout, and account pages are excluded automatically, stock changes purge the affected product pages, and multi-currency plugins are handled so visitors get the right currency from cache.
Yes. Progressify owns the service worker, so Lightify’s browser cache section shows as handled by it. Nothing to configure.
Yes, and it is where caching helps most. Two things to check: that wp-config.php is writable so WP_CACHE can be set, and that PHP execution limits are not too tight for preloading. Raise the preload delay if preloading strains the server.

​
Caching

Check the cache status on the overview page. It should say active. See confirming page caching.
No. Lightify purges automatically when content changes, including the pages that list the post, translations of it, and any page builder templates involved.You do need to purge after changing plugin settings, since existing cached pages were built under the old configuration.
Yes, with one cached copy per role. Only enable it if pages are identical for everyone in a role. Anything per-person will leak between users.
Yes. POST /purge-everything-and-preload with an application password. See the REST API.

​
Optimizations

Page caching, which needs no configuration. After that, Remove Unused CSS is usually the largest single win, because most themes ship one stylesheet covering every page.For interaction responsiveness, which is 30% of the score, Delay JavaScript Execution on third-party tags.
Turn off the last one you enabled, purge, and check. The usual suspects are Remove Unused CSS for visual problems, Defer or Delay JavaScript for broken interactivity, and Lazy Render Elements for anchor links.Then use the exclusion list rather than leaving the feature off.
Lightify controls what WordPress sends. It cannot fix a slow server, a third-party script that must run, or a theme that loads six web fonts. A lab test also simulates a throttled device, so a real-world-fast site scores lower there than its visitors experience.Aim for good Core Web Vitals from real visitors rather than a lab number.
You can. Smart Link Prefetch fetches links near the cursor; Speculative Loading uses the browser’s own prediction and can prerender rather than only download. They complement each other.

​
The score

Real measurements from your visitors on your cached homepage, weighted the way Lighthouse weights them. It is field data, not a lab test, so it needs traffic before it means anything.
Different measurements, both valid. See measuring performance.
Yes. Turn on score alerts and Lightify emails you when the grade moves, in either direction.

​
Database cleanup

The deletions are permanent and there is no undo. Expired transients and spam comments are safe. Post revisions are your edit history, and trashed posts may be things someone meant to restore.Back up before the first run, and look at what one manual pass removes before enabling a schedule.
Consider capping them instead. define('WP_POST_REVISIONS', 5); in wp-config.php keeps the five most recent per post, so they never accumulate and you keep a usable history.

​
Licensing

Pro is part of the DaftPlug membership. One license covers Lightify and every other DaftPlug Pro plugin, and plans differ only in how many sites you can activate on.
Nothing is deleted. Pro optimizations stop applying and the free ones carry on. Purge afterwards so cached pages are rebuilt without them.
Purge everything. Several Pro optimizations default to on, and existing cached pages were built without them.