Skip to content
Performance Issues

Performance Issues

Reports loading slowly

If reports take a long time to open, especially reports with many findings:

  • This is usually a browser issue with large DOM sizes. Try closing the live preview panel to reduce rendering load.
  • If the report has many high-resolution images embedded in findings, the browser needs to load all of them. Consider reducing image sizes.
  • Clear your browser cache and try again.

PDF export takes too long

PDF generation uses a headless browser to render the template. Large reports with many pages, images, or complex layouts take longer:

  • Reports with 100+ pages may take 30-60 seconds to generate. This is normal.
  • If exports consistently time out, check that the Puppeteer container has enough memory. On on-premise deployments, allocate at least 2GB to Docker.
  • Simplify complex template layouts if export time is critical.

If searching for reports, vulnerabilities, or clients is slow:

  • For on-premise deployments, check that MongoDB has enough memory. The database benefits from having frequently accessed data in RAM.
  • Large vulnerability libraries (1000+ entries) may take longer to search. Use the category and language filters to narrow results before searching.

High memory usage

On on-premise deployments, if the server runs out of memory:

  • MongoDB is usually the largest consumer. Allocate at least 2GB for MongoDB.
  • The Puppeteer container needs memory for PDF rendering. 1GB is a good minimum.
  • Check for orphaned Docker volumes with docker system df and clean up unused data with docker system prune.