matters — we all know it. However, do we actually always know what our bottlenecks exactly are? Is it expensive JavaScript, slow web font delivery, heavy images, or sluggish rendering? Is it worth exploring tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, clients hints, CSS containment, HTTP/2 and service workers? And, most importantly, where do we even improving and how do we establish a culture long-term?



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here