20 Top Factors That Impact Website Response Time - Part 2

APMdigest asked industry experts – from analysts and consultants to the top vendors – to outline the most important factors that impact website response time. The second installment of the list, featuring factors 6–10, covers the front end.

Start with Part 1 of "20 Top Factors That Impact Website Response Time"

6. WEB PAGE SIZE

In my experience, the single most consistent factor that contributes to slower load times is page size. All other things being equal, a fatter page is a slower page. In one study I conducted of 60 popular sites that used responsive design, only 20% rendered acceptably quickly — and these were also the only sites that were less than 1 MB in size. According to the HTTP Archive, the average web page today is more than 2 MB in size. This is something site owners should be aware of, and concerned about.
Tammy Everts
Senior Researcher & Evangelist, SOASTA

7. RESPONSIVE WEB DESIGN

Mobilegeddon already is upon us where Google gives higher priority for websites that are mobile friendly. Hence, the new race is to build websites that use responsive web design techniques. This could create performance problems if resources, such as images, are not properly managed. For example, including all variations of images (for tablet, desktop, mobile, retina display) in a CSS and including this CSS incorrectly in the webpage can end up loading all variations of the image in the background for every request, hence slowing down overall page load time.
Gibu Mathew
Director of Product Management, Site24x7

8. JAVASCRIPT

Radware has been studying the various factors that impact website response time for years. Aside from a steady increase in the volume of data required for each page, one of the largest impacts that we are seeing comes from the increasing dependency on JavaScript. When these scripts block execution or download slowly the overall site performance is directly impacted.
Kent Alstad
VP of Acceleration, Radware

14 Best Practices to Cure Your Website’s Performance Pains

9. WEB CONTENT AND CODE

As more and more code resides on the browser side as opposed to server side, one of the top factors impacting website response time is un-optimized browser side content like download of large images, no caching, too many redirects or DNS lookups. Using APM tools, you can see a very granular breakdown of end user response time from the browser and determine the bottleneck at a glance. You can see exactly how much time was spent on resolving DNS lookups, how much time was spent in downloading content, time spent in load event scripts and so forth. It is essential that developers fine tune their browser side code following best practices, cross test across browser types, devices and platforms, and keep an eye on the end user experience with predictive alerts to prevent slow downs.
Payal Chakravarty
Sr. Product Manager - APM, IBM

The top factor that affects website response time is full page load time. Nothing harms the user experience more than slow loading times, especially when multimedia, Flash, or other graphics are involved. Users will leave your site if the video they want to view won't load. Slow load times can be caused by content-heavy pages and poor code on the website side, or inadequate bandwidth on the user side. To ensure website performance, IT can use ping requests and loading time measurements (specifically, the time it takes to download source code) to track page speed. It is often simple to fix problems that cause slow load times, but it is critical to effectively measure what load times are across each browser and on mobile devices to understand when your website is performing poorly.
Amanda Karkula
Channel Sales Manager, Paessler AG

10. N+1 QUERIES

N+1 queries are a common web application anti-pattern that can cause slow website response time. It happens when a single application query runs other queries “automatically” - resulting in multiple queries running at once. For example, a user may be browsing through a photo gallery and while switching from one picture to another, comments get rendered along with the photos. To diagnose, N+1 issues, look into the log data - if you see one query for photos and one for "comments" generated for every photo returned by the original query, you've got an N+1 query on your hands.
Trevor Parsons
Chief Scientist, Logentries

Read Part 3 of "20 Top Factors That Impact Website Response Time"

Related Links

Hot Topics

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

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

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

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 ...

20 Top Factors That Impact Website Response Time - Part 2

APMdigest asked industry experts – from analysts and consultants to the top vendors – to outline the most important factors that impact website response time. The second installment of the list, featuring factors 6–10, covers the front end.

Start with Part 1 of "20 Top Factors That Impact Website Response Time"

6. WEB PAGE SIZE

In my experience, the single most consistent factor that contributes to slower load times is page size. All other things being equal, a fatter page is a slower page. In one study I conducted of 60 popular sites that used responsive design, only 20% rendered acceptably quickly — and these were also the only sites that were less than 1 MB in size. According to the HTTP Archive, the average web page today is more than 2 MB in size. This is something site owners should be aware of, and concerned about.
Tammy Everts
Senior Researcher & Evangelist, SOASTA

7. RESPONSIVE WEB DESIGN

Mobilegeddon already is upon us where Google gives higher priority for websites that are mobile friendly. Hence, the new race is to build websites that use responsive web design techniques. This could create performance problems if resources, such as images, are not properly managed. For example, including all variations of images (for tablet, desktop, mobile, retina display) in a CSS and including this CSS incorrectly in the webpage can end up loading all variations of the image in the background for every request, hence slowing down overall page load time.
Gibu Mathew
Director of Product Management, Site24x7

8. JAVASCRIPT

Radware has been studying the various factors that impact website response time for years. Aside from a steady increase in the volume of data required for each page, one of the largest impacts that we are seeing comes from the increasing dependency on JavaScript. When these scripts block execution or download slowly the overall site performance is directly impacted.
Kent Alstad
VP of Acceleration, Radware

14 Best Practices to Cure Your Website’s Performance Pains

9. WEB CONTENT AND CODE

As more and more code resides on the browser side as opposed to server side, one of the top factors impacting website response time is un-optimized browser side content like download of large images, no caching, too many redirects or DNS lookups. Using APM tools, you can see a very granular breakdown of end user response time from the browser and determine the bottleneck at a glance. You can see exactly how much time was spent on resolving DNS lookups, how much time was spent in downloading content, time spent in load event scripts and so forth. It is essential that developers fine tune their browser side code following best practices, cross test across browser types, devices and platforms, and keep an eye on the end user experience with predictive alerts to prevent slow downs.
Payal Chakravarty
Sr. Product Manager - APM, IBM

The top factor that affects website response time is full page load time. Nothing harms the user experience more than slow loading times, especially when multimedia, Flash, or other graphics are involved. Users will leave your site if the video they want to view won't load. Slow load times can be caused by content-heavy pages and poor code on the website side, or inadequate bandwidth on the user side. To ensure website performance, IT can use ping requests and loading time measurements (specifically, the time it takes to download source code) to track page speed. It is often simple to fix problems that cause slow load times, but it is critical to effectively measure what load times are across each browser and on mobile devices to understand when your website is performing poorly.
Amanda Karkula
Channel Sales Manager, Paessler AG

10. N+1 QUERIES

N+1 queries are a common web application anti-pattern that can cause slow website response time. It happens when a single application query runs other queries “automatically” - resulting in multiple queries running at once. For example, a user may be browsing through a photo gallery and while switching from one picture to another, comments get rendered along with the photos. To diagnose, N+1 issues, look into the log data - if you see one query for photos and one for "comments" generated for every photo returned by the original query, you've got an N+1 query on your hands.
Trevor Parsons
Chief Scientist, Logentries

Read Part 3 of "20 Top Factors That Impact Website Response Time"

Related Links

Hot Topics

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

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

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

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 ...