Another modern web design pattern that I hate is when a website uses an excessive amount of AJAX requests. The practical effect of this behavior is that you see

Another modern web design pattern that I hate is when a website uses an excessive amount of AJAX requests. The practical effect of this behavior is that you see the UI update many, many times before the data you're looking for is actually shown. While the data is being loaded, you just see placeholders and you don't feel like you should do anything until the entire page finishes loading. For instance, when I log into the Chase website, there's 8 UI updates (i.e. 8 sets of loading bars/HTTP requests; see below) that have to load before I can see the recent transactions on my account. Each chunk of requests must finish before the following chunk can start. All in all, it takes ~7.1 seconds for the page/recent transactions to load. --- The 8 UI updates the Chase website goes through before it finishes loading/you can see your recent transactions: 1. Initial blue loading screen with a spinning loading icon 2. Tan colored background color replaces screen #1 3. Header loads 4. The blank outlines of the main UI components loads (without any data in them/with placeholder loading bars) 5. All of my Chase account metadata (account type, current balance, and last four digits of the account number) loads 6. More in-depth data of the first account on the list loads (available credit, payment due date, minimum payment due, etc.) 7. Recent transactions panel starts to load (with no data/with only a placeholder loading bar) 8. Recent transactions are shown At this point, the page is finished loading.