Depending upon where you live, you may have noticed the blog design fluctuation in tests the past week or two. Some of you were served a new version of the blog that was more graphic intensive but easier to navigate (or would have been, once it was fully rolled out). I was fairly optimistic about the ability to make it work but, sadly, it was not meant to be.
Once the new template had been published, the advertising earnings remained steady but the “valid” code put a strain on the server so great that it increased the resource demands by a factor of 15 (as in, a 1,500% increase in strain). Even though I pay to have the resources vastly exceed those necessary to maintain current demand, the code just wasn’t doing its job.
This resulted in the Google speedtest, which now directly influences search result rankings, falling off a cliff, dropping to a pathetic 56 out of 100. Had that been permitted to remain in place, it would have only been a matter of time before new visits began to decline.
Add in a conflict with the search engine optimization plug-ins and the cacheing program that distributes the site through Amazon’s cloud network so that it loads faster for visitors and that was the retreat warning. This morning, I rolled back to the previous design, though kept the color scheme of the upgrade.
Other changes include comments automatically closing on articles older than 14 days.
Related posts:





