APMdigest asked industry experts – from analysts and consultants to the top vendors – to outline the most important factors that impact website response time. The third installment of the list, featuring factors 11–15, covers the back end.
11. THE BACK-END SERVER
From our perspective, back-end server responsiveness is the main factor to ensure a fast website response time.
Founder and CEO, BlazeMeter
Inadequate server resources: When the traffic to a website suddenly increases, the web server gets more requests than it can handle and fails to function efficiently. As a result, the website takes up additional server resources such as memory, disk space, bandwidth and processes, leading to a bottleneck on the server’s resources. If IT Ops don’t pay attention to the growing resource demands and plan capacity accordingly, this can lead to severe resource shortages resulting in poor-responding websites.
Sr. Market Analyst, ManageEngine
Website response times are often tied to server performance, and when a site is slow to load, the underlying cause can be a server delay driven by network bandwidth issues such as BYOD. Because speed is a critical factor in keeping people productive with online apps, or engaged with your website, it’s imperative that organizations are proactive in monitoring servers, networks and applications to identify problems before your online end users are impacted.
VP of Product Management, Ipswitch
While there are plethora of factors that can affect website performance, the top factor in my experience is the performance of its back-end calls. It does not matter if it is a RDBMS, an ERP system, a User directory or simply another application. If the back-end calls are slow, user experience will tank. Maybe the website is running out of database connections; maybe it is making excessive back-end calls; or maybe the back-end server is running out of hardware resources. Whatever the cause, slow back-end calls will eventually bring the website to its knees. Be sure to armor yourself with a modern APM tool to pinpoint the root cause of these slow calls.
Application Support Expert, www.karunsubramanian.com
12. THE DATABASE
According to many reviews written by the IT Central Station community, the top factor that impacts website response time is slow database queries. Some of our reviewers recommend analyzing the queries that are executed, ensuring that they are using indexes correctly. In this way, the time spent in the database can be reduced, improving the response time.
Founder and CEO, IT Central Station
When users experience poor website response time, IT needs to dig deeper than the network or applications. When loading, a web page might not show any errors, but users could be waiting on key dynamic content like a bank balance or an order status. This issue is frequently not the web or application server, but the database that supports them. Bad SQL code and non-optimized databases account for as many as two-thirds of all such website performance issues. Optimize SQL queries to boost website performance so people can blame the network again.
Sr. Director of Product, Idera
One of the top factors that we've seen in our analysis of hundreds of applications is interactions with databases; either slow database queries or too many database queries being executed per web request. As companies analyze how their code spends it's time, it is essential to see how often queries are called and how long they take to run.
Founder and CEO, Stackify
13. THIRD PARTY SERVICES
Third-party integrations such as SaaS vendor plugins can have a “creeping” impact on website performance. As you accumulate more functionality via third-party vendors, you have great functionality, but there is a performance hit. Each plug-in can run multiple queries which causes longer than optimal server side processing. By understanding the performance of queries supporting your website or web application, you can take action to optimize or combine queries for improved performance.
Director, Systems Management Product Marketing, SolarWinds
Third party vendors tend to be the biggest factor when it comes to delaying load times. The amount of requests a site has to make not only increases the time needed to load all of the elements, but also increases the chances for failure somewhere along the way. Furthermore, while reliance on third party infrastructure like DNS and CDNs can help expand the scope of your site’s user base, they also make it harder to detect isolated slowness or outages that may be localized to only a portion of your users. Without a comprehensive monitoring strategy of those third parties, you may not even know that you’re experience performance issues.
Chief Product Officer, Catchpoint
On the client side it is counter-intuitive - when you cram sites full of “bells and whistles” to influence potential customers, problems can arise. This is because videos, pop-up chats, and pay later options are typically driven by third party applications or hosted on CDNs. Add-ons like these often create performance issues that are difficult to identify and diagnose without a robust digital performance strategy and technology that provides a comprehensive end-to-end view encapsulating 100% of every end-user experience. From a customer's perspective, it’s best to think about what a site doesn’t need - and how to simplify and streamline instead. A function that comes at the cost of performance does more harm than good.
APM Evangelist, Dynatrace
14. THE NETWORK
For a modern website built using today’s coding and content best practices along with sufficient host resources, acceptable user response time is only as good as the underlying network. The main variable is throughput, which is the actual amount of data that can be delivered across a network at a given time. All things being equal, the fatter the pipe the better the web performance. Throughput takes into account variables that reduce a network’s theoretical maximum transfer rate (bandwidth) including underlying physical network status, network topology, number of users, and overall network integrity. These factors can negatively impact website response time. Having performance monitoring tools that can characterize these network attributes will enable organizations to achieve optimal website performance.
Solution Manager, Network Instruments/JDSU
Network delay for websites is the big issue. It is ultimately caused by a number of network related factors, not just bandwidth as many believe. So, website developers need to ensure they fully understand how well any site they create is going to be able to cope with the delays caused by a range of network conditions. This is going to involve conducting comprehensive pre-deployment testing in accurate replications of different network environments which is made possible, even easy, with network emulation.
Senior Technical Specialist, iTrinegy
Over commitment of virtualized infrastructure is frequently the cause of “Performance Phantoms" that plague websites: intermittent response time spikes which have inconsistent reasons for delay. Developers chase the delay, attempting to optimize an ever-changing set of slow code identified by APM tools, yet the issue persists. In these cases the slow code is not the root cause, but rather a symptom of micro-pauses of the VM which occur when the hypervisor has a demand that exceeds available resources, so any code unlucky enough to be running during pauses gets equivalently slower. Mission critical websites running in cloud or virtualized environments should be provisioned with dedicated resources to ensure that other tenants can’t steal resources and impact website performance.
Jon C. Hodgson
Global Consulting Engineer, Riverbed
One of the most common and yet difficult things for any admin to accomplish is to trouble shoot end user “slow-time” issues. Slow-time negatively affects enterprise performance and end user productivity ten times more often than downtime and can originate from just about anywhere within the enterprise. Constrained virtual resources can be the root cause of slow-time, or it could just be a resulting symptom. The key to resolving this issue is getting to the root cause quickly before the problem spreads to other systems bringing productivity to a standstill. The use of a 100% web based performance management solution will enable IT administrators to have universal insight into the infrastructure and enable IT to take action anytime, from anywhere on any device. The benefit is total visibility across all layers and tiers of the enterprise. Having universal insight enables and empowers IT admins to enhance IT service performance, increase operational efficiency and ensure IT effectiveness.
CEO, eG Innovations
Achieve more with less. How many of you feel that pressure — or, even worse, hear those words — trickle down from leadership? The reality is that overworked and under-resourced IT departments will only lead to chronic errors, missed deadlines and service assurance failures. After all, we're only human. So what are overburdened IT departments to do? Reduce the human factor. In a word: automate ...
On average, data innovators release twice as many products and increase employee productivity at double the rate of organizations with less mature data strategies, according to the State of Data Innovation report from Splunk ...
While 90% of respondents believe observability is important and strategic to their business — and 94% believe it to be strategic to their role — just 26% noted mature observability practices within their business, according to the 2021 Observability Forecast ...
Let's explore a few of the most prominent app success indicators and how app engineers can shift their development strategy to better meet the needs of today's app users ...
Business enterprises aiming at digital transformation or IT companies developing new software applications face challenges in developing eye-catching, robust, fast-loading, mobile-friendly, content-rich, and user-friendly software. However, with increased pressure to reduce costs and save time, business enterprises often give a short shrift to performance testing services ...
DevOps, SRE and other operations teams use observability solutions with AIOps to ingest and normalize data to get visibility into tech stacks from a centralized system, reduce noise and understand the data's context for quicker mean time to recovery (MTTR). With AI using these processes to produce actionable insights, teams are free to spend more time innovating and providing superior service assurance. Let's explore AI's role in ingestion and normalization, and then dive into correlation and deduplication too ...
As we look into the future direction of observability, we are paying attention to the rise of artificial intelligence, machine learning, security, and more. I asked top industry experts — DevOps Institute Ambassadors — to offer their predictions for the future of observability. The following are 10 predictions ...
One thing is certain: The hybrid workplace, a term we helped define in early 2020, with its human-centric work design, is the future. However, this new hybrid work flexibility does not come without its costs. According to Microsoft ... weekly meeting times for MS Teams users increased 148%, between February 2020 and February 2021 they saw a 40 billion increase in the number of emails, weekly per person team chats is up 45% (and climbing), and people working on Office Docs increased by 66%. This speaks to the need to further optimize remote interactions to avoid burnout ...
Here's how it happens: You're deploying a new technology, thinking everything's going smoothly, when the alerts start coming in. Your rollout has hit a snag. Whole groups of users are complaining about poor performance on their devices. Some can't access applications at all. You've now blown your service-level agreement (SLA). You might have just introduced a new security vulnerability. In the worst case, your big expensive product launch has missed the mark altogether. "How did this happen?" you're asking yourself. "Didn't we test everything before we deployed?" ...
The Fastly outage in June 2021 showed how one inconspicuous coding error can cause worldwide chaos. A single Fastly customer making a legitimate configuration change, triggered a hidden bug that sent half of the internet offline, including web giants like Amazon and Reddit. Ultimately, this incident illustrates why organizations must test their software in production ...