CS420 Weeks 7-14

let's say you accidentally, introduce a performance issue, that causes your page to take an extra half second to load. That's just 500 milliseconds.

That's a pretty small difference.

What kind of difference, in user engagement ,do you think this would cause?

Example

Many well publicized studies from Google,

show that UI performance translates directly to profit. A drop in performance directly drives a drop in user engagement. In short, speed is not a feature, it's a requirement. Users won't use your app if it's not fast.

It is

a requirement

Of course, it's nearly impossible to graph performance into your application after it's already been built, but before we get into good performance patterns, the first step to insuring great performance, is being able to analyze your performance