![]() ![]() Good performance is always important, but it is especially critical for content-focused websites. □ Learn more about what makes Astro’s MPA architecture unique.įast by default Section titled Fast by default These tradeoffs harm page performance - including critical metrics like Time to Interactive (TTI) - which doesn’t make much sense for content-focused websites where first-load performance is essential. However, these come at the expense of additional complexity and performance tradeoffs. This approach has been dubbed the Single Page App (SPA), in contrast with Astro’s Multi Page App (MPA) approach. These frameworks require client-side rendering of your entire website and include server-side rendering mainly to address performance concerns. This approach stands in contrast to other modern JavaScript web frameworks like Next.js, SvelteKit, Nuxt, Remix, and others. With Astro, everything is still just HTML, CSS, and JavaScript (or TypeScript, if you prefer). But you don’t need to learn a second server-side language to unlock it. This is the same approach that traditional server-side frameworks - PHP, WordPress, Laravel, Ruby on Rails, etc. Astro leverages server-side rendering over client-side rendering as much as possible.
0 Comments
Leave a Reply. |