These tags can be styled in all sorts of flexible ways via CSS, and recreate most of the JS versions I've seen out there.
Summary of key points
Takeaway: Examine the functionality of your site and see where there might be opportunities to reduce reliance on large Javascript libraries where there are native HTMLCSS options.
Key point: Remember that the issue is not the size portugal mobile database of the JS file, but the number of round trips required.
Note: There are some cases where you should use a JS solution, but it's important to weigh the pros and cons.
network
Every time a browser has to gather a resource from a server, it has to send a message across the internet and back; this speed is limited by the speed of light. It may sound a little ridiculous, but this means that even small requests can increase the time it takes for a page to load. There are things we can do to help shorten the distance these requests travel or reduce the number of round trips required. These methods are more specialized, but can achieve some real results.
TLS 1.3
TLS or SSL is the encryption technology used to secure S connections. Historically, it took two round trips between the browser and the server to set up the encryption - if the user is 50ms away from the server, that means 200ms per connection. Remember that Google has historically recommended a 200ms target for delivering HTML this seems to have been slightly relaxed in recent updates; you're losing a lot of time here.
The recently defined TLS 1.3 standard reduces this from two round trips to one, which could potentially save some valuable time on the user's initial connection to your site.