Statixly – Static Site Generator vs Varnish/Nginx Proxy Caching

Statixly converts your WordPress site into a fully static HTML website — eliminating PHP, databases, and server-side dependencies from your production host. The result: faster load times, a reduced attack surface, and the freedom to deploy on any web server or CDN. ⚡ Benefits: Why Statixly? 🚀 Faster page loads: Static websites load 3 to 5 times faster than WordPress sites by serving pre-rendered HTML without PHP execution or database queries. 🔒 Reduced attack surface: Static sites have no login page, database connection, or server-side code on your production host. This eliminates primary attack vectors such as SQL injection and brute-force attacks. 🌍 Deploy anywhere: Host on Cloudflare Pages, GitHub Pages, AWS S3, or any standard web server. No PHP, MySQL, or WordPress dependency is required in production. 💰 Lower hosting costs: Static files can be served from free or low-cost CDN-based hosts instead of a PHP-capable server. Managed WordPress hosting typically costs $25 to $100 or more per month, while static hosting is often free or very affordable on platforms like Cloudflare Pages or Netlify, which offer unmetered bandwidth on their free tiers. 🛠️ Zero production maintenance: Your live site is pure HTML. With no WordPress running in production, there are no security patches, plugin updates, or server-side dependencies to manage on your public host. 🎛️ Live export control: Start, pause, resume, or abort the export from the admin screen and monitor progress in real time. 📦 One-click download: The entire static site is packaged as a ZIP file, ready for extraction and upload. 🔄 Auto-resume on interruption: If internet connectivity drops during export, the job resumes automatically once the connection is restored. 🔍 SEO Benefits 📊 Better Core Web Vitals scores: Static HTML loads faster, directly improving Time to First Byte (TTFB) and Largest Contentful Paint (LCP), which are metrics Google uses as ranking signals. 🤖 Improved crawl efficiency: Search engine bots fetch plain HTML instantly, with no server-side rendering delay. This signals high crawl health and allows engines to index content more effectively. ⏱️ Higher uptime reliability: Static files served from a CDN experience near-zero downtime, helping avoid Google ranking penalties for frequently unreachable URLs. 🧹 No WordPress footprint in production: Common WordPress paths such as /wp-admin and /wp-login.php are removed from the live site, reducing spam crawling and preserving crawl budget. The admin screen provides the following capabilities: Start a static export job Monitor live export status in real time Pause, resume, or abort the export Download the generated static site as a ZIP file Download or delete export logs Delete temporary export directories Statixly systematically crawls website URLs, renders content, rewrites links for static output, and packages the results for deployment. Typical workflow First, build and set up your site as you normally do in WordPress. Make sure all content and settings are finalized before exporting. Next, open the Statixly admin screen and select the Generate/Export Static Site button to start the export process. After the export finishes, download the generated ZIP file containing your static website. Extract the files from the ZIP archive. Upload the extracted files to your chosen static hosting provider. For example, use your website’s document root on a web hosting server, Cloudflare Pages, GitHub Pages, AWS S3, etc. Important Requirements If the current WordPress website is on example.com and you want to make the static website available on example.com as well, move the WordPress website to a subdomain and protect it with HTTP Basic Auth, or move it to your localhost computer using a backup and migration plugin such as Duplicator. Permalink structure must not be set to Plain. Keep the Statixly export tab open while export is running. Not for e-commerce, etc. Statixly will not work on any WordPress website that generates content dynamically based on user interaction, e.g., an e-commerce or subscription-based website. Contact forms will not work. The contact form requires immediate backend processing upon submission by the user. However, this is on our roadmap. HTTP Basic Authentication If your WordPress install is protected with HTTP Basic Auth (for example, a staging or subdomain install), enter your credentials under Statixly → Settings → Security so Statixly can authenticate during export. Credentials are encrypted before storage and never exposed in logs or diagnostics output. Advanced Opt-In Options Statixly includes two optional safety/compatibility flags, both disabled by default and configurable from the Statixly → Settings → General screen. Allow insecure local HTTP fetch Enable this only for expired, invalid, or self-signed certificate environments where same-site HTTPS fetches fail TLS verification. This turns off SSL verification only for local same-site fetches. Prefer temporary storage above document root Enable this only if you explicitly want Statixly working directories outside wp_upload_dir(). By default, Statixly uses WordPress uploads paths. Please note that this option works only if the intended directory is readable and writable by the web server user. Both flags can also be set directly in the options table if preferred. Need Help? If you face any issues after installing the Statixly plugin, please open a support ticket with detailed information, and we will be happy to fix the issue.

Complete WordPress Varnish Cache 3.x/4.x/5.x and Nginx Proxy Cache integration. This plugin handles all integration with Varnish Cache and Nginx Proxy Cache. It was designed for high traffic websites. Main features admin interface, see screenshots console for manual purges, supports regular expressions so you can purge an entire folder or just a single file supports every type of Varnish Cache implementation, see screenshots for examples unlimited number of Varnish Cache servers use of custom headers when communicating with Varnish Cache does not interfere with other caching plugins, cloudflare, etc Varnish Cache configuration generator purge key method so you don’t need to setup ACLs debugging actively maintained You can control the following from the Varnish Caching admin panel : Enable/Disable caching Homepage cache TTL Cache TTL (for every other page) IPs/Hosts to clear cache to support every type of Varnish Cache implementation Override default TTL in posts/pages Purge key based PURGE Logged in cookie Debugging option console for precise manual purges This plugin also auto purges Varnish Cache / Nginx Proxy Cache when your site is modified. Varnish Caching sends a PURGE request to Varnish Cache / Nginx Proxy Cache when a page or post is modified. This occurs when editing, publishing, commenting or deleting an item, and when changing themes. Not all pages are purged every time, depending on your Varnish / Nginx Proxy Cache configuration. When a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge: The front page The post/page edited Any categories or tags associated with the page Varnish Cache / Nginx Proxy Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin does not install Varnish/Nginx for you, nor does it configure Varnish/Nginx for WordPress. It’s expected you already did that on your own using the provided config files. Inspired from the following : https://wordpress.org/plugins/varnish-http-purge/ https://github.com/dreamhost/varnish-vcl-collection/