-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react-code-splitting-techniques #29
Comments
Interesting topic! How would you know if your site performance is being affected by the JavaScript bundle size? |
@Cheuktingchan, there are some signs that your site performance is being affected by the JavaScript bundle size. I will split them into two groups: Slow page load (if your site is taking a long time to load, it could be due to the size of your JavaScript bundle). High bounce rate, poor user experience, low conversion rates (if users leave site quickly it can be because website takes long to load or slow to transition between pages, this all can lead to less likely for auser to purchase or sign up for a service). Google Lighthouse is your friend, you can use it to identify performance issues and try to optimise your JavaScript bundle size. If you use webpack, try webpack-bundle-analyzer it will create an interactive treemap visualisation of the contents for all your bundles. |
Great post! Much clarifying, thank you. |
Maximising performance with React code splitting techniques | Edvins Antonovs
You can maximise the performance of your React applications with my guide to the latest code-splitting techniques. Learn how to use dynamic imports, React Lazy, Loadable Components, route-based code splitting, preloading, inlining critical CSS, and dynamic chunks with code examples.
https://edvins.io/react-code-splitting-techniques
The text was updated successfully, but these errors were encountered: