No-one is going to be able to give you a complete description of how to analyse results because it's a very complicated process and is specific to your application. Recording and running the test is the easy bit, working out what it all means is much trickier.
You could try searching google for performance counters you should collect for each of the application you mention, you could probably tell a lot from the different counters/logs you see.
As an example, this is what I would do to get started.
1. Wrap all the individual transactions that make up a page in a timer. e.g. the timer T_HomePage would include the HTML of the homepage and every image, stylesheet etc.
3. When testing has completed export the list of timers to a CSV file, open it in Excel and determine if there are any consistently slow pages.
4. If there is a particularly slow page then investigate what makes up that page, the elements (e.g. huge image), the database queries that are run etc. Try and identify where the page is slow. Adding some debug reporting with times is handy to see where in the page the time is being used up.
5. Analyse the performance monitor stats, as a rough rule on a windows box:
- if your processor is consistently above 85% and you have a Processor queue length of greater than 4 then your system would benefit from a faster processor.
- The available memory and committed bytes will tell you if your using up all your memory and therefore more memory would be good.
- If your application server is doing nothing, but your page response times are slow then it suggests the application server is waiting for something e.g. database.