OldFatGuy: The speed is CAPPED in the standard browser download at 3.5MB/s. It doesn't matter what site you're on. It doesn't matter what time of day, what traffic is like... IT DOESN'T MATTER. Now if your ISP is slower, then yeah, you'll get different speeds based on that type of stuff but they will be LOWER THAN 3.5MB/s.
No, OFG, this is just you. And if you keep acting like the problem is out of your hands, you'll never solve it. It's you, and up to you to fix it.
My parents use Comcast and download just fine at 5-6 MB/sec (they've got a 50 Mbps nominal cap) and despite years of effort, I haven't managed to teach them how to do anything *but* download through a browser. I just recently downloaded a game installer from GOG at around 100MBps (I have gigabit internet) through Firefox. Your problems are
yours. You want answers, go look at the stuff people have told you but that you've brushed aside. You're wrong. Again. You have this problem, and if you want it fixed, you need to see what you're doing wrong. Hint: it's probably your computer, and possibly even your connection to the world, not you as a person - but it's still your error.
timppu: Then again that would be quite odd when they are selling internet with higher speed, and then throttle two quite important ports...
Not that odd here in the USA, sadly. Comcast is one of the providers that still uses cable regularly. Cable has come a long way, but it's still not independently bussed to the home which means congestion happens a lot more often. Especially if OFG is in a less-populated area, there's not a tremendous amount of incentive for Comcast to fix that particular concern. The actual details are available in
RFC 6057 if you're particularly interested, but the short version is that while Comcast
almost certainly doesn't explicitly slow HTTP ports, they probably do so indirectly by using an infrastructure that creates bottlenecks that otherwise don't need to exist.