Submitting posts, general TCP issue

[moonbob69]

I have a general issue with connectivity, apparently due to Google Nest wifi (connected to Comcast) which can not be bypassed. In general connection is fast, Ping returns in ~ms. But sometimes "Performing TLS..." takes many seconds, or if the Looking up and Performing TLS is OK, there is a "Waiting for.. for many seconds". Usually the progress bar in lower right of PM browser shows a hang at 50% or 80%. This occurs about 30% of new tabs, and more often opening linked URL from tab where it occurred. When browser is not "waiting..." connection is immediate, never just slightly slow.

Not being expert, it seems like request never gets to destination address, despite resubmissions.

With reading Wikipedia pages, selecting Stop button then either cursor at end of URL and Enter key, or click on green arrow in URL bar, starts again, with progress bar same place. 4, 5, 6 times. Frequently, browser finally reports "Done" lower left corner (correct URL in address bar but without that page loaded); then Refresh gets Wiki page immediately.

With posting to this forum.palemoon.org, clicking "Submit" got "waiting for..." with no progress ever shown; after Stop then Submit, the same, many times. But when this forum reported "Done" (with page still showing the form "savedraft, preview, submit" window), clicking submit did not get a submission like other sites, just "Done" again. Finally after 6-12 "Done"s, coming back after several minutes did result in submission.

I am hoping that this site's form submission process will shed light on what the fundamental TCP or proxy problem is, or how to diagnose it.

Edit: The above was submitted immediately, without the problem occurring on the described earlier posts.

[Moonchild]

This sounds like a typical problem poorly implemented/nonstandard/not compliant proxies would have when being presented with http pipelining. However, that should not be a problem on the forum since that should all be http/2 which doesn't use that, since it has its own queueing/multiplexing algorithms.

I'm also unfamiliar with Google Nest WiFi so I can't really help further, but you can TRY and see if setting network.http.pipelining in about:config to false and restarting the browser provides any relief.