Resource suggestion
-
1) each page a request (The wordpress cron processes each page every number of hits or seconds, producing a ready page that will be served to everyone who requests it, meaning a single request. The user only wants the page ready, so whoever should be busy requesting hundreds of requests is the installation itself); 2) Creation of the “Define content as static / html” checkbox on the post editing screen (for posts and pages of static content, which will not need to be updated with new information from the server)
-
You might take a look at WP2Static…
https://wordpress.org/plugins/static-html-output-plugin/
There are also people running lashups of HTtrack to webservers to serve up static sites.
Do pay attention to the limitations of static pages. It’s not always the best approach.
A reverse proxy might be a better choice. Some webhosts place reverse proxies in front of their web servers to reduce the load on their hardware. If your web host doesn’t offer that then you might look at building one yourself. Nginx seems to provide a great proxy system but running a separate server just to proxy one website is probably way overkill.
A cache plugin like W3Total (my favorite) is probably the best ‘bang for the buck’.
There’s another choice for servers that aren’t already overloaded…
Cloudflare takes over the DNS services for your domain immediately with one of the best DNS systems out there relieving your webserver from that duty and load. Cloudflare then attempts to proxy your website via their network.
The only problem with the free Cloudflare proxy service level comes about if your host isn’t able to respond to Cloudflare fast enough.
- You must be logged in to reply to this topic.