Webmasters do URL redirect (whether it’s Javascript or META redirects) all the time. Sometimes it’s purpose is to point users from an old page to new, or merely guide users to the correct page. Each redirect create an additional HTTP request and round-trip time (RTT). The more redirection you have, the slower user will get to the destination page.
Minimizing HTTP redirects from one URL to another cuts out additional RTTs and wait time for users.
Sometimes it's necessary for your application to redirect the browser from one URL to another. There are several reasons web applications issue redirects:
- To indicate the new location of a resource that has moved.
- To track clicks and impressions and log referring pages.
- To reserve multiple domains, allow for "user-friendly" or "vanity" domains and URLs, and catch misspelled/mistyped URLs.
- To connect between different parts of a site or application, different country-code top-level domains, different protocols (HTTP to HTTPS), different security policies (e.g. unauthenticated and authenticated pages) etc.
- To add a trailing slash to URL directory names to make their contents accessible to the browser.
Whatever the reason is, redirects trigger an additional HTTP request-response cycle and add round-trip-time latency. It's important to minimize the number of redirects issued by your application — especially for resources needed for starting up your homepage. The best way to do this is to restrict your use of redirects to only those cases where it's absolutely technically necessary, and to find other solutions where it's not.
There is a lot of dedicated extensions for Portal and CMS tools. For Joomla! you can get one from extensions directory here.