Simulating latency when developing on a local webserver

Question

The Performance Golden Rule from Yahoo's performance best practices is:

80-90% of the end-user response time is spent downloading all the components in the page: images, stylesheets, scripts, Flash, etc.

This means that when I'm developing on my local webserver it's hard to get an accurate idea of what the end user will experience.

How can I simulate latency so that I can understand how my application will perform when I've deployed it on the web?

I develop primarily on Windows, but I would be interested in solutions for other platforms as well.

Answer 1

A laser modem pointed at the mirrors on the moon should give latency that's out of this world.