Performance Issues

Reports load slowly

Close the live preview panel and compare the same report again. Large previews and high-resolution images can increase browser memory use. Try a smaller report to see whether the issue is specific to its content.

If several users see the same slowdown, check the server as well as the browser. Include the report's approximate page count, finding count, and image sizes when contacting support.

PDF exports take too long

PDF generation renders the template in a headless browser. Image-heavy reports and complex layouts need more resources.

Check the puppeteer and backend logs for failed requests or timeouts. On a self-hosted instance, inspect container memory use and available disk space. The installation guide lists sizing guidance for the whole deployment.

Slow search

Use category, language, or status filters where available. Compare searches across reports, vulnerabilities, and clients to identify the affected area.

For self-hosted deployments, check MongoDB logs and resource usage. Record the search term, approximate library size, and response time so support can reproduce the issue.

Check server resources

These commands inspect the current deployment without removing data:

docker stats --no-stream
docker system df
vulnotes logs backend
vulnotes logs mongodb
vulnotes logs puppeteer

Do not remove volumes to troubleshoot memory use: they hold persistent data. Review backup and restore before maintenance.