This will show how long lynx takes to do name lookups, connect to the server, wait for your server and perform the download of data.
Real browsers can cache part of your website, but they also need to render the content, so if your concern is the actual user experience, you don't want to use the lynx method.
Assuming a UNIX system, a simple, artificial way would be:
time lynx http -source -dump http://google.com/ > /dev/null
This will show how long lynx takes to do name lookups, connect to the server, wait for your server and perform the download of data.
Real browsers can cache part of your website, but they also need to render the content, so if your concern is the actual user experience, you don't want to use the lynx method.
Question is very vague. One answer would be to
Another answer would be:
Another answer would be
Another answer would be
There are hundreds more.
And that's based on lots of assumptions about what you want to measure.
Go read this, this, this and this
The question is a bit vague, but you have several ways to do so
Also you can use external free sites to check your server like http://www.changedetect.com/ or use Google Analytics as well
In addition to all other good suggestions:
Web application transaction performance can be measured with the open source iMacros for Firefox addon from the command line.