JavaScript & rendering
Pages built by JavaScript that we did not render
One of the 136 checks Lala SEO runs on every page of a site in a free audit.
- How serious
- Worth knowing. Small, or only matters in some cases. Read it and decide.
- Score
- Reported, but it does not lower your site's score.
- Based on
- Google's own documentation
What is wrong
Google's search engine has to run your JavaScript code to see what your pages actually look like, because some websites build their content using JavaScript rather than delivering it ready-made in HTML. This audit found pages on your site that appear to use JavaScript to build content, but we were not able to render them—that is, we could not run the JavaScript to see the final result. This might mean the pages need external resources, have errors in the code, or take longer to build than we waited for.
Why it costs you
The risk is that Google might see a blank or incomplete page instead of your actual content. When Google cannot render your pages properly, it cannot read your headings, links and text clearly, which means those pages are less likely to appear in search results, or may appear with wrong or missing information in the search snippet.
How to fix it
Check whether these pages genuinely need JavaScript to work. If they do, test them in Google's Mobile-Friendly Test tool (at search.google.com/test/mobile-friendly) to see if Google can render them now. If the tool shows a blank page or missing content, you may need a developer to investigate why the JavaScript failed to run—common causes include broken code, missing external files, or timeout issues. If these pages do not need JavaScript at all, rebuild them to deliver content in plain HTML instead, which is simpler for Google to crawl and index.
What the audit tests
- Every page built by a JavaScript framework was rendered before being checked
Check your site
Run a free audit of up to 300 pages. No card needed.
Start a free audit