This document compares single-page applications (SPA), server-side rendering (SSR), and static sites for serving web applications. SPA have poor SEO without additional configuration, slow initial loading times but easy scaling. SSR has fast initial loading, requires a server for deployment but routing can be complex. Static sites have good SEO, fast loading, easy deployment but lack dynamic routes without custom handling.

1. Comparison On Various Ways To Serving Webapps
SPA SSR Static Sites
SEO Poor Good Good
First Paint / First
Contentful Paint
Slow as everything still
needs to be loaded first
Fast Fast
Deployment Static content server
sufficient (S3, Netlify)
Requires server
(AppEngine, Lambda)
Static content server
sufficient (S3, Netlify)
Cloud scaling Easy Complicated Easy
Dynamic routes Yes Yes 404 if directly entered
(need to handle this)
Dev complexity No client / server rendered
content awareness
No
PWA Easy Somewhat easy Easy