So far so good. It seems the use of CloudFlare CDN hasn’t broken anything critical yet, although as CloudFlare only caches static content, the slow response time of Ziphosting’s servers is still a problem.
So far, I have found that Ziphosting seems to be fine with hosting static files, but as soon as the mySQL server gets involved, everything takes longer.
To combat this, I’ve decided to go with a WordPress caching solution – in this case, I’ve chosen WP Super Cache. The idea is that WP Super Cache will pre-generate static HTML files which are served provided no changes are made to the actual content of the post and comments. Regardless, such caching systems have the potential to screw up the site (i.e. white screens of death) and comments (i.e. delayed, not visible).
One of the changes that was required to get WP Super Cache working is to enforce a new permalinks structure. I had been using WordPress’ default http://goughlui.com/?p=xxxx structure for a while, and while not elegant, it was sufficient.
Now, I have migrated to a http://goughlui.com/yyyy/mm/dd/title structure to make WP Super Cache most effective (and avoid a potential issue with too many cached files in a single folder). Luckily, links written in the old format are gracefully redirected to the new structure with no changes necessary. However, links and posts from now on will default to the new structure.
I’ve tried my best to configure WP Super Cache to be most effective to improve the user experience, while also hopefully not being too burdensome on my web hosting provider. I figure I’d do everyone a favour here …
So if you do experience strangeness or problems – please let me know.
UPDATE: Well, it seems the change of permalink format means a reset of all the share button counters on the site. While that’s a bit disappointing, I suppose there isn’t much I can do about it.
UPDATE 2: It seems it’s made the pingbacks feature work again. That’s cool! For some reason they stopped working a while back for pingbacks within my own site …