{"id":7308,"date":"2019-10-17T13:30:50","date_gmt":"2019-10-17T18:30:50","guid":{"rendered":"https:\/\/dcmblogmulti.wpengine.com\/?p=7308"},"modified":"2026-08-28T02:30:57","modified_gmt":"2026-08-28T02:30:57","slug":"network-throttling-monitor-the-user-experience","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/network-throttling-monitor-the-user-experience\/","title":{"rendered":"Network Throttling: Monitor the User Experience"},"content":{"rendered":"
When it comes to monitoring web application performance, not only is it necessary emulate user actions, but also network conditions of end-user devices. Network throttling allows you to control connection speeds to better match the experience of real users, allowing you to see web application behavior in specific network conditions. Network connections can vary for many reasons. User location, device type, and browser used are just a few factors that can affect a user\u2019s experience.<\/p>\n
Users can access your websites, services, and applications using any combination of devices, browsers, and connections, from anywhere in the world, so setting up a monitoring device that mirrors the user\u2019s experience is critical. This is why network throttling is so important. For example, network connections of the device you use for recording a monitoring script can be faster than the network connection of a real end user.<\/p>\n
| \n \n<\/td>\n | Download<\/strong><\/td>\n| Upload<\/strong><\/td>\n | Latency<\/strong><\/td>\n<\/tr>\n | Slow<\/strong><\/td>\n | 0.25Mbps<\/td>\n | 0.05Mbps<\/td>\n | 300ms<\/td>\n<\/tr>\n | Average<\/strong><\/td>\n | 1Mbps<\/td>\n | .5Mbps<\/td>\n | 100ms<\/td>\n<\/tr>\n | Fast<\/strong><\/td>\n | 20Mbps<\/td>\n | 10Mbps<\/td>\n | 20ms<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n | <\/p>\n Learn more about enabling network throttling within the Dotcom-Monitor platform<\/a>.<\/p>\n |