Try running ~9 tests and preferably from the “Dulles Thinkpad” test location. It’s really hard to say with one sample and the Amsterdam server looks like it is seriously CPU constrained loading the page.
There’s a good chunk of time when loading the page where the network is idle and it looks like it’s entirely JS-bound. Looking at the bandwidth charts, the H2 one looks like it more cleanly and consistently fills the connection so I’d be more inclined to think that it might be from something else.
Lennie, a few of my colleagues where talking about this topic today. A possible reason of why h2 is slower than h1 could be a small initial TCP congestion window.
I am not sure how the WPT servers have the TCP parameters configured in the kernel, but a small congestion window will favor h1 which opens 6-8 TCP connections vs h2 which opens only 1.