Skip to main content

20 Top Factors That Impact Website Response Time - Part 4

APMdigest asked industry experts – from analysts and consultants to the top vendors – to outline the most important factors that impact website response time. The last installment of the list, featuring factors 16–20, presents various factors you may not have considered.

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

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

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

16. IT INFRASTRUCTURE CHANGES

As new servers are powered on, database configurations changed, shared storage reconfigured, VMs reallocated, along with a whole host of other everyday infrastructure changes, little does the IT admin know how the upstream effects of these changes may be impacting web response times and the company’s bottom line. Consider this example: A storage (disk) change is made. The change slows a group of VMs. One of those VMs supports a database and therefore slows its queries. Let’s say those queries support the e-commerce application servers. As a result 60% of the users of this application experience slower responses. Or let’s say an overzealous VM admin observes that certain hosts are underutilized and adds an additional application to the underutilized servers. Now when an unexpected spike in user load occurs there will be insufficient compute resources to cover for it. Within each of those technologies, and the transitions between them, lies the potential for problems in end user transactions.
Steve Rosenberg
VP & GM, Dell Performance Monitoring

17. ALTERED CODE

One of the top factors impacting website response time is altered code, which doesn't trigger traditional monitoring alarms, as those are usually based on existing or known thresholds.
Mike Paqquette
VP of Security Products, Prelert

18. DISTRIBUTED DENIAL OF SERVICE ATTACKS (DDoS)

Quocirca researched the concerns Europe organizations have about the security and performance of their online domains and the action taken to mitigate these in 2014. The survey found, that by a small margin the biggest overall concern was denial of services attacks, which have now become so wide spread that they can effect just about any online resource. This is backed by other non-Quocirca surveys that show the number and scale of attacks has continually increased in the last few years. However, whilst it is the biggest attacks that hit the headlines, it is huge number of smaller, largely unreported attacks, that should be of most concern. These are launched as diversionary measures to mask other more targeted attacks or even as demos. DDoS was followed by user end point issues, poor network performance poor website server performance and DNS performance in that order.
Bob Tarzey
Analyst and Director, Quocirca

Download the free report from Quocirca.

19. INFORMATION ARCHITECTURE

The top factor that impacts website response time is the user’s experience. And that is dependent on information architecture. Just responding fast to an http request is insufficient as that would be a technical answer to a business problem. The website exists, presumably to provide information and to answer a user’s question or questions without human intervention; thus, providing information availability 24x7. Is the information on the website structured appropriately so that the user finds the information appropriate to their need instead of waiting and then getting unhelpful information? Information architecture structures the information available for each role and may be grouped by industry. In addition good information architecture structures information in the best form to answer a questions or better yet, solve a problem. Putting the right information in front of the user without excessive navigation and false starts is the best way to improve response. The information provided should build in complexity as the user’s engagement continues. We should be timing how long it takes to get helpful information to the user and not just how long a request/response took.
Charley Rich
VP Product Management and Marketing, Nastel Technologies

20. THE IT TEAM

One factor that is often overlooked is finger pointing. Website response time can be impacted by a number of different factors, which can cause internal finger pointing as folks try to pinpoint the problem. Could be that the client’s network is slow; maybe there’s an issue with the WAN link out to the ISP; perhaps the firewall is slowing or denying traffic – you get the picture. Without an overarching performance monitoring platform to keep an eye on all of these disparate areas, that internal struggle can slow things down considerably.
Brian Promes
Director of Product Marketing, SevOne

In today's software-defined economy where every business runs on apps, the top factor that impacts performance and response time is inattention to early warning signs like increased load time for key pages, long-running database queries, or unresolved user complaints. Often, apps provide clear indications via monitoring alerts when any of these occurs but restoring and maintaining performance first requires a culture of service quality that associates uptime with customer value. Tools and metrics are useful but only if people and process are aligned to deliver exceptional user experiences. A lack of service culture often leads to early warning signs being ignored. One way to ensure that app teams value site performance is to make it easier for them to focus on solving problems that most directly impact customer experience. Too many irrelevant alerts means valuable resources spend time figuring out what problem to solve or solving the wrong problem - either of which are inefficient and demotivating.
Dan Turchin
VP Product, Big Panda

The Latest

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

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

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

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

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

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

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

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

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

20 Top Factors That Impact Website Response Time - Part 4

APMdigest asked industry experts – from analysts and consultants to the top vendors – to outline the most important factors that impact website response time. The last installment of the list, featuring factors 16–20, presents various factors you may not have considered.

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

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

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

16. IT INFRASTRUCTURE CHANGES

As new servers are powered on, database configurations changed, shared storage reconfigured, VMs reallocated, along with a whole host of other everyday infrastructure changes, little does the IT admin know how the upstream effects of these changes may be impacting web response times and the company’s bottom line. Consider this example: A storage (disk) change is made. The change slows a group of VMs. One of those VMs supports a database and therefore slows its queries. Let’s say those queries support the e-commerce application servers. As a result 60% of the users of this application experience slower responses. Or let’s say an overzealous VM admin observes that certain hosts are underutilized and adds an additional application to the underutilized servers. Now when an unexpected spike in user load occurs there will be insufficient compute resources to cover for it. Within each of those technologies, and the transitions between them, lies the potential for problems in end user transactions.
Steve Rosenberg
VP & GM, Dell Performance Monitoring

17. ALTERED CODE

One of the top factors impacting website response time is altered code, which doesn't trigger traditional monitoring alarms, as those are usually based on existing or known thresholds.
Mike Paqquette
VP of Security Products, Prelert

18. DISTRIBUTED DENIAL OF SERVICE ATTACKS (DDoS)

Quocirca researched the concerns Europe organizations have about the security and performance of their online domains and the action taken to mitigate these in 2014. The survey found, that by a small margin the biggest overall concern was denial of services attacks, which have now become so wide spread that they can effect just about any online resource. This is backed by other non-Quocirca surveys that show the number and scale of attacks has continually increased in the last few years. However, whilst it is the biggest attacks that hit the headlines, it is huge number of smaller, largely unreported attacks, that should be of most concern. These are launched as diversionary measures to mask other more targeted attacks or even as demos. DDoS was followed by user end point issues, poor network performance poor website server performance and DNS performance in that order.
Bob Tarzey
Analyst and Director, Quocirca

Download the free report from Quocirca.

19. INFORMATION ARCHITECTURE

The top factor that impacts website response time is the user’s experience. And that is dependent on information architecture. Just responding fast to an http request is insufficient as that would be a technical answer to a business problem. The website exists, presumably to provide information and to answer a user’s question or questions without human intervention; thus, providing information availability 24x7. Is the information on the website structured appropriately so that the user finds the information appropriate to their need instead of waiting and then getting unhelpful information? Information architecture structures the information available for each role and may be grouped by industry. In addition good information architecture structures information in the best form to answer a questions or better yet, solve a problem. Putting the right information in front of the user without excessive navigation and false starts is the best way to improve response. The information provided should build in complexity as the user’s engagement continues. We should be timing how long it takes to get helpful information to the user and not just how long a request/response took.
Charley Rich
VP Product Management and Marketing, Nastel Technologies

20. THE IT TEAM

One factor that is often overlooked is finger pointing. Website response time can be impacted by a number of different factors, which can cause internal finger pointing as folks try to pinpoint the problem. Could be that the client’s network is slow; maybe there’s an issue with the WAN link out to the ISP; perhaps the firewall is slowing or denying traffic – you get the picture. Without an overarching performance monitoring platform to keep an eye on all of these disparate areas, that internal struggle can slow things down considerably.
Brian Promes
Director of Product Marketing, SevOne

In today's software-defined economy where every business runs on apps, the top factor that impacts performance and response time is inattention to early warning signs like increased load time for key pages, long-running database queries, or unresolved user complaints. Often, apps provide clear indications via monitoring alerts when any of these occurs but restoring and maintaining performance first requires a culture of service quality that associates uptime with customer value. Tools and metrics are useful but only if people and process are aligned to deliver exceptional user experiences. A lack of service culture often leads to early warning signs being ignored. One way to ensure that app teams value site performance is to make it easier for them to focus on solving problems that most directly impact customer experience. Too many irrelevant alerts means valuable resources spend time figuring out what problem to solve or solving the wrong problem - either of which are inefficient and demotivating.
Dan Turchin
VP Product, Big Panda

The Latest

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

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

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

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

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

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

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

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

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