From 39b81c38297c353315dae530375b82e38b75b4b3 Mon Sep 17 00:00:00 2001
From: Mauro Bieg
- In an MPA, each navigation triggers a full browser request and the server
- responds with a complete HTML document. HTML is generated on the server
- per request, so the browser always receives ready-to-display content.
- JavaScript is optional and typically used only for progressive
- enhancement. In-memory state is lost on every navigation. Because content
- is present in the initial HTML response, MPAs are naturally SEO-friendly.
- The server must be capable of rendering and serving a full page for every
- route.
+ In an MPA, each navigation triggers a `document` request by the browser
+ and the server (or CDN) responds with a complete HTML document, so the
+ browser always receives ready-to-display content. JavaScript is optional
+ and typically used only for progressive enhancement. In-memory state is
+ lost on every navigation. Because content is present in the initial HTML
+ response, MPAs are naturally SEO-friendly.
Multi-Page Application (MPA)
Single-Page Application (SPA)
@@ -71,12 +69,12 @@ import Layout from '../layouts/Layout.astro'
navigation is handled client-side by JavaScript, without full page
reloads. HTML is generated in the browser, typically by a JavaScript
framework rendering components on demand. On initial load the browser
- receives a minimal document and must download and execute JS before
- content appears. Subsequent navigations fetch only data (e.g. via API
- calls), keeping the page transition fast. In-memory state persists across
- navigation. Because the initial HTML shell contains little content, SPAs
- require extra effort (SSR, prerendering) for good SEO. The server only
- needs to serve static assets.
+ typically receives a minimal document and must download and execute JS
+ before content appears. Subsequent navigations fetch only data (e.g. via
+ API calls), keeping the page transition fast. In-memory state persists
+ across navigation. Because the initial HTML shell contains little content,
+ SPAs require extra effort (SSR, prerendering) for good SEO. The server
+ only needs to serve static assets.
- In an MPA, each navigation triggers a `document` request by the browser
+ In an MPA, each navigation triggers a full page load by the browser
and the server (or CDN) responds with a complete HTML document, so the
browser always receives ready-to-display content. JavaScript is optional
and typically used only for progressive enhancement. In-memory state is
From 731ce43d4c4e2dba76773e502c09ceebc9828066 Mon Sep 17 00:00:00 2001
From: mb21
- In an MPA, each navigation triggers a full page load by the browser
- and the server (or CDN) responds with a complete HTML document, so the
- browser always receives ready-to-display content. JavaScript is optional
- and typically used only for progressive enhancement. In-memory state is
- lost on every navigation. Because content is present in the initial HTML
+ In an MPA, each navigation triggers a full page load by the browser and
+ the server (or CDN) responds with a complete HTML document, so the browser
+ always receives ready-to-display content. JavaScript is optional and
+ typically used only for progressive enhancement. In-memory state is lost
+ on every navigation. Because content is present in the initial HTML
response, MPAs are naturally SEO-friendly.
Multi-Page Application (MPA)