The Great HTTPS Migration

Most websites have been using the http protocol for many years without issue. The protocol used to access a website is rarely something most users consider or understand. Which is understandable, since the onus is on web developers to determine the protocol used when someone types in a website URL. For instance, the user types in “google.com” and the developer chooses to redirect to www. and also https instead of the default http.

The Web Is Getting Slower, and That’s a Problem

We’re all too familiar with the current Web design trends being replicated across many websites these days: much longer-scrolling pages, full-screen background photography (and auto-playing videos), parallax regions, scrolling takeovers, and tons of animations flying in and out. All of these techniques have gotten much easier to implement over the last few years, which has led us where we are today. What has been overlooked along the way, however, is the performance of websites using these techniques. And let me tell you, the Web is slow right now. Go ahead and finish your New York Times crossword while you wait for that home page with its 40-megabyte background video to load. You might as well multitask.