JavaScript & rendering
Pages that appear to be client-rendered shells
One of the 136 checks Lala SEO runs on every page of a site in a free audit.
- How serious
- Worth fixing. Weakens how Google reads or shows the page. Fix after the serious ones.
- Based on
- Google's own documentation
What is wrong
Your website contains pages that load as empty shells and only fill with content after JavaScript runs in the visitor's browser. Search engines send crawlers that can run JavaScript, but they do not wait indefinitely—if the content takes too long to appear, the crawler may index a blank page or give up entirely.
Why it costs you
When a page is indexed as empty or nearly empty, it cannot rank for the words visitors search for. Your pages become invisible in search results. Visitors who do find a link to your site may land on what appears to be a broken or blank page, and leave without reading anything.
How to fix it
Render your essential content (headings, main text, product details) on the server before the page is sent to the browser, rather than waiting for JavaScript to build it. If you use a framework like Next.js or Nuxt.js, enable static generation or server-side rendering in your build settings. Test whether your pages display their main content within 3 seconds when JavaScript is disabled—if they do not, the crawler will likely see what a visitor with slow JavaScript would see.
What the audit tests
- The page's HTML carries real text, not a near-empty shell full of scripts
Check your site
Run a free audit of up to 300 pages. No card needed.
Start a free audit