Performance considerations

blueriq.web-resources:= source location

blueriq.web-resources.cache-key-seed

blueriq.web-resources.cache-period-seconds

HTTP 1.1versus HTTP 2.0

HTTP 1.1. can only perform one request per connection, resulting in latency, HTTP 2.0 fixes this by introducing mulitplexing, which allows for multiple requests and responses to be handled by a single TCP connection at the same time.

In HTTP/1.1 it was quicker to download a single file as opposed to several smaller files. As a result it was best practice to concatenate your site’s CSS and JS. In a HTTP/2 era, HTTP requests are cheap, therefore creating a single concatenated file is often unnecessary and an anti-practice for two reasons:

1. The concatenated file would often contain components not required by the current page. For example, your blog page might load components that are only used on your checkout pages.
2. If a single component changed then the entire concatenated file would need to be invalidated from the browser cache.

Both of the above increase the amount of data which needs to be downloaded from the server to the browser. However, concatenation still does have its place due to compression ratios. Generally, larger files yield better compression results, thus reducing the total overall file size of your page.