Speed Tracker
Track response times to the millisecond across every endpoint. See historical trends, set custom thresholds, and get alerted the moment performance degrades.
Historical analysis
Switch between time ranges to see how your response times change throughout the day, across a week, or in the last hour. Hover over any bar to see the exact millisecond value. The chart colour-codes each check: blue for normal, amber for warning, red for critical.
Most performance problems are intermittent. Your site runs fine at 3am when traffic is low, then slows to a crawl during the morning rush. The 24-hour view shows you exactly when degradation starts and how long it lasts, so you can correlate it with deployments, traffic spikes, or third-party service issues.
Combine response time data with uptime monitoring to see whether slowdowns eventually lead to full outages. If your P95 creeps above 1 second for three consecutive checks, Pulse Stack can fire an alert through any of 16+ channels including Slack, PagerDuty, or SMS.
Drag the sliders to set warning and critical thresholds. Watch how different levels classify the same set of requests.
4
Normal
4
Warning
2
Critical
Where your response times actually land
Half of all requests complete faster than this
75% of requests are faster
90% of requests are faster
The threshold most SLAs reference
Only 1 in 100 requests is slower
Averages lie. If 99 requests take 100ms and one request takes 10 seconds, the average is 199ms. That looks acceptable. But one in every hundred users waited ten seconds. Percentile-based monitoring tells you what your users actually experience. The P95 is what SLA contracts reference because it represents the worst experience for 95% of your traffic.
Set your thresholds based on percentiles, not averages. A P95 of 500ms means 95% of users get a fast experience. If the P95 suddenly jumps to 2 seconds, you know 5% of your traffic is having a terrible time, even though the average might still look fine. That is the kind of insight that keeps customers loyal.
Every monitor in Pulse Stack lets you set independent warning and critical thresholds. A payment API might need a 200ms critical threshold because customers abandon checkout flows when they stall. A background reporting endpoint might tolerate 3 seconds without anyone noticing.
Configure thresholds per monitor, then connect them to your incident management workflow. When a critical threshold is breached, Pulse Stack creates an incident, posts to your status page, and alerts your on-call team through whichever channel they prefer.
Response time monitoring is included in every plan. Free for 50 monitors.
Performance is not a vanity metric. Every 100ms of additional latency has a measurable impact on conversions, bounce rates, and search rankings.
Research across e-commerce and SaaS platforms consistently shows the same pattern: as page load time increases from 1 second to 3 seconds, the probability of bounce increases by 32%. At 5 seconds, the bounce probability is 90%. Every additional 100ms of load time costs roughly 1% in conversion rate.
These numbers apply to your API endpoints too. When a checkout form takes 3 seconds to submit instead of 300ms, users assume it failed and hit the button again, creating duplicate orders. When a search endpoint is slow, users abandon it and go to a competitor. Response time monitoring catches these problems the moment they start, not when your revenue report shows a dip three weeks later.
Load time vs bounce rate
SaaS platforms typically respond in under 200ms. E-commerce sites average around 320ms. Government sites? Often above 800ms. Knowing your industry benchmark lets you set realistic thresholds and understand whether your performance is competitive.
Pulse Stack tracks your response times from 10+ global locations simultaneously. If your London users get 150ms response times but Singapore users experience 800ms, that is a CDN or routing problem you can fix. Check latency per region through the Global Watch Network.
Industry average response times
Google has used page speed as a ranking factor since 2010 and expanded it to mobile in 2018. Core Web Vitals, including Largest Contentful Paint and Interaction to Next Paint, directly impact your search visibility. A slow site does not just lose users directly; it also loses the traffic that would have come from search results.
Monitoring response times is the foundation. If your server takes 2 seconds to respond before the browser even starts rendering, no amount of frontend optimisation will save your Core Web Vitals scores. Use response time monitoring alongside SSL monitoring and DNS monitoring to cover every layer of your site speed stack.
Speed stack layers
Pulse Stack monitors the first four layers
50 monitors free forever. Response time tracking included in every plan.
Most popular
£29/month
All plans include response time tracking, incident management, and public status pages. Full plan comparison →
Response time monitoring works best alongside these other checks.
Everything you need to know about response time monitoring.
Response time monitoring for every endpoint. Free for 50 monitors, no credit card required.
Start tracking speed free