Given the rapid adoption of mobile technology, and the plentitude of mobile apps and websites available to users, the mobile user experience is of the utmost importance in today’s marketplace. Even if your target audience is expected to own high-end devices, the phones may not always be used in an optimal environment. Site loading times are also affected by the users’ data coverage or the strength of their current network, which is often lacking in a busy work environment or a public WiFi zone.
If your app employs a heavy use of frameworks and libraries, code splitting will almost certainly improve the quality of your customers’ user experience.
Performance budgets for your website provide clear, measurable figures to keep everyone accountable to the goals for the website or app. Mobile sites should aim for a JS budget of no more than 170KB compressed, which equals approximately 0.7MB of uncompressed code. By working within the budget’s constraints, the site’s performance becomes a constant consideration instead of an afterthought to be addressed down the line.
These budgets can be defined in three ways: milestone timings, which are created in accordance with the user experience on the page; quality-based metrics, which are based on the browser experience using raw figures; and rule-based metrics, which are scores formulated by other tools (e.g., Lighthouse).
Users have a multitude of websites, apps, and companies vying for their attention. A slow-loading site not only affects the user experience on mobile sites, but it can also result in lost leads, conversions, and purchases.