It’s still surprising to see people placing so much effort and time into doing things the “old” way. Just because you can make pretty graphics and animations it doesnt mean you should… in fact there is a lot of research to suggest it should be avoided.
I highly recommend the ASM guidelines (https://www.asmconsortium.net/deployment/guidelines/Pages/default.aspx) and high performance handbook (https://www.amazon.com/High-Performance-HMI-Handbook-Comprehensive-ebook/dp/B00CELQJU8).
These books go into lots of details about the advantages of keeping graphics simple and the advantages for operators (namely, identifying and addressing abnormal situations). In our example here, the pretty rounded-edges tank would be replaced with a simple bar chart and a sparkline graph showing the last x mins/hrs etc. This lets the operator access the process at a glance and check where the level is in respect to the desired limits, alarm limits and if the process is tracking as desired.
Now, I dont know your project and the context of the question more than is provided so please dont take this message as negative criticism! I’m just trying to raise awareness! I too have made lots of pretty pages in my time but have been converted after implementing, deploying and using an ASM-based system vs traditional. The first impressions are “This is bland…” but it doesnt take long to realise the advantages and to start relying on them!