traccar.org deficiencies

serving traccar.org 3.6 web interface over rpi wifi to mobile device is EXCEEDINGLY slow - read 30 seconds to download all resources, parse java etc on iphone4s.
then, the mobile interface is quite clunky.
given this is a race tracker and the web portal is designed for viewing by general public, we want simple decluttered interface minus logon if possible

traccar.org 3.6 web interface:
pros:

• custom map (for serving our own tiles)
• easy to change html source for referencing offline cdn/js libraries without recompiling

cons:

• web interface is slow to load over rpi wifi and iOS
• mobile interface is poorly fitted to mobile canvas size
• no 'show track' easily available
• no 'no logon/auto logon' available

this project using the old traccar.org web interface package seems to be better suited, but isn't ideal either

https://github.com/vitalidze/traccar-web/
pros:

• auto-logon via http get is possible (we can set a landing page on our rpi captive portal to auto log on as guest and go to mobile site
• mobile site is very good on mobile device
• track is shown
• .war file is just a zip - changing code relatively easy

cons

• no custom map layer - will need to recompile .war to add custom map source if possible (replace OSM url's probably...?)
• will need to recompile .war each time to make changes to code..
• not easy to see where libraries are loaded
• device icons are static, not direction-based arrows
• no track shown in mobile layer
•