@deg sorry to be preach if you already know this:
If you compress the video, then my dummy terminal (probably a smartphone) will take its time putting the video back together. So it is that 140ms + compression time + compressed transfer + rebuild time vs 140 ms + transfer time. Because I am assuming I need to see everything in my screen, there are some tricks, but I can't run from the 140ms delay.
It is the round trip I sending my input package through the web, and they answering it to me what the game did.
There exists a protocol called UDP, very simple I send you a message it runs the web and gets to you. But most UDP transfers send more than once the message, because net congestion, some of those messages get lost, don't necessarily move in the same path, and I don't want to wait at least 140 ms to discover you didn't receive it. So there is a little of jitter in that 140ms, it sometimes will be 145ms for example.
There is the IP protocol, part too, that udp message needs to go to a computer the router who will look the address and forward closer to you. That address can change. Router has a list of messages, from all over the place coming through. If the list will be bigger than its memory when the package arrives it just drops it, and the package stops existing. If the place in the list the message arrived is further back, it gives it a small delay.
Say each message do be reasonably small after compression they still be that small being sent 3 times? Will they be small if by cosmic energies that message addressed To Dey, starts saying To Deg, will Deg bandwith be able to handle wrong traffic from Beg Dey Dag Dog ... aka message storms? And the internet infrastructure for the peak of Christmas holidays? Or when Hurricanes go around and wreck the havoc.
If you make the dummy terminal very smart, and add dlss, and etc, you start moving to a place where I am cloud gaming but could run it in my machine effortless, and now internet 140ms is just an overhead that I never needed. And I might lose some quality too.
I don't need big guns to play Celeste for example, but I may need it, to play GTA 6, Half Life 3, if they ever launch or some Call of Duty: Expendable Abuse aka CoD: EA. So browser gaming could mean sending Celeste as WASM, and Streaming the interface to GTA6.
But it would be a very big differential if the greed game dev said: I can build a game that runs natively to you all. (and he proceeds to just compile the game and sell it like GoG, because that is all he needed to do. And now we have AI Gaming too)
ps: Electron/browser/webview/Edge engine/ whatever will be between the game and the WASMs. And my dumb terminal keeps becoming smarter and smarter.
A message in average jumps through 6 routers before getting to yours. (And yes this has to do with Bacon degrees)
Prices for cloud computation have been rising due to AI, thus that service also rises. Games are very poorly optimized, and nothing I have seem lately deserves the technical requirements.