Traduzir "http compression makes" para holandês

EN A bar chart showing the usage rates of different compression algorithms for HTTP responses. 77.39% of HTTP responses that use compression employ the Gzip algorithm, 22.59% use Brotli, and 0.03% use some other method.

• bar chart showing
• responses
• algorithm
• Brotli

EN More importantly, since HTTP/3 uses QUIC (hence UDP) where prior versions of HTTP use TCP, HTTP/3 will always be at a different endpoint from the HTTP/1.x and HTTP/2 service.

• importantly
• since HTTP
• uses QUIC
• hence UDP
• TCP
• HTTP

EN There are two common types of image compression techniques. These are the lossy compression and the lossless compression.

• two common types
• image compression techniques
• lossy compression
• lossless

EN Text compression is widely used for the relevant formats, although there is still a significant percentage of HTTP responses that could benefit from additional compression

• formats
• responses that could
• additional compression

EN Using HTTP compression makes a website load faster and therefore guarantees a better user experience

• HTTP compression makes
• website load faster
• user experience

EN Running no compression on HTTP makes for a worse user experience, may affect the growth rate of the related web service, and affects search rankings

• Running no compression
• worse user experience
• affect the growth
• related web service
• affects search rankings

EN Compression techniques as used in ZIP are called no-loss compression, because it is possible to extract the original files from the compressed version without any loss of information

• ZIP are called
• compression
• extract the original
• compressed version without

EN Low-loss compression methods are often used in picture compression as with the JPG format

• Low-loss compression methods
• JPG format

EN There haven been developed specific compression algorithms for voice compression which feature low-loss combined with a very small bandwidth allocation

• haven been developed
• compression which feature
• small bandwidth allocation

EN compression, the quality difference between the image before and after compression is almost invisible. Generally speaking, only superfluous meta information is removed from the image file to save unnecessary kilobytes. With

• compression
• quality difference between
• image before
• invisible
• Generally speaking
• file to save
• kilobytes

EN compression, the image quality may suffer due to a reduction of colors and resolution. On the other hand, lossy compression can save significantly more file size.

• compression
• colors
• resolution
• hand
• significantly more file

EN ShortPixel is an image compression plugin that you can install and forget about. Image compression is important to make your site faster and this will make a huge difference.

• install
• site faster
• huge

EN Compression techniques as used in ZIP are called no-loss compression, because it is possible to extract the original files from the compressed version without any loss of information

• ZIP are called
• compression
• extract the original
• compressed version without

EN Low-loss compression methods are often used in picture compression as with the JPG format

• Low-loss compression methods
• JPG format

EN There haven been developed specific compression algorithms for voice compression which feature low-loss combined with a very small bandwidth allocation

• haven been developed
• compression which feature
• small bandwidth allocation

EN This codec, also developed by Fraunhofer, is based on an improved compression and loses less audio quality during compression.

• codec
• developed by Fraunhofer
• compression
• loses less audio
• during

EN Brotli is a new open-source data compression algorithm that offers better compression ratios than existing techniques

• open-source data compression
• offers better compression
• existing techniques

EN While lossy compression is often acceptable for images and other media types, for text we want to use lossless compression, i.e. recover the exact text after decompression.

• While lossy compression
• media types
• text we want
• lossless compression
• recover the exact
• after

EN It is surprising that while all those content types would profit from compression, the range of percentages varies widely over the different content types: only 44% use compression for text/html against 93% for application/x-javascript.

• surprising that while
• those content types
• profit from compression
• range of percentages
• content types
• compression for text

EN This breaks down what compression methods, if any, are used for all the content types which are images. For all three image types, i.e. jpeg, png and gif, around 96.5% use no compression is used.

• methods
• images
• three image types
• jpeg
• png
• gif

EN For dynamically compressed resources, we need to choose the compression levels such that compression takes less time than the time difference between sending an uncompressed versus a compressed file

• dynamically compressed resources
• choose the compression
• compression takes less
• difference between sending
• file

EN The color of each box represents how many of these resources were served compressed, orange indicates a low percentage of compression while blue indicates a high percentage of compression

• color of each
• resources were served
• percentage of compression

EN However within the responses that do use compression, for first parties, the ratio of Brotli compression is only 18%, while the ratio for third parties is 27%.

• compression
• parties
• ratio of Brotli
• while the ratio

EN The text compression audit evaluates whether a site can benefit from additional text-based compression

• text compression audit
• whether a site
• benefit from additional
• compression

EN HPACK header compression is replaced with QPACK, which allows manual tuning of the compression efficiency versus HOL blocking risk tradeoff, and the prioritization system is being replaced by a simpler one

• HPACK header compression
• replaced with QPACK
• allows manual tuning
• compression efficiency versus
• blocking risk tradeoff

EN Cache system, Gzip compression, minify, group resources, database optimization, image lazy loading and compression; all the tools to load your pages blazing fast

• Cache system
• Gzip compression
• minify
• group resources
• database optimization
• image lazy loading
• compression
• tools to load
• pages blazing fast

EN HTTP: This will route from HTTP, usually to the same HTTP. If used with HTTPS on the right side, it may cause errors to occur.

• HTTP
• route from HTTP
• used with HTTPS
• right side

EN HTTP Secure (HTTPS) is the safe version of the Hypertext Transfer Protocol (HTTP) for secure online transactions. It is easy to see the difference because with the protocol HTTP, URLs start with

• HTTP Secure
• HTTPS
• Hypertext Transfer Protocol
• HTTP
• secure online transactions
• protocol HTTP

EN HTTP: This will route from HTTP, usually to the same HTTP. If used with HTTPS on the right side, it may cause errors to occur.

• HTTP
• route from HTTP
• used with HTTPS
• right side

EN HTTP Secure (HTTPS) is the safe version of the Hypertext Transfer Protocol (HTTP) for secure online transactions. It is easy to see the difference because with the protocol HTTP, URLs start with

• HTTP Secure
• HTTPS
• Hypertext Transfer Protocol
• HTTP
• secure online transactions
• protocol HTTP

EN HTTP/3 is the latest version of HTTP, and it builds upon the success of HTTP/2 by adding several new features and improvements

• HTTP
• improvements

EN As the HTTP protocol has evolved, the semantics of HTTP have stayed the same; there have been no changes to the HTTP methods (such as GET or POST), status codes (200, or the dreaded 404), URIs, or header fields

• semantics of HTTP
• stayed the same
• methods
• POST
• status codes
• dreaded
• URIs
• header fields

EN Last year?s analysis of HTTP Archive data showed that HTTP/2 was used for over 50% of requests and, as can be seen, linear growth has continued in 2020; now in excess of 60% of requests are served over HTTP/2.

• Last year
• analysis of HTTP
• showed that HTTP
• requests
• seen
• served over HTTP

EN Is there any difference in which content-types are served over HTTP/2 or gQUIC? Figure 22.8 shows, for example, that 90% of websites serve 100% of third party fonts and audio over HTTP/2 or gQUIC, only 5% over HTTP/1.1 and 5% are a mix

• served over HTTP
• gQUIC
• Figure shows
• example
• party fonts
• audio over HTTP
• HTTP
• mix

EN As discussed in the HTTP/1.0 to HTTP/2 section, HTTP/2 multiplexes multiple different streams on top of one connection

• HTTP
• section
• multiplexes multiple different

EN Since QUIC and HTTP/3 run over UDP, things aren?t as simple as with HTTP/1.1 or HTTP/2

• Since QUIC
• HTTP
• run over UDP
• things aren

EN This likely will have to be done for each domain separately, which will probably lead to most page loads using a mix of HTTP/1.1, HTTP/2, and HTTP/3.

• done for each
• separately
• mix of HTTP
• HTTP

EN Most likely, we will continue to see a healthy mix of HTTP/3, HTTP/2, and even HTTP/1.1 on the web for years to come.

• likely
• HTTP
• even HTTP
• web for years

EN Home pages have seen a 13% increase in HTTP/2 adoption, leading to an even split of pages served over HTTP/1.1 and HTTP/2

• increase in HTTP
• adoption
• split of pages
• HTTP

EN We use optimised HTTP/2 for SSL, which ensures that your WordPress websites load much faster through compression, improved data transfer and server push.

• optimised HTTP
• SSL
• websites load much
• compression
• improved data transfer
• server

EN No optimization hassle anymore. Caching, server-side compression, HTTP/2 and PHP7 are already pre-installed.

• optimization hassle anymore
• Caching
• server-side compression
• HTTP
• already

EN Our websites use the latest web technologies, including free SSL, PHP 7, HTTP/2 and Brotli compression as standard.

• web technologies
• free SSL
• PHP
• HTTP

EN HTTP/2 supports header compression, intelligent packet streaming management, query multiplexing and priority

• HTTP
• supports header compression
• intelligent packet streaming
• query multiplexing
• priority

EN HTTP/2 supports header compression, intelligent packet streaming management, query multiplexing and priority

• HTTP
• supports header compression
• intelligent packet streaming
• query multiplexing
• priority

EN HTTP/2 supports header compression, intelligent packet streaming management, query multiplexing and priority

• HTTP
• supports header compression
• intelligent packet streaming
• query multiplexing
• priority

EN HTTP/2 supports header compression, intelligent packet streaming management, query multiplexing and priority

• HTTP
• supports header compression
• intelligent packet streaming
• query multiplexing
• priority

EN HTTP/2 supports header compression, intelligent packet streaming management, query multiplexing and priority

• HTTP
• supports header compression
• intelligent packet streaming
• query multiplexing
• priority

EN You can pursue the HTTP/2 and Compression chapters for more information on the life of a modern request.

• pursue the HTTP

EN Current state of HTTP compression

• compression

EN Currently, practically all text compression is done by one of two HTTP content encodings: Gzip and Brotli. Both are widely supported by browsers: can I use Brotli/can I use Gzip

• Currently
• practically all text
• two HTTP content
• Gzip
• Brotli
• Both are widely
• browsers