Skip to main content

Web Performance and the Impact of SPDY, HTTP/2 & QUIC - Part 1

Jean Tunis

As websites continue to advance, the underlying protocols that they run on top of must change in order to meet the demands of user expected page load times. This blog is the first in a 5-part series on APMdigest where I will discuss web application performance and how new protocols like SPDY, HTTP/2, and QUIC will hopefully improve it so we can have happy website users.

Start with Web Performance 101: The Bandwidth Myth

Start with Web Performance 101: 4 Recommendations to Improve Web Performance

So How Are We Doing?

In my last blog, I talked about all the different recommendations I've provided or come across over the years.

How are we doing with that? Are website owners out there listening?

Well, I decided to take a look at the archive — HTTP Archive, that is.

With HTTP Archive, I can look at some worldwide statistics on thousands of websites it monitors.

Let's look at bytes being sent to the browser.


As we can see, the average total byte size of a web page is a little over 2.3MB. And look at the biggest percentage in type of files: images account for about 63% of worldwide page sizes. Those file sizes can be reduced or minimized.

Okay. So maybe that was an outlier. In Performance Engineering, we never want to focus too much on averages. Percentiles and trends are things that give us better insight into whether something should be a concern or not.

So let's look at the trend in the past year.


We see that the trend of transfer sizes has been going up in the past year. Websites across the world have increased in size by about 18%. At this rate, if it continues, in 5 years, websites will increase in size by almost 300%! That's crazy!

While I think this is unlikely to happen with the increased importance placed on web performance, it's unbelievable to think we're increasing at this rate.

In my last blog, I mentioned how important it is to reduce latency. One of the ways to do that is to implement a content delivery network.

So let's see how that's going across the world.


We can see that only about 14% of websites have implemented a Content Delivery Network (CDN). With free CDNs out there, everyone should be using a CDN.

It's also encouraging that we're trending upward on that one.

Now that we get a sense of how websites are doing with HTTP requests across the globe, I want to look at the the protocol itself. If website operators are only slowly making some improvements, what can be done with the protocol itself to help?

Read Web Performance and the Impact of SPDY, HTTP/2 & QUIC - Part 2, covering the limitations of HTTP/1.0 and HTTP/1.1.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Web Performance and the Impact of SPDY, HTTP/2 & QUIC - Part 1

Jean Tunis

As websites continue to advance, the underlying protocols that they run on top of must change in order to meet the demands of user expected page load times. This blog is the first in a 5-part series on APMdigest where I will discuss web application performance and how new protocols like SPDY, HTTP/2, and QUIC will hopefully improve it so we can have happy website users.

Start with Web Performance 101: The Bandwidth Myth

Start with Web Performance 101: 4 Recommendations to Improve Web Performance

So How Are We Doing?

In my last blog, I talked about all the different recommendations I've provided or come across over the years.

How are we doing with that? Are website owners out there listening?

Well, I decided to take a look at the archive — HTTP Archive, that is.

With HTTP Archive, I can look at some worldwide statistics on thousands of websites it monitors.

Let's look at bytes being sent to the browser.


As we can see, the average total byte size of a web page is a little over 2.3MB. And look at the biggest percentage in type of files: images account for about 63% of worldwide page sizes. Those file sizes can be reduced or minimized.

Okay. So maybe that was an outlier. In Performance Engineering, we never want to focus too much on averages. Percentiles and trends are things that give us better insight into whether something should be a concern or not.

So let's look at the trend in the past year.


We see that the trend of transfer sizes has been going up in the past year. Websites across the world have increased in size by about 18%. At this rate, if it continues, in 5 years, websites will increase in size by almost 300%! That's crazy!

While I think this is unlikely to happen with the increased importance placed on web performance, it's unbelievable to think we're increasing at this rate.

In my last blog, I mentioned how important it is to reduce latency. One of the ways to do that is to implement a content delivery network.

So let's see how that's going across the world.


We can see that only about 14% of websites have implemented a Content Delivery Network (CDN). With free CDNs out there, everyone should be using a CDN.

It's also encouraging that we're trending upward on that one.

Now that we get a sense of how websites are doing with HTTP requests across the globe, I want to look at the the protocol itself. If website operators are only slowly making some improvements, what can be done with the protocol itself to help?

Read Web Performance and the Impact of SPDY, HTTP/2 & QUIC - Part 2, covering the limitations of HTTP/1.0 and HTTP/1.1.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...