惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

Catchpoint Blog

SRE Report: AI optimism and the economics of effort SRE Report: Why fast is what users trust The SRE Report 2026: Defensible Ns SRE Report 2026: What surprised us, what didn't, and why the gaps matter most Why Synthetic Tracing Delivers Better Data, Not Just More Data A New Chapter: LogicMonitor + Catchpoint – A Personal Note from Mehdi Mezmo + Catchpoint deliver observability SREs can rely on The four pillars holding up your digital business, and what happens when they crumble When payments pause: lessons from a global payments outage Observability 2025 Decoded: What the DZone Report Means for SLO-Driven Ops The next evolution of WebPageTest has arrived, and it’s a game-changer The Monitoring Blind Spot That Could Cost You Black Friday Powering Mexico’s Digital Future: Expanded Internet Observability with Catchpoint The Next Chapter of WebPageTest: Your New Experience Starts Soon SRE Report Retrospectives — Have AIOps Predictions Held Up? When BGP becomes UX: The inside story of a SaaS routing decision gone wrong (or right) Session Replay explained: A guide to seeing digital experience through your user’s eyes Making the invisible visible: Are your cloud firewalls and DDoS protection really working? Why it’s time to move beyond APM: Monitoring from the user’s perspective When metrics mislead: Inside the 2025 Retail Web Performance Benchmark The vendor trap: why your next outage won’t be your fault—but will be your problem LLMs don’t stand still: How to monitor and trust the models powering your AI Semantic Caching: What We Measured, Why It Matters The Annual SRE Survey Is Open—We Want to Hear from You Observability isn’t about the tool. It’s about the truth Invisible dependencies, visible impact: Lessons from the Google Cloud outage Real-time detection of BGP blackholing and prefix hijacks Leading analyst firm reveals the real cost of internet disruptions The Power of Over 3000 Intelligent Observability Agents Monitoring in the Age of Complexity: 5 Assumptions CIOs Need to Rethink Why Intelligent Traffic Steering is Critical for Performance and Cost Optimization Retail digital performance event recap: Key insights from IBM & Catchpoint Zendesk outage: A case for proactive monitoring and faster incident response Silence during chaos: Why the X outage is a call to arms for proactive monitoring The $1 Million Lesson: Building a Culture of Quality Through SLAs When AI tools fail: How to map your AI dependencies for proactive visibility Why Super Bowl 2025 was a triumph for Internet Resilience Why Internet Performance Monitoring is the new health check for IT organizations Why use Playwright in Catchpoint for synthetic monitoring Introducing WebPageTest Expert Plan: Real-Time Insights, Synthetic + RUM together in One Platform The shift to digital: How businesses are reshaping their priorities for 2025 The SRE Report 2025's Call to Action Monitoring in the Age of the Internet: DEM, IPM, and APM—What You Need to Know SSL Monitoring, Trust, and McLOVIN Lessons from Microsoft’s office 365 Outage: The Importance of third-party monitoring Cloudflare outage: another wake-up call for resilience planning 5 Actions you can take to improve digital performance 2024: A banner year for Internet Resilience APM vs Observability: Both-and, not either-or AppAssure: Ensuring the resilience of your Tier-1 applications just became easier APM vs observability: why your definitions are broken APM vs Observability: What comes next? APM vs Observability: Observing beyond APM AWS Outage: How do you prepare for the failure of your own safety net? Agentic AI: Powerful But Fragile—What You Need to Know Catch frustration before it costs you: New tools for a better user experience Catchpoint Peak Performance Summit 2025: Redefining Observability for the Outcome Economy Connected Devices: Unlocking the next frontier of Internet Performance Monitoring Cloud Monitoring's Blind Spot: The User Perspective Cloudflare’s Resolver Outage: More Than Just DNS How to Monitor AI Agents in Commerce Systems Creating the IPM Category: Catchpoint’s Journey to Leadership and the LogicMonitor Era Critical Requirements for Modern API Monitoring Diagnosing Wi-Fi failures that traditional tools miss: a case study Escalating risk, shrinking margins: The 2025 Internet Resilience Report From refresh to results: the metrics that shaped Election Day 2024 coverage Fast and furious: The importance of performance in the digital age Getting Started with Traceroute From the source to the edge: the six agent types you can’t ignore From SEO to AEO: Why Web Performance Is the Key to AI Search Success Here’s the proof: What the fastest sites on the web have in common Google’s Agent-to-Agent (A2A) Protocol is here—Now Let’s Make it Observable How IPM helped a top tech brand catch an OpenAI outage before it became a crisis How AI Turns Monitoring From “What Now?” Into “What’s Next?” How SAP achieved world-class uptime through modern observability
Performing for the holidays: Look beyond uptime for season sales success
2024-12-06 · via Catchpoint Blog

With the holiday shopping season in full swing, poor web performance can have a big impact on revenue. There’s intense competition for online shoppers, and customers will quickly bounce to another site instead of slogging through a bad experience. The best way to track and achieve your web performance goals is through experience-based SLOs (Experience Level Objectives, or XLOs). Get it wrong, and you risk losing sales during the holiday shopping rush—something we saw happen during Black Friday.  

Holiday revenue at stake

This year, the National Retail Federation projects 2024 holiday sales will reach record levels, up to $989 billion, with growth of 2.5% to 3.5% over last year. According to a recent study, the upward trend of online shopping will continue, as more than 90% of shoppers go online, and over 40% planning to do most or all their holiday shopping online.

Don’t be fooled by Availability

Most web Service Level Objectives (SLOs) are based on simple availability: Is your website up or down? But that doesn’t give you a good view of the performance users are actually experiencing at their locations. During the holiday shopping season, increased traffic can cause congestion and performance issues that don’t impact your service availability but can significantly harm customer experience.  

As our upcoming SRE Report 2025 confirms “Slow is (officially) the new down.” Users won’t wait for poor web performance—they get frustrated and bounce. Setting XLOs for performance metrics provides early warnings about negative trends that can impact business long before you reach an alert threshold.

To set and track performance goals on user experience, you need to measure performance metrics, like Core Web Vitals, from real locations—not just from the data center or cloud, where your customers aren’t. This is a key requirement for XLOs and the main factor that differentiates an SLO from an XLO. It’s the best way to measure web performance against realistic goals.  

A Tale of Two Metrics

To illustrate this point, consider two similar competing websites. We’ll call them Company_A and Company_B to avoid public shaming. We’ve set both an availability and a performance XLO for them. The performance XLO is based on Largest Contentful Paint (LCP), a Core Web Vital metric that helps indicate when the main content of a web page has likely loaded, making the page ready for user interaction.

Availability

The figures below show the availability burndown charts for Company_A and Company_B for the week of Thanksgiving through Black Friday and Cyber Monday. For both companies, the XLO was leniently set at 99.9% availability.  

As shown in the first chart, Company_A experienced a 6-minute outage on Black Friday evening. The outage wasn’t major enough to violate the overall objective, but it was unfortunately timed. A deeper analysis revealed web timeout failures for customers in Dallas, Denver, and Seattle, as they waited for servers to respond. Customers in these locations may gone to Company_B’s website instead, resulting in lost revenue for Company_A.

A graph on a computer screenDescription automatically generated

The second chart shows the availability burndown for Company_B. There were no outages during this time, so no XLO violations occurred, and the 99.9% objective was easily achieved. Looking at this alone, you might think all of Company_B’s customers were satisfied—but you would be wrong.

A screen shot of a graphDescription automatically generated

Performance: Largest Contentful Paint

The burndown charts for LCP below tell a different story. A good LCP score is 2.5 seconds or less. The XLO was set at 75% adherence for 2.5 seconds. That means for the majority of customers (or 75% of the time), the largest element rendered on the site happened within 2.5 seconds, providing a good user experience. This may seem lenient, but a 75th percentile is recommended for this Core Web Vital.

The first burndown chart shows Company_A easily beat the XLO objective, providing most customers a good user experience. This doesn’t include outages, so it only applies to users who successfully accessed their website.  

A graph showing a number of paintDescription automatically generated with medium confidence

Company_B, on the other hand, showed consistently slow LCP and missed their XLO before the Black Friday weekend was over.  

A graph showing a number of paintDescription automatically generated with medium confidence

A closer look at the scatterplot below shows that the LCP was often greater than 4 seconds. The black horizontal line represents the 2.5 second mark, making it clear how this objective was regularly missed throughout the major shopping week.  

A graph with blue dotsDescription automatically generated

Note that LCP isn’t necessarily when the web page is fully interactive, only that the largest object has rendered. A deeper analysis shows the full measure of Time To Interactive (TTI) for Company_B was often above 8 seconds when LCP was high. That level of poor performance was found across the entire month of November, not just Black Friday through Cyber Monday. Users experiencing that poor performance are typically frustrated and at risk of bouncing—likely to the competitor, Company_A.  

A graph showing a number of dotsDescription automatically generated

Wrapping it up

Measuring web performance from real locations is vital for setting realistic XLOs. As shown here, both companies maintained availability over 99.9% (despite Company_A’s limited outage), but only Company_A met their performance objective, offering a better user experience overall.

While Company_B might have congratulated themselves on 100% availability, the performance XLO shows they provided a suboptimal user experience for 25% of their customers for the entire high-value shopping period. This would have had a broader impact on user experience and, consequently, on revenue than a brief outage in a limited set of locations.  

This disparity highlights the importance of focusing on performance metrics like LCP, which directly impact user satisfaction. Availability alone can be misleading; it’s not enough to represent user experience. While both companies had issues during the peak holiday shopping period, the performance XLO suggests that Company_B fared worse.

The best way to avoid failing the peak shopping season is to set both availability and performance-based XLOs. Burndown charts, like those above, can help you project whether you’re on track to meet or miss your performance objectives from a real customer perspective. Ultimately, that impacts revenue. Given how much is at stake during the holiday shopping period, customer experience must be a top priority.

To learn more about how we can help you stay resilient during peak traffic periods, check out our Internet Resilience Program

Summary

With the holiday shopping season in full swing, poor web performance can have a big impact on revenue. There’s intense competition for online shoppers, and customers will quickly bounce to another site instead of slogging through a bad experience. The best way to track and achieve your web performance goals is through experience-based SLOs (Experience Level Objectives, or XLOs). Get it wrong, and you risk losing sales during the holiday shopping rush—something we saw happen during Black Friday.  

Holiday revenue at stake

This year, the National Retail Federation projects 2024 holiday sales will reach record levels, up to $989 billion, with growth of 2.5% to 3.5% over last year. According to a recent study, the upward trend of online shopping will continue, as more than 90% of shoppers go online, and over 40% planning to do most or all their holiday shopping online.

Don’t be fooled by Availability

Most web Service Level Objectives (SLOs) are based on simple availability: Is your website up or down? But that doesn’t give you a good view of the performance users are actually experiencing at their locations. During the holiday shopping season, increased traffic can cause congestion and performance issues that don’t impact your service availability but can significantly harm customer experience.  

As our upcoming SRE Report 2025 confirms “Slow is (officially) the new down.” Users won’t wait for poor web performance—they get frustrated and bounce. Setting XLOs for performance metrics provides early warnings about negative trends that can impact business long before you reach an alert threshold.

To set and track performance goals on user experience, you need to measure performance metrics, like Core Web Vitals, from real locations—not just from the data center or cloud, where your customers aren’t. This is a key requirement for XLOs and the main factor that differentiates an SLO from an XLO. It’s the best way to measure web performance against realistic goals.  

A Tale of Two Metrics

To illustrate this point, consider two similar competing websites. We’ll call them Company_A and Company_B to avoid public shaming. We’ve set both an availability and a performance XLO for them. The performance XLO is based on Largest Contentful Paint (LCP), a Core Web Vital metric that helps indicate when the main content of a web page has likely loaded, making the page ready for user interaction.

Availability

The figures below show the availability burndown charts for Company_A and Company_B for the week of Thanksgiving through Black Friday and Cyber Monday. For both companies, the XLO was leniently set at 99.9% availability.  

As shown in the first chart, Company_A experienced a 6-minute outage on Black Friday evening. The outage wasn’t major enough to violate the overall objective, but it was unfortunately timed. A deeper analysis revealed web timeout failures for customers in Dallas, Denver, and Seattle, as they waited for servers to respond. Customers in these locations may gone to Company_B’s website instead, resulting in lost revenue for Company_A.

A graph on a computer screenDescription automatically generated

The second chart shows the availability burndown for Company_B. There were no outages during this time, so no XLO violations occurred, and the 99.9% objective was easily achieved. Looking at this alone, you might think all of Company_B’s customers were satisfied—but you would be wrong.

A screen shot of a graphDescription automatically generated

Performance: Largest Contentful Paint

The burndown charts for LCP below tell a different story. A good LCP score is 2.5 seconds or less. The XLO was set at 75% adherence for 2.5 seconds. That means for the majority of customers (or 75% of the time), the largest element rendered on the site happened within 2.5 seconds, providing a good user experience. This may seem lenient, but a 75th percentile is recommended for this Core Web Vital.

The first burndown chart shows Company_A easily beat the XLO objective, providing most customers a good user experience. This doesn’t include outages, so it only applies to users who successfully accessed their website.  

A graph showing a number of paintDescription automatically generated with medium confidence

Company_B, on the other hand, showed consistently slow LCP and missed their XLO before the Black Friday weekend was over.  

A graph showing a number of paintDescription automatically generated with medium confidence

A closer look at the scatterplot below shows that the LCP was often greater than 4 seconds. The black horizontal line represents the 2.5 second mark, making it clear how this objective was regularly missed throughout the major shopping week.  

A graph with blue dotsDescription automatically generated

Note that LCP isn’t necessarily when the web page is fully interactive, only that the largest object has rendered. A deeper analysis shows the full measure of Time To Interactive (TTI) for Company_B was often above 8 seconds when LCP was high. That level of poor performance was found across the entire month of November, not just Black Friday through Cyber Monday. Users experiencing that poor performance are typically frustrated and at risk of bouncing—likely to the competitor, Company_A.  

A graph showing a number of dotsDescription automatically generated

Wrapping it up

Measuring web performance from real locations is vital for setting realistic XLOs. As shown here, both companies maintained availability over 99.9% (despite Company_A’s limited outage), but only Company_A met their performance objective, offering a better user experience overall.

While Company_B might have congratulated themselves on 100% availability, the performance XLO shows they provided a suboptimal user experience for 25% of their customers for the entire high-value shopping period. This would have had a broader impact on user experience and, consequently, on revenue than a brief outage in a limited set of locations.  

This disparity highlights the importance of focusing on performance metrics like LCP, which directly impact user satisfaction. Availability alone can be misleading; it’s not enough to represent user experience. While both companies had issues during the peak holiday shopping period, the performance XLO suggests that Company_B fared worse.

The best way to avoid failing the peak shopping season is to set both availability and performance-based XLOs. Burndown charts, like those above, can help you project whether you’re on track to meet or miss your performance objectives from a real customer perspective. Ultimately, that impacts revenue. Given how much is at stake during the holiday shopping period, customer experience must be a top priority.

To learn more about how we can help you stay resilient during peak traffic periods, check out our Internet Resilience Program

This is some text inside of a div block.