I've not measured it, because it's still a substantial time and error saver. The only possible downside I've spotted is that it seems the autotype response is slower than before. For debugging/testing: added plgx-build-install-run-loop. Always returns a 16x16 icon to keep DB size low. This returns an icon based on the domain name, so will likely return an incorrect icon if a sub-page has a different icon than at URI path / - but I did not test this. I've used it with many different browser and not found any issues. Changes Option in the Tools->YAFD menu to use Google S2 API to fetch icons. autotype) and have it perform a different task relevant to the page URL or window title. Use the same command on each window (i.e. For example, default autotype behaviour can be set up on page 1 and the username and password automatically typed in to these fields, but when the next window opens, using autotype can now be set to use the PICKCHARS function to produce the selected characters from the keyword. This excellent add-in allows you to store different data, and configure different KeePass behaviours, dependent on the browser window that is displayed at the time. a username and password on page 1, followed by a random selection of characters from a keyword on page 2. These often involve two or more web pages / browser windows, with different types of data on each page e.g. More and more 'security conscious' websites such as banks, credit cards, etc are requiring multiple stages of login.

Google chrome keepass plugin