When I use Google Chrome (all addons disabled, cache deleted, cookies cleaned, local storage cleaned etc.), I have a massive interface lag time.
For example, loading the main Status page hangs on "Loading view" with the circular icon for a total of 41.62 seconds. By comparison, Firefox loads this page in 1.12 seconds.
Similarly, the Network-->Wireless page takes 21.38 seconds to load with Chrome and just over a second with Firefox.
This is against uhttpd. Using nginx, the interface is much faster and the wait time on Chrome decreases considerably, but a substantial gap still exists between Chrome and Firefox. Using nginx decreases the 41 second load time for the status page to a total of 3 seconds, while with Chrome to a little less than a second.
This is not a machine resource issue: my build is running on a 4-core x86_64 with 16GB of RAM and a data centre class SSD. It's also not a client PC issue: I've tested on multiple machines, wired and wireless connections and the problem is the same across all platforms.
Android versions of the browsers behave similarly, although they're both much slower to load the pages and sometimes glitch and don't load at all when using uhttpd.
My Openwrt 15.05 build running on exactly the same hardware with uhttpd as the backend loads these pages almost instantly.
Has anyone else noted this painfully slow behaviour from Chrome? I know others have already pointed out that uhttpd is very slow....