Understanding the critical rendering path - 2017-10-09
- 0-100ms - instant feel
- 100-300ms - slight perceptible delay
- 300-1000ms - loss of task focus, perceptible delay
- 1s+ - mental context switch
- 3s+ - user leaves
Modern high-traffic websites must serve hundreds of thousands, if not millions, of concurrent requests from users or clients and return the correct text, images, video, or application data, all in a fast and reliable manner.
This is a guide that anyone could use to learn about the practice of front-end development. It broadly outlines and discusses the practice of front-end engineering: how to learn it and what tools are used when practicing it in 2017
This course covers how to analyze your web pages to make sure they are following known performance best practices.
“How could I organize my code?”, “What is the best way to design this?”, “How can I make my application more modular?”, “How do I handle a set of asynchronous call effectively?”, “How can I make sure that my application will not collapse while it grows?”.
If you have such questions without answers, that book is definitely for you!
The aim of this book is to guide you through this emerging world of patterns, techniques and practices, showing proven solution to the common problem.
To rock the interview to achieve what you deserve and to improve your concepts about front end technologies, I have consolidated a list of questions and answers. It’s a one stop solution for front end interview process.
One of the biggest mistakes I see when looking to optimize existing code is the absence of the debounce/throttle function. Both of them are ways to limit the amount of JavaScript you are executing based on DOM events for performance reasons. But they are, you guessed it, different.
Is it faster to use the native forEach or just loop with for?
What is the most reasonable approach?