The impact of removing jQuery on our web performance
11–20 of 283 posts
Re: The impact of removing jQuery on our web performance
#12Has anyone noticed how all UK government websites like https://www.gov.uk/ , https://www.nhs.uk/ , https://tfl.gov.uk/ , https://coronavirus.data.gov.uk/ have the same look-and-feel and the same UX? Are there more such examples of countries that have uniform UX for their government websites?
Bonus: The ONS has some pretty smashing data visuals https://www.ons.gov.uk/peoplepopulationandcommunity/healthan...
Re: The impact of removing jQuery on our web performance
#13How does browser caching come into play here? Doesn't it make a difference?
Re: The impact of removing jQuery on our web performance
#14Er... the utility of jQuery in 2022 aside, I would say: if it equates to a lot of data when it's on every page (of a single website), you're doing something wrong?! I mean, caching content between different domains is not a thing anymore, but on the same domain jQuery should only be loaded once?
Re: The impact of removing jQuery on our web performance
#15Has anyone noticed how all UK government websites like https://www.gov.uk/ , https://www.nhs.uk/ , https://tfl.gov.uk/ , https://coronavirus.data.gov.uk/ have the same look-and-feel and the same UX? Are there more such examples of countries that have uniform UX for their government websites?
They're built using the gov.uk design system[0], which is not just a CSS framework! It also has a lot of guidelines and requirements to make sure that the pages you're building are accessible to everyone https://design-system.service.gov.uk/
Re: The impact of removing jQuery on our web performance
#16Has anyone noticed how all UK government websites like https://www.gov.uk/ , https://www.nhs.uk/ , https://tfl.gov.uk/ , https://coronavirus.data.gov.uk/ have the same look-and-feel and the same UX? Are there more such examples of countries that have uniform UX for their government websites?
- The UK: https://design-system.service.gov.uk/
- The US: https://designsystem.digital.gov/
- Canada: https://www.canada.ca/en/government/about/design-system.html
- Argentina: https://argob.github.io/poncho/
- Italy: https://designers.italia.it/
- Singapore: https://www.designsystem.tech.gov.sg/
- Estonia: https://brand.estonia.ee/
Re: The impact of removing jQuery on our web performance
#17Has anyone noticed how all UK government websites like https://www.gov.uk/ , https://www.nhs.uk/ , https://tfl.gov.uk/ , https://coronavirus.data.gov.uk/ have the same look-and-feel and the same UX? Are there more such examples of countries that have uniform UX for their government websites?
Re: The impact of removing jQuery on our web performance
#18Deleted.
And with HTTP2 it doesn't really matter if you have more than 8 resources.
I doubt query selectors will have any meaningful impact on page load
Re: The impact of removing jQuery on our web performance
#19Earlier quoted context omitted.
They all use this design system: https://design-system.service.gov.uk . It's much more than just a CSS framework, it's full specifications on how to implement easy to follow and sensible UX. I wish there was more buy in by local councils of this system, there are some incredibly poor local government sites.
I imagine a buy-in by local councils is just that - a cost. And most councils are either poorly funded, poorly managed financially or both!
Plus the (at times) antagonistic relationship between Whitehall and local government I think means they don't want to necessarily use something they associate with the incumbent administration.
Re: The impact of removing jQuery on our web performance
#20When I did web development, I specifically loaded JS lazily so first you got a pure HTML page with just a few lines of code. Those lines of code are normal (not jQuery) JS that loads the rest of the JS lazily in a progressive enhancement. This means the page can start being rendered before the jQuery code loads. But in fact, jQuery is largely not needed since Internet Explorer lost market share and there's less of a…
If done properly this can be nice but a common grief is when interactive elements (input fields/buttons/links, including in flowing text) move around after first becoming visible. The worst is input fields that get cleared or grabbing focus (this is way too common; not stellar to have to password reset due to typing half a password in an auto-complete search field) as part of this process after the user has already s…