Hey eric594
Currently the HTML itself is not served via HTTP/2, but all published assets (js, css, images) are.
The biggest improvements in page load performance are where a large number of assets need to be downloaded - with HTTP/2 they now can be downloaded in parallel where previously they would have been downloaded sequentially.
The initial page load of the HTML must occur before any additional assets will be downloaded (since it is what defines the additional assets) - so the additional benefit of HTTP/2 for the HTML itself is tiny in comparison to the assets.
However having said that, we still would like to serve all pages via HTTP/2, and once it’s possible for us to we will do so. At this point we are waiting for support from Fastly for HTTP/2.
Using the tool you linked, here is an example URL you can test for HTTP/2 support: https://daks2k3a4ib2z.cloudfront.net/58000b7f7105d4e052bb5194/css/nathan-s-supercool-site-62181f.webflow.d566752b6.css