Browser extensions

When testing websites, we rarely have only one browser open. Except Chrome, there are also Firefox, Opera, IE, Safari. They also have memory-hungry extensions. Although these extensions may have the same names, they reside multiple times in memory as they use different hosts. This can make a system less responsive. Although, extensions very often promise to make our life easier, they quietly steal machine resources. Running extensions and plug-ins can be costly, because they compete with the open tabs for the same available resources. The more active extensions we have, the less tabs we can open and the worse the browsing experience becomes. The web designer may not always be guilty that a website is slow, when a third-party extension can adversely impact the user-page interactions. In Chrome it is recommended to use an incognito window, which prevents the extensions from starting without uninstalling them. This is much easier than seeking where to enable/disable them before each run. When we need an extension, we can always open a normal window. A more radical approach would be to uninstall most extensions, especially the ones that we use only occasionally, but are constantly taxing the system. Depending on their number, we may notice a certain speedup in the browser response time when dealing with tabs and loading new content. Another option is to close certain non-critical processes when they occupy inadequate levels of memory. But this is hardly repeatable.

bit.ly/1bCBKtZ