This delay can annoy your user and make them leave your site. Because in the startup performance is the only thing that can bind user with you. The slow performance isn’t the problem for you, the big companies like Facebook and Wikipedia constantly works their ass off to get high website performance.
The major fact that determines the performance of webpage in this smartphone world is the power of users smartphone. The performance will always be different in high-end mobile like iPhone as compared to the regular like Moto G. But, as a developer, you should always be ready for high end mobile as well as regular mobile.
“I’m not Facebook” Well if you are thinking that you don’t have a large database as Facebook and surely your parse and compile time will be small. But, that’s not the case folks, as according to a study conducted in different production sites libraries and frameworks like React, Angular, Ember, and Vue.
The websites are tested via regular WebPageTest, so you can redo test yourself if you like. But, that’s not the point, the main point here is to analyze the insight of the study.
- Apps became interactive on the desktop in 8 seconds using cables whereas in a smartphone it takes 16 seconds on the average 3G network.
- Apps mostly spend 4 seconds in a startup on the desktop.
- On mobile devices, parse time is 36% higher than the desktop.
Tools To Measure Parse Time
You can easily measure your website’s parse time by using following tools:
- Chrome DevTools
- Chrome Tracing
- User Timing
What Can We Do To Reduce Parse Time?
Okay, so if you are in hurry and quickly wants to reduce parse time of your website for fast loading. Then, you can take following steps immediately:
- Use Code splitting. Shop only those codes which user need to load and lazy load the rest. This will be very beneficial in reducing parse time. Patterns like PRPL encourage this type of route-based chunking, now used by Flipkart, Housing.com, and Twitter.
- Script Streaming. V8 have told developers to use `async/defer` to opt into script streaming for parse-time improvements of between 10–20%. This allows HTML to detect the work early and this way document loading won’t be blocked by the server. Loading larger bundle earlier has lots of advanced like there will be only one streamer thread.
- Measure Parse Cost of Dependencies. You should measure the parsing cost of Dependencies such as libraries and framework. According to Paul Lewis, ” A good way to measure start-up costs for frameworks is to first render a view, delete and then render again as this can tell you how it scales. “
Startup performance matters the most. The increase parse time and slow execution can be one of the biggest hurdles for your website boost up. So, try to find the parse, compile and execution time of your time using different tools. And, took productive steps to improve it as well.
As performance always matter.