for example, usiI’ve come across that even professionals who get paid to build websites have absolutely no idea how to make websites load faster. So I wrote a short article about technologies that have been with us for a few years but remain unus.
The first two are gzip and brotli.
It was and still is the case that the more data is transferr between the server and the client, the longer the transfer takes. So many years ago, compressible content began to be compress in transit. It has long us and still uses good old gzip for this.
If you have Apache on your server, then it’s very likely that you’re compressing content without even knowing it, because by default it’s set to:
So you see that safely compressible content is being compress
The only problem with gzip is that it is old. So, years ago (in 2013 to be precise), developers at Google develop a new compression algorithm call brotli. It is vietnam phone number data faster than gzip, compresses better and uses less resources.
Well, now an example in practice. I download the Builder from jQuery UI – and upload it to two different directories on our test server.
At first glance, it can be seen that while gzip manag to ruce the content to 250KB and it took 1.215s to load the page, brotli ruc the transferr data each profile must have a photo to avoid appearing fake volume to 236KB and it took 1.061s to load the page.
The difference between the two pages is that the following rules have been add to the .htaccess for brotli:
This puts an end to compression
even if only in appearance. Another thing from the Google developer workshop is the WebP format. Again, this is nothing new, it has been out since 2010. Here I prepar a somewhat more drastic example. I upload ten .jpg files straight cmo email list from the camera to the directory to demonstrate the stark difference between JPEG and WebP. I compress the files with default settings (lossy compression, 75% quality) with cwebp CLI utility -ng the whois command (inetnum field).