Browser protocol
Navigation Timing reports the protocol used for this page, usually h2 for HTTP/2 or h3 for HTTP/3. Checking again does not reload the page.
See the HTTP protocol your browser used to load this page.
Comparing browser navigation with the connection visible to Localtonet.
This is the protocol used for this page load. A different protocol on a later load is normal; this test does not measure speed.
HTTP/2 carries multiple requests over a TCP connection. HTTP/3 uses QUIC over UDP, which changes how connections handle transport and packet loss. This test reports the protocol used to load this page; it does not test an arbitrary website.
Your browser and the application may see different protocols when a CDN or reverse proxy sits between them. Reload after a network or VPN change to compare a new page load, and use the TLS fingerprint test for the secure connection details available to the application.
Navigation Timing reports the protocol used for this page, usually h2 for HTTP/2 or h3 for HTTP/3. Checking again does not reload the page.
The application sees the final connection in the hosting path. A proxy may use a different protocol when forwarding traffic.
UDP reachability, server advertisements and cached connections can affect negotiation. Another protocol does not prove HTTP/3 is unsupported.
Reload the page after changing your network, VPN or browser settings to create a new navigation observation.
Run the test to see its detected details.
No. Its benefits depend on latency, packet loss, implementation and the page itself. This tool reports protocol negotiation, not performance.
A CDN or reverse proxy can use one protocol with your browser and another with the application.
The browser value belongs to the current page navigation. Reload the page to inspect a new navigation.
Browser policy or privacy controls can omit Navigation Timing details. The application observation may still be available.