All Entity and Device dropdown are insanely slow to load and freeze the browser to the point I can't right click the page or select an entity for a considerable amount of time. This has only gotten worse the more devices I've integrated.

The user interface and drop downs shouldn't freeze.
I also sometimes see this issue when I paste in the full entity id into a dropdown. It's not consistent, but over time I will have to reload the browser and be frustrated the whole time.
I notice this mostly on Safari (14.0.1) but have been able to reproduce on chrome (it takes longer to reproduce and isn't as noticeable). I've seen this both on PC running windows 10 (Ryzen 9 5900x) and Mac OS (2018 6core i7 MBP).
There are way to many entities to list here, but they are in all different kind of states from unavailable (a few). The ones I'm selecting are all available and mostly motion sensors.
I have ~1630 entities and ~366 devices that show up in the config/entities lists. There is nothing that I can think of that would be causing this to be slow hardware wise. HA is running on a NUC 10 and I've been able to reproduce the client side issues on my high end desktop (12 Core Zen 3 5900x).

Here is a view of longest time taken while the cpu is going crazy:


I have a hunch it has to do with massive lists of entities/devices and them all being loaded / rendered and then a bug in the filtering with deletes / adds.
@bdraco Did you create an integration to mock having over 1000 entities? Might be useful here to see if we can reproduce this
@zsarnett http://github.com/bdraco/scaletest
Awesome. I will try to reproduce this sometime in the next week
Using Bdraco's Scale Test Component I was able to create 1600 extra entities.
I can definitely tell there is some lag in loading all pages but I can also reproduce the lag in the Logbook.
It seems to slow down a bit for me. Definitely not an unusable point but I can see a slow down. Seems to just stutter or lag a bit. I was unable to find it keep growing in memory but the scale test doesn't add any logbook history (not really possible I don't think) so maybe that would make the difference there. I am not sure what to do about the slowdown or what could make it better though. Nothing sticks out to me as obvious. The response from the backend seems pretty quick to pull the data when I do have history for an entity.
@bramkragten may have some more insight on what we can do to help performance overall
I see that but I also see it really go crazy when you try deleting the partial. Say you have entity named sensor.back_door_motion, type that in and then delete tion from the end, then delete _door then select all text and hit the delete key. Try it a few times.
Most helpful comment
Awesome. I will try to reproduce this sometime in the next week