FlexiStatic
Performance is most important for the first post/page that a visitor of your blog will request. Usually if the vistor like what he see the next pages are not so critical. But the nature of static sites implies that any dynamic elements of your install that reply upon WordPress plugins or internal fu
Performance is most important for the first post/page that a visitor of your blog will request. Usually if the vistor like what he see the next pages are not so critical. But the nature of static sites implies that any dynamic elements of your install that reply upon WordPress plugins or internal functions to operate dynamically will no longer work. So why do you want lost all the benefit from dynamic elements like captchas when making all the post/pages static? Chose only the landing pages and let the other posts work as prior.
FlexiStatic create real static html-sites. So you can also give the blog page (start page) a performance boost whatever do you still use WP static page option.
- 01Upload everything to the /wp-content/plugins/ directory
- 02Activate the plugin using the plugins menu in WordPress
- 03use the link “flexi static” at the tools menu
Frequently asked questions.
Q: Why do I need it?
A: You do not need it! Your visitors need it 😉 The most performant way to deliver a website is static html content. But this is not the best way for all single posts of your blog because you are losing the benefit of dynamic elements like captcha checks. So the optimal solution would be only make the landing pages / the start page static.
Q: Does it work with a CDN?
A: Yes. A CDN will cache the content of you blog posts. Usually the CDN ask for changes on your server before deliver the cached content. So real static content can speed up this process to.
Q: Why should I delete all static content before changing permalinks?
A: This plugin use the permalink provided by your WP core installation to create and check if a static version of the post/page is still stored on your webserver. So if do you change the definition of the permalink structure the plugin will not find prior stored content. We are thinking about a log for all static URLs. But this will need additional storage in the database and we want try to have as small/performant footprint as possible. Perhaps we will change this with a future version. But it is not on our agenda at this time.