Does GDS Service Standard require server-side rendering?

GDS Service Standard requires services to work without JavaScript for users who disable it or use assistive technologies that do not execute JavaScript. This effectively rules out pure SPAs for GDS-assessed public sector services. Next.js App Router with Server Components renders the core functionality server-side — JavaScript enhances but is not required. All ClickMasters GovTech projects use Next.js SSR with progressive enhancement.

How does rendering strategy affect UK GDPR cookie consent?

SPA: analytics scripts load before server response — cookie consent must fire before analytics initialise (implemented with a blocking consent manager, but still runs on the client). SSR: server renders the page without any tracking cookies — cookie consent is served as part of the first HTML response. The user sees the consent banner on first paint with no tracking having fired. SSR provides a cleaner UK GDPR / PECR cookie consent implementation.

Spa Vs Ssr Uk 2025

SPA vs SSR vs Static Site — Which Rendering for UK Web Applications? (2025)

Updated: June 20259 min read

🇬🇧 UK💷 GBP📊 Comparison🔒 UK GDPR⚖️ UK Law

Direct Answer

Server-Side Rendering (Next.js App Router) is the right default for most UK web applications: better SEO, better Core Web Vitals (critical for Google ranking), better performance on first load, and natural fit with UK GDPR cookie consent (server-rendered consent before any tracking). Pure SPAs (React without SSR) are right for highly interactive applications (dashboards, admin tools, internal tooling) where SEO is not needed. Static Site Generation (SSG) is right for content-heavy marketing sites. Rendering strategy affects SEO, Core Web Vitals performance, UK GDPR cookie consent implementation, and developer experience. Here is a practical UK comparison.

Factor	SSR (Next.js App Router)	SPA (React/Vite)	SSG (Next.js/Astro)
SEO (Google ranking)	✅ Excellent — HTML on first response	Poor — JS must execute first	✅ Excellent — pre-rendered HTML
Core Web Vitals LCP	✅ Fast — server renders critical content	Slow — JS bundle before content	✅ Fastest — pre-built HTML
UK GDPR cookie consent	✅ Consent before any client-side tracking	⚠️ Consent must fire before analytics	✅ No cookies without explicit opt-in
GDS Service Standard compliance	✅ Works without JS (progressive enhancement)	❌ Requires JS — not GDS-compliant	✅ Works without JS
Dynamic data (real-time)	✅ Server Components + SWR	✅ Excellent (client-side fetching)	Limited (revalidation required)
Admin/dashboard UX	Possible but more complex	✅ Excellent — rich interactivity	Not appropriate
Time to first byte (TTFB)	Server compute adds latency	Very low TTFB	✅ Lowest — CDN-served static
ClickMasters default	Consumer/public-facing apps	Dashboards/admin tools	Marketing/content sites