SpinupWP vs Warmer – Cache Warmer and Cache Preload Crawler

This plugin ensures that the SpinupWP page cache is cleared when your site’s content changes. Not using SpinupWP yet? Sign up here. SpinupWP is a modern server control panel that’s here to help you implement best practices for every server you spin up. Designed for WordPress. This companion plugin should be installed on sites created using SpinupWP to allow the page cache to be cleared when your site’s content changes. Not using SpinupWP yet? Sign up here. Any Provider We support DigitalOcean, Linode, AWS, and any other provider. If your server has an IP address, you can connect SpinupWP. It does need to be a fresh install of Ubuntu though. Latest & Greatest Software SpinupWP will install the latest stable versions of Nginx, PHP, MySQL/MariaDB, and Redis from the standard apt-get repos. No who-knows-what-they-did custom builds of packages. Disconnect from SpinupWP in the future and you can still keep your packages up-to-date with apt-get upgrade. Automatic Security Updates SpinupWP will configure your server to install security updates as soon as they are available to reduce the likelihood of a software vulnerability putting your server at risk. Free SSL/TLS Certificates Serving your site over HTTPS is essential these days, not only for security, but to take advantage of the performance improvements of HTTP/2 as well. When you add a site to SpinupWP, a free Let’s Encrypt SSL/TLS certificate will be acquired, installed, and configured for your site. And SpinupWP will handle certificate renewals as well, so you hardly need to think about certificates. Cache All the Things One of the keys to a great performing WordPress site is caching. All sites are set up with Redis object caching to greatly reduce database requests. And with the check of a box you can enable full-page caching to serve pages lightning fast without even hitting PHP. Git Push-to-Deploy Developers! Developers! Developers! Add a git repository to your SpinupWP site and simply push to master to deploy your code. GitHub, Bitbucket, or a custom git repo will work. You can also configure a build script to run some tasks on the server after deployment is complete. Error Logs WordPress doesn’t enable error logging by default. Probably because the log is saved to a publicly accessible directory and can quickly balloon to take up a lot of hard drive space. SpinupWP enables error logs by default but stores them in a safe place and makes sure they’re rotated regularly like other server logs. Security Security Security Each server provisioned by SpinupWP is security-hardened from the word go. SSH login is disabled for the root user (you login with your user and use sudo instead). The firewall only allows connections to Nginx and SSH and failed attempts are monitored and blocked when the reach a threshold. Nginx is configured to defend against XSS, clickjacking, MIME sniffing, and other attacks. Software security updates are installed automatically. Scheduled Posts Published on Schedule For every site you add via SpinupWP, a server-side cron job will be configured to make sure that your WordPress site’s cron is executed every minute, as it should be. WP-CLI Preloaded If you love WP-CLI (we do! ❤) you’ll be very pleased to find it available on the command line the first time you login to your server. Security Isolation for Sites For each site that you add to your server via SpinupWP, a new system user is created for that site. All site files are owned by the site user and a PHP-FPM pool is configured to run as that user as well. Each site only has access to its files and so if only one site has a security vulnerability and gets infected with malware for example, only the files for that one site can be infected. SFTP Access for Your Clients If you’re hosting a site for someone else, you can easily give them SFTP/SSH access to just that site. And because of the security isolation between sites, they will only have access to files for that site. Professional Guidance & Best Practices SpinupWP will actively point you in the right direction and offer suggestions for maintaining your server. And because it provides detailed feedback about the operations it runs on your server, you can learn what is happening with your server. New release of Ubuntu just came out, should I upgrade? We’ll add a notice to the app about that, why we don’t recommend upgrading your existing servers, and how you can spin up a new server with the new release of Ubuntu and migrate your sites to that server instead. Should I install Varnish to improve page caching performance? We’ve benchmarked Varnish and Nginx FastCGI Cache performed better. Varnish would add complexity too, so one less moving part is another reason. Much of the time SpinupWP will suggest things that you may not have even thought of. Email deliverability for example. SpinupWP will strongly encourage you to configure an email sending plugin for the best email deliverability. SpinupWP’s guidance is especially helpful for those new to managing a server, but can also help those who’ve been at it a while, providing transparency to our decisions. Scheduled Backups of Site Files & Database All server providers (DigitalOcean, Linode, etc) offer automated backups of your entire server for a fee. These services are great and we highly recommend having backups of your whole server. But what happens if some media or data was deleted by accident from your WordPress site? You’re not going to restore your entire server just to get that data back. That’s where site backups come in. Site backups are full backups of your site files (media, themes, and plugins) and database. They allow you to easily restore a single site or just some files or data from a single site. With SpinupWP’s site backups, you choose your preferred provider to stash your backups whether that’s Amazon S3, DigitalOcean Spaces, or Google Cloud Storage. You plug in your account details and SpinupWP will send your site backups there in an easy-to-see format. Teamwork Makes the Dream Work Create a new team account, invite a member of your team, and allow them to spin up their own servers. Or just only allow them to add sites, the permissions you give them is up to you. Features Page cache purging Persistent object caching Ensures debug.log files aren’t saved in a publicly-accessible location

Warmer is a WordPress cache warmer and cache preload crawler that visits your site URLs on a schedule so page cache can be generated before real visitors arrive. Most caching plugins create cached pages only after a URL is requested. That means the first visitor after a cache purge, cache expiration, deployment, or content update may hit a slower uncached page. Warmer helps solve that cold-cache problem by crawling selected URLs in the background and warming the cache ahead of time. Use Warmer to warm posts, pages, archives, media attachment pages, and supported custom post types. You control the schedule, URL sources, request delay, timeout behavior, and diagnostics from the WordPress admin. What Warmer does Warms page cache by visiting selected site URLs Preloads cache on a schedule using WordPress cron Crawls posts, pages, category archives, tag archives, media attachment pages, archives, and supported custom post types Provides manual start and stop controls Shows crawl status, success counts, failure counts, and downloadable logs Includes diagnostics for HTTP requests, URL sources, scheduler status, and server compatibility Supports automation workflows with webhooks and WP-CLI Saves settings automatically with Ajax and top-right confirmation notices Works alongside caching systems that build cache when a page is requested Why use a cache warmer? A caching plugin can make cached pages fast, but the cache usually needs to exist first. After a purge or expiration, the first real visitor may be the one who triggers cache generation. Warmer creates those first visits automatically, helping reduce cold-cache page loads and keeping important URLs ready for visitors. Warmer is useful after: Cache purges or cache expiration Publishing or updating content Theme, plugin, or deployment changes Low-traffic periods where pages may fall out of cache Scheduled maintenance Landing page, archive, and custom post type updates URL sources Choose which parts of your site should be warmed: Posts Pages Category archives Tag archives Media attachment pages Archive pages Supported custom post types Request controls Fine-tune cache warming behavior for your hosting environment: Page timeout Connection timeout Request delay Retry attempts User-Agent override Redirect handling SSL certificate verification Manual start and stop controls URL source testing Start with conservative delay and timeout settings, then adjust based on your server response time, cache behavior, and hosting limits. Logging and diagnostics Warmer includes visibility tools so you can understand what happened during each cache warming run: Crawl status tracking Success, failure, redirect, average time, and last-run statistics Structured log rows with status badges Log filters for errors, warnings, success, and redirects Search by URL, status, or message Downloadable logs Clear log history with confirmation System information Source testing Schedule status HTTP request diagnostics Compatibility Warmer is cache-plugin agnostic. It works with caching plugins, server caches, reverse proxies, and CDN/page cache layers that generate cache when a URL is visited. Common setups include: LiteSpeed Cache WP Rocket W3 Total Cache WP Super Cache NGINX FastCGI cache Varnish and reverse proxy caches CDN/page cache layers configured to cache visited pages Warmer does not replace your caching plugin. It helps your existing cache layer stay warm by requesting the pages you choose. Developer and automation features WP-CLI support for command-line cache warming workflows Webhook support for deployment and publishing workflows Diagnostics for testing URL sources and scheduler behavior Logs that make cache warming easier to monitor and debug Best use cases Warmer is built for site owners, developers, agencies, and performance-focused WordPress teams who want to reduce cold-cache page loads. It is especially helpful for: Business websites Blogs and publishers WooCommerce product pages and category pages when custom post type warming is enabled Membership and LMS sites with cacheable public content Sites using full-page cache Sites with scheduled cache expiration Sites where important pages should stay fast after cache purges