The slow web page loading is due to latency not data speeds. The hughesnet server or satellite is overloaded and their reponse time is terrible. We are being screwed by Hughes net when they only talk about data speeds. The problem is not data speed it is server/satelite reponse time. I'm serious thinking of taking this to small claims court.
Latency is related to the laws of physics -- no court in the land will be able to change that. Additionally, as per the Hughesnet contract, binding arbitration is the only way to legally solve disputes. Read the contract to see how this would work. (Binding arbitration clauses are very common nowadays and you will find them in credit card documentation, bank documentation, ISP contracts, etc. Hughesnet did not invent this.)
Don't think legal action would be easy / help, but I agree with the complaint.
I understand the 600 - 700 ms latency involving a geostat satellite. I would need to use a stopwatch to add all of the "back & forth" data exchanges (~280ms latency, due to round trip to satellite - rest is Hnet) to load a typical web page to quantify properly. OTOH, just observing the data activity and measuring the overall time to complete a page load seems to take much longer than just the satellite distance / latency time. I have had many pages take in excess of 45 to 90 seconds to finish loading. I also realize there is going to be some latency at the earth gateway. But, I would not expect so much. Pages are a little slower to load while I am (now out of data) throttled - back, but not by much. Sad to say in many cases that 1Mbps will load a page as fast as 30Mbp due to delays at Hnet. Admittedly, I can tell that when throttled-back, zooming-in with google/maps is just a little slower. BTW, don't stream video much at all, so no opinion on that.
Double it. That's just the speed of light from you to the satellite. The satellite then has to send it to the groundstation in the west coast to get to the internet, which is nearly identical.
Doing the math, for me in Central Virginia to the satellite at -97.1071 (west) and roughly 36km up, then to the groundstation in San Diego is about 523ms. The rest is HughesNet and their upstream provider, which for me (Level3) is more often than not the biggest added problem - speedwise and latency.
The slow web page loading is due to latency not data speeds.
No, it's not. Latency, as noted, is a bit over a half second. That's it. *
If you'd like to work on the issue please start a new topic.
* Edit: The latency can be a bit higher than a half second under some conditions, as BirdDog has noted below, but not many seconds, or even minutes.
A single two way communication takes two round trips total to the satellite and back. So four 22,236 mile legs.
22,236 x 4 = 88,994 miles
88,944/186,000 = 0.4781935483870968
The perfect laboratory conditions would equal 478ms. This is not counting any real world delays like slowness of the Internet servers, processing signals, traffic delays, etc. These other delays boost the latency to over 500ms minimum and double or more under some conditions.