Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Dana Gardner, Elizabeth White, Liz McMillan, Zakia Bouachraoui

Related Topics: @DevOpsSummit, Java IoT, @CloudExpo

@DevOpsSummit: Blog Feed Post

How Fast Is Fast Enough? By @Lounibos | @DevOpsSummit #APM #DevOps

How do you know when the site or app you’re building has achieved mythical “fast enough” status?

When It Comes to Delivering the Best Possible User Experience, How Fast Is Fast Enough?

Last month I spoke at the Conversion Conference, and after my talk I met a developer who had been tasked with single handedly making her company’s site faster. We talked for quite a while, and she expressed good-humored frustration at the vagueness of this directive.

Some of the things we talked about:

  • What does “faster” mean?
  • Who defines “fast” within an organization?
  • How do you know when the site or app you’re building has achieved mythical “fast enough” status?
  • And how do you respond when the same people who tell you to make the site faster are also adding images, features, and scripts that are killing performance?

Today I’m going to try to answer these questions… and hopefully help lay to rest any anxiety you’ve been feeling if you’ve been given a similarly vague directive.

What’s the ideal page load time?
Depending on whom you ask, you’ll get a different answer…

100 milliseconds?

Usability expert Jakob Nielsen has been testing people’s reactions to varying response times since 1993. The results are unchanging over the years: load times of 1oo milliseconds or less give us the most satisfying illusion of instantaneous response. This illusion is crucial to maintaining “flow” — a task state of maximum productivity coupled with personal well-being. (“Flow” is a concept popularized by psychologist Mihaly Csikszentmihalyi, who explains it really well in this TED talk.)

1 second?

Google has been pursuing a slightly less aggressive — but still ambitious — goal of pushing that pages should render in 1000 milliseconds or less. This is largely driven by the need to serve faster, less bandwidth-intensive pages to mobile users.

2 seconds?

User surveys are interesting, because they serve as a barometer of what people believe they want. For instance, according to one Akamai survey, 47% of consumers expect web pages to load in 2 seconds or less.

web performance and user expectations

More?

Similarly, if you ask the people responsible for creating and maintaining websites how fast they think their pages should be, you’ll get a mixed bag of responses. In this thread on a discussion board for marketing professionals, one commenter said that “I myself wouldn’t consider it very important. Granted if page is too slow it’s loses users, but I believe if page is loading in 5 or 6 seconds it doesn’t make much difference

There’s no single right answer
That’s because there’s no one-size-fits-all number that applies to every user and every website. Your own patience threshold varies throughout the day, depending on whether or not you’re in a hurry, how tired or hungry you are, what kind of site you’re on, how distracting your environment is, and countless other variables.

Here are a few examples to illustrate the variability of user expectations…

People are more willing to be patient with specialty sites than with sites selling general merchandise.

We looked at data from two ecommerce sites: one of which sells specialty goods and the other of which sells general merchandise. As the graphs below illustrate, when pages slow down, both bounce rate and conversions suffer much more for the general merchandise retailer than for the specialty shop.

website performance monitoring: speciality versus general merchandise

website performance monitoring: general versus specialty ecommerce

People are more patient at some points in the sales funnel than they are at others.

Looking at more real user data, we can see that for a typical ecommerce site, the conversion rate drops by up to 50% when the load time for “browse” pages increases from 1 to 6 seconds:

website performance monitoring: load times while browsing

But looking at the same set of user data, we see that the impact on conversion rate is much less when checkout pages degrade in speed:

website performance monitoring: checkout load times

Visitors in some countries are more patient than visitors in others.

Breaking down user data by geography, we found that, when faced with slower load times, people in Australia were much less likely to bounce than visitors in the US.

website performance monitoring: bounce rate by geography

Sometimes, making the user interface TOO fast is a problem.

Admittedly, this is so rare that I hesitate to mention it, but according to Jakob Nielsen, about 1% of the time the user interface is too fast. In the example that Nielsen cites, UI elements loaded so quickly that the user didn’t notice that they were still loading as she tried to interact with the page. As a result, she repeatedly clicked on the wrong page element as her intended target kept moving.

The Sophie’s choice of performance optimization
All the examples I just cited serve to illustrate that, while having the goal of making every page as blazingly fast as possible is simple and makes you feel like a performance superhero, it may not always be necessary — or even helpful. If, for example, you know that your Australian shoppers don’t seem to care whether pages render in 2 seconds or 5 seconds, why invest in optimizing pages for that audience, when you’d be better served by investing in your much less patient US shoppers?

Yes, there’s the idealistic, altruistic argument that we should serve the best, fastest user experience to all visitors. But sometimes you have to make a Sophie’s choice about where to invest your limited resources. You need data to help drive those hard choices.

So how do you determine what’s “fast enough” for your site?
The only way to answer the question “how fast is fast enough?” is to come up with a set of metrics for “fast enough” that work for your company and your visitors. Here’s a quick guide to getting started.

1. Measure
I’ve read scores of case studies about the impact of performance on business and user experience metrics for great companies, ranging from retail mega-entities like Walmart to smaller “mortal” companies like Smartfurniture.com and Edmunds.com. I love these case studies because they shine tons of light onto the business value of performance. But none of these case studies shine light on your website and your visitors. That’s why you need to collect and analyze your own user data.

The best tool for measuring (and then proceeding to the next steps: correlating and monitoring) your website’s performance is a real user monitoring solution, which gathers data about every user who visits your site. In addition to the usual page metrics — such as load time, etc. — real user monitoring can teach you a great deal about how people use your site, uncovering insights that would otherwise be impossible to obtain. There are a number of paid and open-source RUM tools on the market, though I’m partial to mPulse.

Read the original blog entry...

More Stories By SOASTA Blog

The SOASTA platform enables digital business owners to gain unprecedented and continuous performance insights into their real user experience on mobile and web devices in real time and at scale.

@DevOpsSummit Stories
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
"We do one of the best file systems in the world. We learned how to deal with Big Data many years ago and we implemented this knowledge into our software," explained Jakub Ratajczak, Business Development Manager at MooseFS, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
All zSystem customers have a significant new business opportunity to extend their reach to new customers and markets with new applications and services, and to improve the experience of existing customers. This can be achieved by exposing existing z assets (which have been developed over time) as APIs for accessing Systems of Record, while leveraging mobile and cloud capabilities with new Systems of Engagement applications. In this session, we will explore business drivers with new Node.js apps for delivering enhanced customer experience (with mobile and cloud adoption), how to accelerate development and management of SoE app APIs with API management.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.