Performance matters — we all know it. However, do we actually always know what our performance 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 start improving performance and how do we establish a performance culture long-term?
from Articles on Smashing Magazine — For Web Designers And Developers http://ift.tt/2Cjn44I via http://ift.tt/1M61DFR
from Tumblr http://ift.tt/2lPfWXt
No comments:
Post a Comment