What is server-side rendering?
Server-side rendering means a page's HTML is produced on the server, so it arrives ready to display.
Definition
The browser receives complete content instead of an empty shell that JavaScript fills in. Frameworks such as Next.js render pages on the server or ahead of time.
Why it matters
Content appears faster, and search engines and AI crawlers read everything without running scripts.
How to get it right
- Render marketing pages on the server or statically.
- Keep critical content in the HTML.
- Use client-side code only where needed.
- Check the page source shows your content.
Mistakes to avoid
- Client-only rendering for content pages
- Hiding text until scripts run
- Huge client bundles
Related terms
- Next.jsNext.js is a popular React framework for building fast websites and web apps with server rendering.
- Largest Contentful Paint (LCP)Largest Contentful Paint is the time it takes for the biggest piece of content in the first screen to appear.
- llms.txtllms.txt is a plain-text file at a website's root that gives AI assistants a concise, readable summary of the site.
Orlume, the design-first AI website builder, gets the details on this page right for you: describe your site in one prompt and it decides the layout, type, colour and structure, builds it in React and Next.js and puts it live in one click.
Free to start · No card required · Live in one click
More building and hosting terms
Questions, answered.
The things people ask before they start building.
What is server-side rendering?
Server-side rendering means a page's HTML is produced on the server, so it arrives ready to display. The browser receives complete content instead of an empty shell that JavaScript fills in. Frameworks such as Next.js render pages on the server or ahead of time.
Why does Server-side rendering matter?
Content appears faster, and search engines and AI crawlers read everything without running scripts.
How do you get server-side rendering right?
Render marketing pages on the server or statically. Keep critical content in the HTML. Use client-side code only where needed. Check the page source shows your content.
Still stuck? Email usBuild something that doesn't look AI-made.
Describe the site you want. Watch it get designed, not just generated. Then publish it to its own orlume.site address.
- Free to start
- No card required
- Publish to a live URL
- You own the code