Skip to main content

The Key to a Well-Running Web Site

Sven Hammar

Website development and maintenance is not a simple proposition. You need to get your message out to your audience in a fast, attractive and secure way. Yet, making a website attractive and keeping it secure may take away some speed. Buy back speed by reducing security and you stand a chance of having your users avoid your site. Skimp on the aesthetics and your speed and security may not mean a thing, nobody's coming. What's a developer to do?

The answer, of course, is "test, test, test!” Test in development, test in the real world and, as you're fine-tuning and fixing, test each content exchange until the website is humming and your users are busy navigating your site, not complaining about it.

Using the correct monitoring tools is one key to bringing your website to the public quickly and keeping it working flawlessly with the least amount of pain to your users. So let's introduce some three-letter abbreviations here; The tools available are Web Performance Monitoring (WPM – aka Synthetic Monitoring), Application Performance Management (APM) and Real User Monitoring (RUM). Each of these has its use cases and when used together they combine to keep your website responsive and your users satisfied.

WPM

WPM uses synthetic monitoring, also known as active monitoring, which is monitoring using web browser emulation or scripted recordings of web transactions. You control testing the performance of the website as a whole, including how pages render, response time to content requests and other aspects of website operation that are directly responsible for how well or how poorly the website runs.

Use synthetic monitoring to test specific pages or transaction types that may not get regular traffic on your website, monitoring it from a user's perspective. Behavioral scripts simulate the actions or exercise paths that your users will take. An example of this would be to have the script login to the website, go through a transaction, get to the purchase page and then abandon the purchase. This gives you a clear indication of how a user will experience your checkout page and whether it takes too long to complete a purchase.

Use WPM, as well, to check javascript timing to see how long it takes your pages to render. Use synthetic monitoring on live websites from clients scattered throughout the world to test the network paths from where your users are connecting.

APM

Use APM to allow your developers to dive deeper into website problems so root causes can be uncovered and fixes can be put in where they will do the most good. APM allows you to follow critical transactions through from start to finish so you can determine exactly what is going wrong on your website and perform searches for values to find where bugs, bottlenecks or less-than-optimal code can be found and fixed to create a faster, more efficient website.

RUM

Since RUM is a passive monitoring process, use it to provide information about how real-world users are experiencing your website. Find out whether slowdowns are tied to time-of-day, or specific content requests, or any of the variety of issues that can plague a normally smooth-running site. RUM won't tell you exactly what's wrong but it will alert you as things do go wrong and how your users are affected.

Unfortunately, RUM cannot be directed against specific pages or processes and cannot give you on-demand testing, nor can it be used to create an artificial load on your website to see how it reacts to stress. What it can do is alert you to those times when your website is starting to experience sub-optimal performance so you can get your team working on your issues.

Combine WPM, APM and RUM

The key to developing and maintaining a well-running website, then, is combining all three monitoring tools, using RUM to get a good sense of how your users are experiencing the website, WPM to exercise your code and get real baseline monitoring as well as testing of lesser-visited pages and using APM to troubleshoot and find the source of problems found by RUM and WPM. Only by using each of these tools can you ensure that your site is performance optimized.

Hot Topics

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

The Key to a Well-Running Web Site

Sven Hammar

Website development and maintenance is not a simple proposition. You need to get your message out to your audience in a fast, attractive and secure way. Yet, making a website attractive and keeping it secure may take away some speed. Buy back speed by reducing security and you stand a chance of having your users avoid your site. Skimp on the aesthetics and your speed and security may not mean a thing, nobody's coming. What's a developer to do?

The answer, of course, is "test, test, test!” Test in development, test in the real world and, as you're fine-tuning and fixing, test each content exchange until the website is humming and your users are busy navigating your site, not complaining about it.

Using the correct monitoring tools is one key to bringing your website to the public quickly and keeping it working flawlessly with the least amount of pain to your users. So let's introduce some three-letter abbreviations here; The tools available are Web Performance Monitoring (WPM – aka Synthetic Monitoring), Application Performance Management (APM) and Real User Monitoring (RUM). Each of these has its use cases and when used together they combine to keep your website responsive and your users satisfied.

WPM

WPM uses synthetic monitoring, also known as active monitoring, which is monitoring using web browser emulation or scripted recordings of web transactions. You control testing the performance of the website as a whole, including how pages render, response time to content requests and other aspects of website operation that are directly responsible for how well or how poorly the website runs.

Use synthetic monitoring to test specific pages or transaction types that may not get regular traffic on your website, monitoring it from a user's perspective. Behavioral scripts simulate the actions or exercise paths that your users will take. An example of this would be to have the script login to the website, go through a transaction, get to the purchase page and then abandon the purchase. This gives you a clear indication of how a user will experience your checkout page and whether it takes too long to complete a purchase.

Use WPM, as well, to check javascript timing to see how long it takes your pages to render. Use synthetic monitoring on live websites from clients scattered throughout the world to test the network paths from where your users are connecting.

APM

Use APM to allow your developers to dive deeper into website problems so root causes can be uncovered and fixes can be put in where they will do the most good. APM allows you to follow critical transactions through from start to finish so you can determine exactly what is going wrong on your website and perform searches for values to find where bugs, bottlenecks or less-than-optimal code can be found and fixed to create a faster, more efficient website.

RUM

Since RUM is a passive monitoring process, use it to provide information about how real-world users are experiencing your website. Find out whether slowdowns are tied to time-of-day, or specific content requests, or any of the variety of issues that can plague a normally smooth-running site. RUM won't tell you exactly what's wrong but it will alert you as things do go wrong and how your users are affected.

Unfortunately, RUM cannot be directed against specific pages or processes and cannot give you on-demand testing, nor can it be used to create an artificial load on your website to see how it reacts to stress. What it can do is alert you to those times when your website is starting to experience sub-optimal performance so you can get your team working on your issues.

Combine WPM, APM and RUM

The key to developing and maintaining a well-running website, then, is combining all three monitoring tools, using RUM to get a good sense of how your users are experiencing the website, WPM to exercise your code and get real baseline monitoring as well as testing of lesser-visited pages and using APM to troubleshoot and find the source of problems found by RUM and WPM. Only by using each of these tools can you ensure that your site is performance optimized.

Hot Topics

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