Get In Touch
Recently by Stephen Ludin
Content delivery networks (CDNs) have been around and have evolved over a long time (in internet years). They all speak HTTP and you can safely rely on them to work with just about anything else that speaks HTTP. This is the beauty of standards -- HTTP in this case. What you cannot count on is there being a standard way to configure them. In some cases, this is understandable: they
This blog post is part of an ongoing series where we will discuss a wide range of H2-related topics. In today's post, we talk about some of the misconceptions regarding HTTP/2 being a silver bullet for improved website performance.
Akamai was the first CDN to support HTTP/2. This blog post is part of an ongoing series where we will discuss a wide range of H2-related topics. In today's post, we are boding a fond farewell to SPDY.
When Let's Encrypt was founded at the end of 2014 it had a lofty goal: promote the use of TLS everywhere by making certificates free and server configuration painless. It was noted that for many web administrators, for both large and small sites, TLS was seen as expensive, difficult to configure, and slow. With that headwind, the return on investment was seen as too low to bother unless you were
If there was ever a truism it is that technology is rapidly evolving under our feet. What was right today, is likely to be sub-optimal tomorrow. This situation can cause a sense of paralysis leading to delayed action because next week the "Next Great Thing" is coming soon. With the advent of HTTP/2 (h2) that translates to holding off on optimizing your web properties. When you have large portions of
HTTP/2 (h2) is incredibly exciting: The first major rev to HTTP in 15 years, focused on modern web development, performance minded, etc., etc. But one thing that has people looking at it with trepidation is that to use it you effectively need to move your site over to TLS (i.e. HTTPS). Though not a requirements in the protocol, no major browser has plans to put h2 in the clear. Whether
In early 2012 something remarkable happened: a call went out for proposals for a new version of HTTP. From the perspective of an Internet whose warp and weft seemingly shift on a daily basis, this may appear to be just one change amongst many, but because of the importance of HTTP in our daily lives, its impact is difficult to overstate. If you are reading this, it is likely
An Aging StandardHTTP is old. How old? Let's look at a timeline to start:1991 - HTTP/0.91996 - HTTP/1.01999 - HTTP/1.12013? - HTTP/2.0 Our beloved protocol that has been powering the information age in which we all live has been kicking around for over 21 years. Further, it has not had a major version change in 13! Using the dog year's metaphor, this puts the invention of HTTP back in the
Now, more than ever, time is money. The four two second rule is a thing of the past and companies today are not simply looking at performance as a specific bar to get over, but rather as an element that has a direct effect on their conversion rates. Akamai has supported this view this for a long time, and to that end have continually come up with new technologies to