You have an item that updates this often. HABPanel is watching for those changes in the EventSource, and logs every change to console before parsing it.
It’s not trying to load. It’s working as expected. It reacts to the changes published by the event source. Your item is changing that often, so habPanel reacts that often also.
Here’s a quick test. Open a new browser window, point it to http://YOUROH:PORT/rest/events
Watch how often your item state changes. This would be just as often HabPanel will parse them accordingly.
Jersey is not ready yet is expected. Habpanel resources (html/css/js/etc) are cached and also uses service workers, which means HABPanel will RUN even in offline mode even when server is not yet ready.
Read my comment about the event source above. It does not matter if the item is configured in HABPanel or not. If you have an item, it will be published through the event source, and publishing those changes are done my OH itself, not HABPanel.
Because that’s how it works. Without the event source, how would HABPanel know anything about your item state changes. Instead of using websockets, HABPanel is using EventSource . It’s a REST call but the connection is kept alive so clients can remain and “subscribe” to those events.
FYI… Im running one HABPanel instance on a chromium browser on a tiny orange pi zero h2 with only 512 RAM, 1.2ghz CPU and I have zero issues with performance.