> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/c/client-side-rendering-csr.md).

# Client-Side Rendering (CSR)

Client-Side Rendering (CSR) is a web rendering approach where the browser downloads a minimal HTML page and then uses JavaScript to fetch data and render the full page content on the client. Frameworks like React, Vue.js, and Angular commonly use this pattern through single-page application (SPA) architectures.

In a CSR application, the initial page load may be slower because the browser must download, parse, and execute JavaScript before content appears. Subsequent navigations, however, are typically faster because only data (usually fetched via API calls) needs to be retrieved rather than full HTML pages.

CSR applications rely heavily on APIs to fetch and submit data. This makes API design, performance, and reliability critical. An API gateway can improve CSR application performance by caching frequently requested API responses, compressing payloads, and enforcing rate limits to protect backend services from excessive client-side requests.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.serverlessapigateway.com/glossary/c/client-side-rendering-csr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.