Surge
Surge generates and serves static HTML files for your WordPress site, causing quicker requests, faster load times and a shorter time to first byte (TTFB). Surge does not require configuration, and has no options. It works out of the box on any well-configured hosting platform. Cached files are store
Surge generates and serves static HTML files for your WordPress site, causing quicker requests, faster load times and a shorter time to first byte (TTFB).
Surge does not require configuration, and has no options. It works out of the box on any well-configured hosting platform. Cached files are stored on disk, and automatically invalidated when your site is updated.
In various load tests, Surge has shown to easily handle 1000-2500 requests per second at 100 concurrent, on a small single-core server with only 1 GB of RAM. That’s over 70 times faster than a stock WordPress install.
Via the WordPress Dashboard: navigate to Plugins – Add New. In the search bar type “surge” and hit Enter. Find the Surge plugin in the search results, hit Install, then Activate.
Manually: download the Surge plugin .zip file from WordPress.org. In your WordPress admin navigate to Plugins – Add New – Upload. Select the .zip file and hit Upload. Activate the plugin after upload is successful.
Manually via FTP: download the Surge plugin .zip file from WordPress.org, extract the archive, make sure the directory is called “surge”. Use your FTP/SFTP client to upload the “surge” directory to wp-content/plugins. Then activate the plugin in your WordPress admin from the Plugins section.
Using WP-CLI: wp plugin install surge –activate
Frequently asked questions.
Where is the plugin configuration screen?
There isn’t one.
How do I clear the cache?
Toggle the plugin activation or run wp surge flush using WP-CLI.
Is my cache working?
Visit the Site Health screen under Tools in your WordPress dashboard. Common caching errors, like installation problems, etc. will appear there. Otherwise, open your site in an Incognito window to see the cached version. You could also look for the “X-Cache” header in the server response.
