Divi Rocket – Caching Plugin Specifically Designed For The Divi
Created Specifically for Divi Theme
Divi Rocket’s robust set of speed enhancing features include: Divi-aware server-side caching, Divi section controlled lazy loading, browser caching, database optimization, GZip compression and more coming soon!
Optimize Your Divi Website for Speed
Boost SEO, Reduce User Bounce
Clean, Easy and Intuitive to Use
developers. Since Divi Rocket was built specifically for Divi, we have optimized user interface to be as easy to use and intuitive as the Divi theme itself. Divi Rocket’s no-nonsense, clean User Interface is built both for the experienced Divi developer, and hobbyist in mind. With functionality broken up into individual tabs and useful tool-tips, you will feel
confident knowing what features you are enabling, and why you are enabling them. The end result? A faster Divi website and more engaged visitors without the headache.
Divi-Aware Server-side Caching
Traditional server-side caching works by temporarily storing web pages locally on the website’s server (rather than in a browser), remembering the content and quickly loading it each time your website is visited. The stored cache is then regenerated for the entire page any time a revision is made anywhere on the cached page, so it is properly served up to the next visitor. This method of caching speeds up the web page content being served to the visitor, but can be rather resource intensive and inefficient due to the way it broadly regenerates the cache.
How does Divi Rocket’s server-side cache differ from others available on the market?
Our revolutionary Divi-Aware server caching saves the static HTML of the individual Divi Modules on a page or post and
intelligently checks your website’s database to determine whether or not the cached modules need to be regenerated. In other words, being Divi-Aware means that it knows about the different types of Divi modules and when each of them needs to be re-generated, so it can generate only part of the page as needed (such as a blog module if a new post is added) rather than re-generating the entire page, post or product when a change is made that only affects one module.