You have now realized or are at least interested in the performance and security benefits of hosting your WordPress site as a static site. You may also be aware of the potential for massive cost-savings over your existing hosting.
It’s not always just a 1-click process to get your site fully functional in its new static format. There’s usually at least one thing you’ll need to tweak in order to get it functioning the same as it was when it was a plain old vanilla WordPress site.
We’ll go through the essentials, but also explore a whole other range of optimizations you can do to get the fastest-loading, secure and easy-to work on WP-powered static site.
Contact form solutions for static websites One of the most widely used WordPress plugins is the Contact Form 7 plugin. Install it, add a shortcode to a page(s) et voila, you have a working contact form for your website. This is great, until you start getting all the spam email abuse, even with reCAPTCHA enabled, but I digress. When you start using WordPress as a static site generator, one of the first things you miss is this easy contact form implementation.
Adding a search engine to your static site Another functionality that you get for free with WordPress is the built-in search mechanism. The way this works is by querying the database for the search terms you enter. This is great, but is also another point that can slow down your website. The more things that are requesting information at once add to site slow down. Caching queries can help a bit, but not all of your users are going to search for the same terms, so there’s still an initial cost for each new search term.
You may have used a tool such as pingdom to get a measure of your sites performance, related to the average time for websites to load. Here, we’ll outline a few points that can help with your “on-page” speed optimizations. There are other areas “off-page” that we will cover later, such as your DNS resolution, server response times, geo-distributed CDNs and more. Use the WP Path Rewriting configuration option in the plugin to shave off even more bytes per page.
Comments powered by Talkyard.