This file has to get loaded in browsers which takes a good amount of time and the user has to wait for the first painting of the webpage. Here you can see this is a bundled JS generated by the building of an Angular App which is more than 1 MB 🤯. Since the initial index.html is very lightweight, most hard work is being done by the subsequent Javascript files fetched from the server and the client executing that JS in the browser.Īs our project starts to become complex with a lot of components and dependencies, the bundled JS file sizes get bigger with time. Now let's come to the problem or one of the drawbacks of using a SPA. basically, most of the modern SPA frameworks like Angular, React, and Vue has a templating engine of sorts running in your browser to generate the HTML. The client (and not the server) handles the job of transforming data to HTML once the application has started.
#Angular image compress update
the application uses this JSON data to update the page dynamically. All subsequent calls return just the data, usually in JSON format.
js file which is going to take control of the index.html page. that's the only time an HTML file is served. In SPA, when the browser makes the first request to the server, the server sends back the index.html file. The single-page application is a web application that interacts with the user by dynamically rewriting the current page, rather than loading entire new pages from the server.
This article is part of the Epic Hashnode Writeathon submission as well.īefore diving into the article, let's first understand how a Single Page Application (SPA) works be it developed using any web framework (Angular, React, etc.) Single Page Application Hello folks, Today I will discuss, how I speeded up the loading time of my Web App built using Angular or any SPA (Single Page Application).
0 kommentar(er)
