Detects heavy Client-Side Rendering (CSR) by comparing initial HTTP payload to fully rendered DOM.
This check compares the initial HTML your server sends (before any JavaScript runs) with the fully rendered page (after JavaScript has finished executing). If the rendered page is dramatically larger than the initial HTML, it means your site relies heavily on Client-Side Rendering (CSR) — where JavaScript builds the page content in the user's browser instead of the server sending complete, ready-to-read HTML.
Search engines like Google can execute JavaScript to see your page's content, but it's an extra step that takes time and computing resources. Pages that rely heavily on JavaScript to render their main content may experience significant delays in being indexed — sometimes days or even weeks. Server-Side Rendering (SSR) or Static Site Generation (SSG) delivers complete HTML immediately, making it faster and easier for search engines to discover and index your content.
Heavy Client-Side Rendering can cause severe indexing delays, meaning your content might not appear in search results for an extended period after being published. For time-sensitive content (like news articles, product launches, or event pages), this delay can be very costly and cause you to miss out on traffic during the most critical window.
Use Next.js SSR/SSG instead of purely client-side React rendering.Run a free audit to see how your site performs on JavaScript SEO (CSR Detection) and 159 other checks.
Start Free Audit