“Make fewer calls.” It’s one of the first suggestions for #webperf engineering and web design. “If you want your application to go fast, you should first try to make fewer requests.” Oh cool! So, you can go fast by doing less … and less … and less? Until you reach point where the application is doing almost nothing? But then it will be instantaneously responsive at its working … doing nothing. That’s insane, of course because everyone is doing the opposite. We add more functions, more features, more coverage, more user communities and we grow the data by leaps and bounds. Performance problems are found because we do MORE, not LESS.
My objective in this web performance workshop is to review the core principles guiding the modern #webperf trends and expand on them. I’ll share some deeper perspectives on how to solve performance problems beyond the simple things a web developer might do. We’ll dig into the technical elements and architectural implications and develop your robust understanding of web performance beyond the basics.
