Unless you’re clicking through pages at record speed, 1 second latency for a web page and 100ms will be almost unnoticeable.

I just pulled Amazon.com, and on my computer it takes about 2 seconds for it to render, if we add 1 second of ping and it took 3 seconds to rend, I wouldn’t notice it. Looking inside chrome tools, I see it takes 700ms to download the content on the front page. This is relative of course and I could go deeper (if the initial page, and the content server both were 1 second away, technically it could take 2 seconds because it needs two round trips) but that’s kind of besides the point.

The main issue on the web is content generation/download, it’s not the time to reach the server. Lag matters more in gaming because you’re constantly talking to the server in a round trip constantly, so any latency is increased and will be more problematic. but with HTTP, you’re sending a request and getting it back, it’s a single round trip, you then will take time to parse that data and read it, and then when you’re ready for more you’re doing another round trip.

So if a server is 100ms or 1 second away you’re only paying that penalty once in a while. The issue is if the website gets under heavy load and can’t respond for multiple seconds or more, or fails to respond. That’s more of an issue with server load, which is why I say to focus on that.

If you TRULY think this is an issue, go to your command line and run “ping lemmy.world” I get 189ms pings. Amazon gives me 79 ms pings. Google is 28 ms ping. Those levels will be unperceivable after you consider the rest of the time it takes to download and render a page.