I guess I have to look on how people design their dashboards. I only have small display tho (Pi Display), so space is limited. I will try to find different skin and to test.
Lot of space for me is taken by clock, weather and plex.
What do you mean by optimizing the device? Not sure what I really can do in Pi.
with optimising the device i mean actually chosing a device that is fast enough.
browsing on a PI is very slow (try to go to different websites and youll know)
so thats really not the device you want to use for showing different dashboards.
i dont know what actions you want to do on the PI, how many and what dashboards you already have, so i cant give you good advise how to optimise.
if you want to talk about it some more to see what can be done i advise you to come to our discord.
I have done some extensive testing for nearly the same setup as yours, itās just Iām building a remote control for HA, not a wall mounted tablet (I use a tablet as well, but thatās a different thing, as it is Android based).
The only chance you have to speed up your Pi is to minimalize your installation. Letās stay with the remote control example. At first I was trying to base this remote on a Pi Zero, with not much luck. I tried six different dashboards, they donāt make much difference in speed, I coudlnāt get the response time for changing views under nine seconds.
So tried to upgrade the Pi to a 3B+, that did give some improvement, but it wasnāt as good, as I had hoped for. So I again tried the different dashboards, funny enough, the fastest was lovelace in combination with button cards (because of the remote feeling).
But what brought up a real change in speed (between one and two seconds as response time) was the strip down of the Pi. I installed RaspberryOS Lite and ran a minimal installation just for the browser. No desktop, no fancy anything, just OS and browser.
This will give you a relatively normal behaviour on the Pi 3b+, Iād say it works as fast or slow as my laptop does with lovelace. I did a specific (and stripped down) view for that remote, and for now itās running fine and is usable. You have to keep in mind, that this device is only configurable via SSH, and it will start directly to the url you specify (in my case the remote-control-view). You have to make your own controls (buttons) in your dashboard for controlling the Pi (restart and so on) or you have to SSH into the machine.
You will find some instructions on how to build such a minimal setup (OS + Chromium) on Google, I used this one: Setup a Raspberry Pi to run a Web Browser in Kiosk Mode
2 Likes
Hmm, sounds good. I dont remember what I have used since it is some time ago.
But this guide may be obsolete, since I only get black screen now.
It wanted to start openbox-lxde which was missing, so I installed openbox-lxde-session. But I dont think this is the desired setup as it starts different UI. I think autostart is just ignored since it always just wants to start LXDE.
If it wants to start LXDE you must have done something wrong, as LXDE is a desktop environment that we donāt want. 
I suspect you didnāt start fresh with RaspberryOS Lite. LXDE is not part of the Lite version, and therefor shouldnāt even be installed nor needed. RaspberryOS Lite comes without any desktop environment.
You need to get an installation as minimal as it could be. LXDE is a desktop environment that uses a lot of power from your Pi, thatās why we donāt even install it in this use case.
Try with a fresh install, Iāve set this up according to that blog post a few times, it works as expected.