PRR (Partial / Progressive Rendering)
noun · web performance
A web rendering technique where the critical elements of a page are sent and displayed first, while secondary components are loaded progressively — reducing perceived load time and improving Core Web Vitals.
A performance architecture adopted by modern frameworks like Next.js and React, which allows HTML to be streamed in chunks to the browser via mechanisms such as Suspense and streaming SSR, avoiding the monolithic wait for a complete page.
An optimization strategy that decouples the rendering of heavy components (charts, large lists, third-party widgets) from the rendering of the main content, guaranteeing instant display of essential information on all devices.
PRR (Partial / Progressive Rendering) is a web rendering technique that consists of sending and displaying the critical elements of a page first, then progressively loading the rest of the content. Instead of waiting for the entire page to be generated server-side, the browser receives a continuous HTML stream and displays each section as soon as it is ready. Our agency uses this approach with React Suspense and Next.js streaming SSR to deliver near-instantaneous perceived display times.
Progressive Rendering drastically improves the user experience by eliminating the blank loading screen: the user sees the main content appear immediately while secondary elements load in the background. This perception of speed reduces bounce rates and increases engagement. Our agency implements elegant loading indicators (skeletons) for areas still being rendered, transforming wait time into a smooth and professional experience that inspires trust.
PRR has a direct and positive impact on Core Web Vitals, particularly the Largest Contentful Paint (LCP) and First Input Delay (FID). By sending critical content first, the LCP is reached much earlier because the browser does not wait for heavy components. The main thread is freed up faster, improving FID and Interaction to Next Paint (INP). Our agency uses PRR as the primary technical lever to achieve green Core Web Vitals scores on every page.
Classic hydration waits for all the HTML to be rendered server-side, then the client JavaScript takes over the entire page in a single operation. Partial Rendering, on the other hand, allows components to be hydrated selectively and progressively: each section becomes interactive independently as soon as its JavaScript is loaded. Our agency leverages this granularity so that critical interactive elements (navigation, CTAs) are functional instantly, without waiting for the hydration of lower-priority sections.
On bandwidth-limited mobile connections, Progressive Rendering is crucial because it allows the user to start consuming content without waiting for the complete page download. HTML streaming sends bytes as soon as they are available, and the browser progressively displays the received content. Our agency optimizes this approach for mobile audiences by prioritizing critical text content and deferring images and heavy components, ensuring universal accessibility.
PRR isolates heavy components (complex charts, image carousels, third-party widgets) within Suspense boundaries that do not impact the rendering of the main content. The server sends a placeholder for these components and continues streaming the rest of the page. When the heavy component is ready, it is dynamically injected without blocking the interface. Our agency uses this architecture to integrate rich features without ever compromising the perceived speed for the user.
Progressive Rendering relies on HTTP streaming, a feature natively supported by all modern browsers (Chrome, Firefox, Safari, Edge). HTML is sent in chunks via Transfer-Encoding chunked, a standard capability of the HTTP/1.1 protocol. For older browsers, rendering falls back to the classic method without any functional degradation. Our agency ensures that this optimization technique is implemented progressively, delivering the best possible experience to each browser.
Partial Rendering has a positive impact on technical SEO because the critical content — headings, paragraphs, metadata — is sent first in the HTML stream, exactly as indexing robots expect. Googlebot receives the main content without waiting for secondary components, which accelerates indexing and improves the perceived quality of the page. Our agency structures streaming so that SEO-critical information is always in the first chunk sent to the browser.
Implementing PRR requires a framework that supports streaming SSR such as Next.js with React Suspense, a Node.js server capable of handling chunked responses, and a CDN configured not to buffer streamed responses. The architecture must identify the critical components to render first and encapsulate secondary sections within Suspense boundaries. Our agency deploys this infrastructure turnkey, from server configuration to component optimization, to maximize the benefits of progressive rendering.