Improving responsiveness and performance of my dashboard

Configuration Frontend
1

I decided to clean my dashboards, it was way too big and slow.

I deleted things I didn’t need and I thought: what would ChatGPT say about it. There were a few things:

  1. too much templating in the frontend. I made some template sensors and read those in my cards.
  2. visbility rules. ChatGPT suggested that a conditional card was better for performance. But is that true?

Are there other ways to improve my responsiveness?!

2

These are different things:

  1. Templating in a card = ability to use jinja/JS templates in a card config. None of stock cards support such templating (only Markdown card for a “content” option). Only custom cards/plugins like card-mod, apexcharts, button-card support templating. JS templates are resolved on a client side (causing a load on a client device), jinja templates - on a server side. In fact, lots of custom cards/plugins on a page may cause performance issues.
  2. It is normal to “read template sensors” on cards since they are resolved on a server side. All cards support such entities, no need to use “special” cards supporting templating.
3

I moved the templateing in a card, mushroom cards, to template sensors. So all the calculations and icons etc. are set in a template sensor. But this in fact answers my question: jinja templating in a card is client side, putting the same information in a sensor it’s server side.

Is that the same for visability vs conditional card?