When your phone starts to feel slow or you find your tablet or laptop taking a long time to perform some task, you start to think about upgrading. Odds are a newer device will come with better specs and a generally more performant device.
When your phone starts to feel slow or you find your tablet or laptop taking a long time to perform some task, you start to think about upgrading. Odds are a newer device will come with better specs and a generally more performant device.
Should you use single quotes or double quotes when writing PHP? How about URLs? Should they be absolute or relative? You make choices like these when writing code and your choice will depend on a any number of factors, one of which is performance.
A couple of weeks ago I shared some performance tests for server response time as well as Speed Index and time to first byte that I ran on this site before and after moving to a new web host. The posts were part of an on-again off-again series about website performance that I’ve been running the last year or so. In every post up to this point I’ve talked as though all sites were built in fundamentally the same way. As you know, not all sites are built in the same way.
Last week I told you how I moved the site to a new host and that the site now runs on a server with better specs for a lower price. I also shared the results of a test to measure server response time and while response times are better with Siteground than my old host, they weren’t anything to brag about.
Since last spring I’ve been running an on-again, off-again series about website performance. In early April I left off with some talk about hosting, server hardware, and server software, specifically Apache, NGINX, IIS, and LiteSpeed. Oddly enough, between publishing the last of those posts and writing this one, I moved the site to a different web host.