Page could not be rendered

Warning severity, in the JavaScript tab

Why it matters

Headless Chromium timed out or failed on this page, so JavaScript-dependent content was not evaluated. Search engines may hit the same wall.

How to fix it

Load the page in a browser with the network throttled and look for scripts that block rendering, endless loaders or bot blocking. Raise the request timeout if the site is just slow.

How Crawlune finds it

Crawlune flags Page could not be rendered automatically on every crawl and lists the affected URLs under the JavaScript tab, where you can filter, inspect each page and export the list to CSV. The free version crawls up to 550 URLs with every check enabled.