As the world’s consumers move to the web, the importance of user experience management increases. Shopping cart abandonment rates are at an all-time high, despite greater functionality and offerings of e-commerce sites. Learn how to combat growing abandonment rates and protect your online sales.
A challenge for monitoring Silverlight is creating browser-driven monitoring scripts that mimic end user actions that won’t break due to the dynamic nature of Silverlight. In fact, many advanced monitoring solutions that use browsers won’t succeed in running a monitoring script through a rich interactive Silverlight application. In order to monitor Silverlight (or any RIA) an additional level of technical sophistication – beyond only a browser-driven monitoring script – is often needed.
Flash Monitoring for Web Performance – Adobe Flash has played an important role in making the Internet a more engaging, interactive place. It serves as one of the preeminent Web 2.0 Rich Internet Applications (RIAs) by allowing enterprises to deliver a high quality on-line experience. Web designers use Flash to incorporate active and interactive content like video and animations. Flash continues to be important driver behind appealing web content and unique user experiences.
However, properly monitoring Flash to ensure users have a consistently compelling user experience, presents a challenge.
Website Uptime isn’t a Condition, it’s a Calculation
Central to service level agreement (SLA) reports is the concept of website “uptime.” However, what exactly is uptime? Website uptime, in the recent past was often narrowly defined as the working vs. non-working condition of a web server, ie web server uptime. More recently, we have worked with many organizations that are carefully defining the details of website uptime vs. downtime, by taking into account variables like network uptime, server uptime, web application uptime, or website uptime, has become critical.
Do you have a true user’s view of your web application performance when an error occurs? Because if you don’t have web application monitoring with video capture — if all you see when an error occurs is an error code — then you’re in trouble.
If every web application monitoring error diagnostic is based on reading web application code — and not seeing an actual video of the web application at the time of the error, then you are not seeing your customers’ experience of your web application – and that’s a problem. If you aren’t viewing a web application performance video you aren’t seeing your web application through your user’s eyes, no matter how hard you try or how much code you read.