Page History
...
Measurements in Google Chrome with Blueriq 10.5
| HTTP 1.1 with disabled cache | HTTP 1.1 with cache | HTTP 2.0 (with TLS) and cache disabled | HTTP 2.0 (with TLS) with cache | |
|---|---|---|---|---|
| Requests | 38 | 38 | 38 | 38 |
| Transferred | 1.4 MB | 16.3 KB | 1.4 MB | 293 KB |
| Finish | 1,47 s | 379 ms | 475 ms | 400 ms |
| DOMContentLoaded | 663 ms | 261 ms | 321 ms | 271 ms |
| Load | 694 ms | 285 ms | 348 ms | 290 ms |
GZIP compression enabled with HTTP 1.1 is 214 percent faster than HTTP 1.1 with GZIP compression disabled | When the resources are in the browser cache the response times between HTTP 1.1 and 2.0 are very similar. Strangely with HTTP 2.0 the CSS stylesheet resources are not loaded from the cache, while this is the case with HTTP 1.1 | When the resources are NOT (yet) in the browser cache HTTP 2.0 is 309 percent faster than HTTP 1.1 | When the resources are in the browser cache the response times between HTTP 1.1 and 2.0 are very similar. Strangely with HTTP 2.0 the CSS stylesheet resources are not loaded from the cache, while this is the case with HTTP 1.1 |
Relevant Blueriq properties
blueriq.web-resources: the location (URL) of additional or overridden webresourcesReference Guide: Properties [editor]
blueriq.web-resources.cache-key-seed:
blueriq.web-resources.cache-period-seconds:the cache period for all static webresources. When null, default behavior is to rely only on 'Last-Modified' header. When 0, caching is disabled. When > 0, the number of seconds to cache a resource client-side (browser).
HTTP 1.1 versus HTTP 2.0
HTTP 1.1. can only perform one request per connection, resulting in additional latency, HTTP 2.0 fixes mitigates this by introducing mulitplexingmultiplexing, 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 often considerably faster to download a single one large file as opposed to several smaller files. As a result it was best practice to concatenate your site’s CSS and JS resources. 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:
- 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.
- If a single component changed changes then the entire concatenated file would need to be invalidated from the browser cache.
...
Websphere: it seems that Websphere currenlty (november 2017) does not support HTTP 2.0 (https://github.com/http2/http2-spec/wiki/Implementations)
Gzip compression
Enabling HTTP / 2.0 alone can have a significant impact on your site’s performance, but additional best practices such as gzipping assets ensure optimal load times. Static text based files such as CSS and JS should be compressed by the server before sending them to the browser. This can reduce file sizes by up to 90%, which can significantly reduce the time it takes to download each asset.
Concatenation
...
In HTTP 2.0, concatenation isn't required anymore any more to improve performance. We can now send (potentially) hundreds of requests in one connection, so we don't have to bundle files together anymoreany more. Concatenation was a way to cheat the 6-connections-open-at-one-time limit. That limit doesn't exist in HTTP / 2.0. In fact, concatenation could be counter productive--what if you're loading a bunch of CSS that doesn't get used on a some of your pages? You're just loading extra bytes and that can slow down rendering of your page. In HTTP /1.1, it was often worth avoiding an extra round trip, but in HTTP / 2.0 it probably isn't.
Further reading: https://deliciousbrains.com/performance-best-practices-http2/
...
Overview
Content Tools