Akhilesh is right. With any network program, there's a lot of factors that are out of your control. Firefox tries to speed things up with optimizations like
prefetching pages. That kind of optimization would be easy to replicate.
Java has long been
as fast as compiled code for most tasks, and there are
pure Java browsers so I don't think Java itself would be a problem.
That said, there's a reason why Chrome uses
Webkit rather than a home-built rendering engine. The level of effort and knowledge in building a fast browser is large, and it no longer makes sense to reinvent the wheel. Building a fast browser in Java may be possible, but it doesn't really make sense when we already have several very capable browsers on the market.
