It depends on the application to application. There are some guidelines (2-3 seconds may be ?) for how long user will wait, but 2-3 seconds may not be appropriate in some cases and can be considered very fast in another.
There are no standards for Response Time, it really depends on what your application does, who it does it for, and how long they consider acceptable to wait.
For example, you're probably willing to wait longer for the results to a search to appear than you are for a home page to display.
If you're using a system over the internet you'll probably we happy waiting longer than if you were using it over the intranet.
If it's something you really want, you'll wait longer than if it's something you clicked on out of interest.
If you click on something and the screen goes blank then 5 seconds might seem like a long time, if the screen goes to a "loading..." animated graphic, then 5 seconds may not seem like very long to wait because you've got a clue that the system is doing something.
There are so many variables that it's impossible to have a standard time, and it doesn't make sense to do so.
There is lots of good information on this (see much of Scott Barber's work), and lots of misinformation (the often mis quoted 8 second rule).
You really need to know what your users will find acceptable. To do this, you probably need to talk to them.