Remove jQuery From GOV.UK Performance Removing jQuery from GOV.UK resulted in a 10% decrease in web performance, when compared to the same site without jQuery. There are a few potential causes for this decrease in performance, some of which can be attributed to the way that jQuery is used. For example, when displaying images, jQuery can slow down the display of the images by caching the images. This can lead to a 10% decrease in performance, when compared to the

In the first blog post we covered "How and why we removed jQuery from GOV.UK", let’s now turn our attention to what performance difference it has made for users. Please read that blog post before this one. Therefore, a 32 Kb image has much less of a performance impact than 32 Kb of compressed JavaScript. Improving web performance is often made up of lots of smaller incremental changes over time. So it’s been great to see support for this change from the wider web performance community. With that assumption in mind, what performance impact will removing 32 kB of compressed JavaScript have? As you can see from our performance monitoring results above, we have improved page performance for many users who struggle on low specification devices and slow connections, even though GOV.UK is already a very quick website for the majority of users. As mentioned previously, the jQuery library was only 32 Kb of compressed and minified (when white space removed from code and repeated words substituted) JavaScript. (). Continue reading.

Related Hacker News news

You may also be interested in Exoplanets Ferrari CompuServe Telegram Acura Radio Publishing Diabetes