Infrastructure & Hosting · AuditJet Glossary

SSR (Server-Side Rendering)

A rendering strategy where HTML is generated on the server for each request, rather than in the browser via JavaScript.

SSR improves FCP and LCP compared to client-side rendering (CSR) because the browser receives complete HTML immediately rather than waiting for JavaScript to generate content. However, SSR increases server load and TTFB if not optimised. Next.js, Nuxt.js, and SvelteKit all support SSR. The trade-off between SSR, SSG, and CSR is a key web performance architectural decision.

Related terms

SSG (Static Site Generation)

A rendering strategy where all HTML is generated at build time and served as static files — with no server processing per request.

TTFB (Time to First Byte)

The time from when a browser requests a page until the first byte of the server's response is received.

LCP (Largest Contentful Paint)

The time from page navigation start until the largest image or text block visible in the viewport has finished rendering.

Hydration

The process by which a JavaScript framework attaches event listeners and makes a server-rendered or statically generated HTML page interactive.

Frequently asked questions

What is SSR (Server-Side Rendering)?

A rendering strategy where HTML is generated on the server for each request, rather than in the browser via JavaScript.

How does AuditJet measure SSR (Server-Side Rendering)?

AuditJet runs automated Google Lighthouse audits that surface SSR (Server-Side Rendering) scores alongside actionable fix guidance. You can track SSR (Server-Side Rendering) trends across all your pages and receive alerts when the metric regresses.

Monitor SSR continuously

AuditJet tracks Core Web Vitals on a schedule with revenue impact alerts — powered by Google Lighthouse and Google PageSpeed Insights.

Start Free