Some of examples of the benefits different companies have seen of Quick Page load are:
- Walmart found that every 100ms reduction time in page loading time leads to an increase in incremental revenue by as much as 1%.
- Mozilla saw increase in downloads of firefox by 5 million per month after making their page 2.2 seconds quicker.
- Bing found that a 2 second slowdown changed queries/user by -1.8% and revenue/user by -4.3%.
- Google Search found that a 400 millisecond delay resulted in a -0.59% change in searches/user. What’s more, even after the delay was removed, these users still had -0.21% fewer searches, indicating that a slower user experience affects long term behaviour.
- Phil Dixon, from Shopzilla, had the most takeaway statistics about the impact of performance on the bottom line. A year-long performance redesign resulted in a 5 second speed up (from ~7 seconds to ~2 seconds). This resulted in a 25% increase in page views, a 7-12% increase in revenue, and a 50% reduction in hardware.
Pros of SPA
Let’s see some of the advantages of SPA:
“Application like” interaction even though only a single page is involved.
Ability to go offline
Cons of SPA
Seeing all those advantages and the enhanced performance factor, an obvious thing arises: “there has to be a catch somewhere, there must be some features I will be missing.” Well, there are few features you may loose as well.
But Each of the Cons has effective Solutions. All these challenges are effectively Handled.
Coming up in next blog: how challenges are handled, which frameworks are used for Single Page Applications & common mistakes to avoid in Single Page Applications.