Showing results for 
Search instead for 
Did you mean: 
Community Team Member
Community Team Member

In this article, we are going to map some of Sisense Dashboard Design Best practices related to performance. When you start developing a dashboard or when you want to simply improve its performance, take a look at the guidelines below and adjust your dashboard accordingly. 

Avoid Wide or Long pivot tables

  • Reduce the number of columns
  • Filter the number of rows (Top filter on value)
  • Consider Table widget or Aggregated Table plugin

Avoid many members in charts 

  • Wide X-axis in Line / Column charts
  • Many members in “break by
  • Use Drill hierarchies 

Always consider the number of widgets

  • Recommended 7-10 widgets 
  • Consider the number of elements (filters/texts)
  • Use drill dashboards (Accordion / Jump to

Avoid dashboard date functions

  • Date functions in the dashboard are re-calculated in the front end (Qdiff, MTD) 
  • Try to create the logic in the ElastiCube 

Avoid too many include/exclude values

  • Choose the lowest selection between the two
  • Consider using a higher hierarchy

Addons and customization

  • Make sure all the scripts are not colliding (console)
  • Disable un-used plugins

Performance issue and Possible Cause



Version history
Last update:
‎10-14-2021 05:32 AM
Updated by:
Community Toolbox

Recommended quick links to assist you in optimizing your community experience:

Developers Group:

Product Feedback Forum:

Need additional support?:

Submit a Support Request

The Legal Stuff

Have a question about the Sisense Community?